Repository navigation
fix(publish): map item history 400/403/404 (#4740) - #4744
Merged
Merged
Conversation
PublishingShell item history already listed status, server, and time. GET pubhistory now returns 400 for a bad id, 404 when the item is missing, and 403 when the caller has no assignment, and the panel maps those statuses instead of treating them as empty history. > Co-Authored by Grok Build 1.0.40 using grok-4.6 with agent night-issue-prs.
Record the pre-push mkd-code-review advisory report. In-diff bugs: 0. > Co-Authored by Grok Build 1.0.40 using grok-4.6 with agent night-issue-prs-erlang.
Collaborator
Author
|
LGTM. Erlang 0.1.1 / mkd-code-review 0.1.18 (pack percussion, gate advisory, base origin/main). In-diff findings: 0. Preexisting rows are outside the diff and do not block. Tests cover the new 400/403 (and 404 on #4744) paths. Same-login APPROVE is rejected by GitHub; this comment is the review.
|
4 of 5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Parent: #4531 (slice 19 / ITM-06).
PublishingShell already shows item publish history (status, delivery server, location, time) on Status and Logs via
GET /services/itemmanagement/item/pubhistory/{id}. This slice maps the lookup failures the panel was collapsing into a generic error:Those responses stay errors in the panel. They are not empty history and not success. Schedule dates (#4741) and takedown (#4742) are unchanged.
Operator: Grok: night-issue-prs (model grok-4.6)
Fixes #4740
Test plan
PSItemServicePublishingHistoryTestcovers 400, 403, 404, 500, and a reader success rowitemHistoryErrorMessageand the history paneltests/publishing/itemPublishingHistory.spec.js— 3 passed, pageerror listeners emptyProduct documentation
product-docs/8.2/admin/publishing.md(item publishing history error states)Maven
projects/sitemanage,WebUI,modules/perc-qa-automationcd projects/sitemanage && rtk mvn clean install— BUILD SUCCESS. Tests run: 2972, Failures: 0, Errors: 0, Skipped: 125cd WebUI && rtk mvn clean install— BUILD SUCCESS. Java tests run: 69, Failures: 0. Vitest: Test Files 517 passed, Tests 4786 passedcd modules/perc-qa-automation && rtk mvn clean install— BUILD SUCCESS. No tests to runUI proof (H2 QA)
python3 docker/scripts/perc-devctl.py qa-up— TEST_CMS_URL=http://127.0.0.1:9993, container perc-matrix-cms-h2qa-healthRESULT:OK HEALTH:healthyqa-deploy-war-jars --restart-jetty(sitemanage + perc-system SNAPSHOT into WEB-INF/lib, in-cell StopJetty/StartJetty) andqa-deploy-webuiqa-healthagain RESULT:OK HEALTH:healthynpm run test:surface -- --path tests/publishing/itemPublishingHistory.spec.js— 3 passedPre-push local code review
Erlang review — PR #4744
Scope
CLI stdout (
mkd-code-review analyze --format markdown)Summary
Machine analysis found 6 finding(s), 0 bug(s).
Scope
Recommendation
approve
Gate
Issues
Issue 1 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sepIssue 2 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sepIssue 3 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sepIssue 4 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sepIssue 5 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sepIssue 6 -- Severity: bug
paths.hardcoded_seppaths.hardcoded_sep