Update error handling of subscription
What does this MR do and why?
Update error handling of subscription
- previously the error part of graphql never was triggered and was instead handled by errorMessages
- now error is triggered for some issues
- errorMessages has been deprecated for a more standard errors
- update tests
Changelog: changed
EE: true
References
Please include cross links to any resources that are relevant to this MR This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Error type | Screenshot |
---|---|
Error as data | ![]() |
Top level error | ![]() |
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
- Upload a GitLab Ultimate license
- Navigate to a new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the user is navigated to the newly created security policy project with an MR
- Navigate to the new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the user is navigated to the security policy project with an MR
- Navigate to the new project/group => Secure => Policies => Edit policy project => Remove the linked project
- Navigate to the new project/group => Secure => Policies => New policy => Pipeline execution project => Create a policy
- Verify the error appears and a user can still take actions on the page
- Repeat the steps for every policy type
- Verify the steps above work for every policy type
Related to #495518 (closed)
Merge request reports
Activity
changed milestone to %17.6
assigned to @aturinske
added pipelinetier-1 label
removed pipelinetier-1 label
- Resolved by Alexander Turinske
@Andyschoenen I am confused a bit by the backend still. In the scenario listed in the description, I thought the backend was going to throw an error if the subscription failed due to a backend issue (e.g. a security policy project already exists with the name, but isn't linked), returning the standard graphql error, which would be then picked up the apollo graphql error catcher.
But the errors still get put into a successful request, is that correct?
example of error responses by graphql below.
{ errors: [{message, locations, extensions}] }
Response by the subscription is still a successful response
{ data: { securityPolicyProjectCreated: { status: 'FAILED', errors: [...], errorMessage: '...', project: { ... }, }, }, }
Edited by Alexander Turinske
mentioned in merge request !172751 (closed)
added 556 commits
-
51a570a7...24811360 - 555 commits from branch
master
- bb70b73c - Update error handling of subscription
-
51a570a7...24811360 - 555 commits from branch
Reviewer roulette
Category Reviewer Maintainer frontend @ramistry
(UTC+5.5, 13.5 hours ahead of author)
@jivanvl
(UTC-6, 2 hours ahead of author)
Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger- Resolved by Miranda Fluharty
- Resolved by Miranda Fluharty
@snachnolkar can you review this? Thanks
requested review from @snachnolkar
changed milestone to %17.7
added pipeline:mr-approved label
added pipelinetier-2 label
requested review from @mfluharty and removed review request for @snachnolkar
Bundle size analysis [beta]
This compares changes in bundle size for entry points between the commits 11a02dd5 and 09030197
Special assetsEntrypoint / Name Size before Size after Diff Diff in percent average 4.46 MB 4.46 MB - -0.0 % mainChunk 3.36 MB 3.36 MB - 0.0 %
Note: We do not have exact data for 11a02dd5. So we have used data from: 3abf3154.
The intended commit has no webpack pipeline, so we chose the last commit with one before it.Please look at the full report for more details
Read more about how this report works.
Generated by
Dangeradded pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label
Before you set this MR to auto-merge
This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.
Before you set this MR to auto-merge, please check the following:
- You are the last maintainer of this merge request
- The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
- This pipeline is recent enough (created in the last 8 hours)
If all the criteria above apply, please set auto-merge for this merge request.
See pipeline tiers and merging a merge request for more details.
- Resolved by Miranda Fluharty
- Resolved by Alexander Turinske
nitpick (non-blocking): This "The file path can't be empty" form validation message doesn't seem to be true
mentioned in issue #505363 (closed)
E2E Test Result Summary
allure-report-publisher
generated test report!e2e-test-on-gdk:
test report for 09030197expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 129 | 0 | 22 | 0 | 151 | ✅ | | Govern | 75 | 0 | 3 | 0 | 78 | ✅ | | Package | 24 | 0 | 11 | 0 | 35 | ✅ | | Verify | 43 | 0 | 2 | 0 | 45 | ✅ | | Plan | 76 | 0 | 0 | 0 | 76 | ✅ | | Manage | 1 | 0 | 1 | 0 | 2 | ✅ | | Monitor | 8 | 0 | 0 | 0 | 8 | ✅ | | Release | 5 | 0 | 0 | 0 | 5 | ✅ | | Data Stores | 33 | 0 | 1 | 0 | 34 | ✅ | | Secure | 4 | 0 | 0 | 0 | 4 | ✅ | | Fulfillment | 2 | 0 | 0 | 0 | 2 | ✅ | | Analytics | 2 | 0 | 0 | 0 | 2 | ✅ | | Ai-powered | 0 | 0 | 1 | 0 | 1 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 402 | 0 | 41 | 0 | 443 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
e2e-test-on-cng:
test report for 09030197expand test summary
+------------------------------------------------------------------+ | suites summary | +-------------+--------+--------+---------+-------+-------+--------+ | | passed | failed | skipped | flaky | total | result | +-------------+--------+--------+---------+-------+-------+--------+ | Create | 140 | 0 | 20 | 0 | 160 | ✅ | | Verify | 49 | 0 | 16 | 0 | 65 | ✅ | | Plan | 86 | 0 | 8 | 0 | 94 | ✅ | | Analytics | 2 | 0 | 0 | 1 | 2 | ✅ | | Secure | 2 | 0 | 5 | 0 | 7 | ✅ | | Data Stores | 33 | 0 | 10 | 0 | 43 | ✅ | | Manage | 1 | 0 | 9 | 0 | 10 | ✅ | | Govern | 84 | 0 | 9 | 1 | 93 | ✅ | | Release | 5 | 0 | 1 | 0 | 6 | ✅ | | Package | 24 | 0 | 14 | 0 | 38 | ✅ | | Ai-powered | 0 | 0 | 2 | 0 | 2 | ➖ | | Configure | 0 | 0 | 3 | 0 | 3 | ➖ | | Monitor | 8 | 0 | 12 | 0 | 20 | ✅ | | Fulfillment | 2 | 0 | 7 | 1 | 9 | ✅ | | Growth | 0 | 0 | 2 | 0 | 2 | ➖ | | ModelOps | 0 | 0 | 1 | 0 | 1 | ➖ | +-------------+--------+--------+---------+-------+-------+--------+ | Total | 436 | 0 | 119 | 3 | 555 | ✅ | +-------------+--------+--------+---------+-------+-------+--------+
aborted automatic add to merge train because the source branch was updated. Learn more.
added 387 commits
-
0a8452cc...f245e8fe - 385 commits from branch
master
- 7b04c9dc - Update error handling of subscription
- fd98d34a - Update integration tests for new api
-
0a8452cc...f245e8fe - 385 commits from branch
reset approvals from @mfluharty by pushing to the branch
requested review from @mfluharty
mentioned in issue #458409
- Resolved by Alexander Turinske
aborted automatic add to merge train because the source branch was updated. Learn more.
added 285 commits
-
0014414c...95ce0a22 - 282 commits from branch
master
- a38adf96 - Update error handling of subscription
- 2dd80222 - Update integration tests for new api
- 09030197 - Quarantine test that fails in vue 3
Toggle commit list-
0014414c...95ce0a22 - 282 commits from branch
reset approvals from @mfluharty by pushing to the branch
- Resolved by Miranda Fluharty
@mfluharty can you review this again? Thanks
requested review from @mfluharty
assigned to @markrian
requested review from @markrian
unassigned @markrian
mentioned in issue #505820 (closed)
started a merge train
mentioned in commit afcfd780
added workflowstaging-canary label and removed workflowin review label
added workflowcanary label and removed workflowstaging-canary label
added workflowstaging label and removed workflowcanary label
added workflowproduction label and removed workflowstaging label
added workflowpost-deploy-db-staging label and removed workflowproduction label
added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label
added releasedcandidate label
added releasedpublished label and removed releasedcandidate label