Skip to content

fix: execution plan svg not saving in chrome #1744

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Dec 12, 2024

Conversation

astandrik
Copy link
Collaborator

@astandrik astandrik commented Dec 9, 2024

Closes #1743

CI Results

Test Status: βœ… PASSED

πŸ“Š Full Report

Total Passed Failed Flaky Skipped
212 212 0 0 0
Test Changes Summary ✨3 πŸ—‘οΈ1

✨ New Tests (3)

  1. Plan to SVG dropdown shows options and opens plan in new tab (tenant/queryEditor/planToSvg.test.ts)
  2. Plan to SVG download option triggers file download (tenant/queryEditor/planToSvg.test.ts)
  3. Plan to SVG handles API errors correctly (tenant/queryEditor/planToSvg.test.ts)

πŸ—‘οΈ Deleted Tests (1)

  1. Plan to SVG experiment shows execution plan in new tab (tenant/queryEditor/planToSvg.test.ts)

Bundle Size: πŸ”Ί

Current: 65.88 MB | Main: 65.87 MB
Diff: +5.96 KB (0.01%)

⚠️ Bundle size increased. Please review.

ℹ️ CI Information
  • Test recordings for failed tests are available in the full report.
  • Bundle size is measured for the entire 'dist' directory.
  • πŸ“Š indicates links to detailed reports.
  • πŸ”Ί indicates increase, πŸ”½ decrease, and βœ… no change in bundle size.

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 2 out of 3 changed files in this pull request and generated no suggestions.

Files not reviewed (1)
  • src/containers/Tenant/Query/QueryResult/i18n/en.json: Language not supported

artemmufazalov
artemmufazalov previously approved these changes Dec 10, 2024
Raubzeug
Raubzeug previously approved these changes Dec 10, 2024
})
.catch((err) => {
setError(JSON.stringify(err));
const errorMessage = err.data?.message || err.message || JSON.stringify(err);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we want to move such a logic into a helper (we have similar logic in ResponseError and parseQueryError)?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

moved to utils/errors

@astandrik astandrik added this pull request to the merge queue Dec 12, 2024
Merged via the queue into main with commit 189174a Dec 12, 2024
7 checks passed
@astandrik astandrik deleted the astandrik.move-storage-tables-to-paginated-1693 branch December 12, 2024 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

fix: execution plan svg not saving in chrome
3 participants