Skip to content
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

refactor(core): Stop reporting disk I/O error to Sentry (no-changelog) #10324

Merged
merged 1 commit into from
Aug 8, 2024

Conversation

ivov
Copy link
Contributor

@ivov ivov commented Aug 8, 2024

Disk full error is not actionable in-app, so we should not be reporting it.

Example:

@n8n-assistant n8n-assistant bot added core Enhancement outside /nodes-base and /editor-ui n8n team Authored by the n8n team labels Aug 8, 2024
Copy link

cypress bot commented Aug 8, 2024



Test summary

395 0 0 0Flakiness 0


Run details

Project n8n
Status Passed
Commit 1562717
Started Aug 8, 2024 9:59 AM
Ended Aug 8, 2024 10:03 AM
Duration 04:32 💡
OS Linux Debian -
Browser Electron 118

View run in Cypress Cloud ➡️


This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Cloud

Copy link
Contributor

github-actions bot commented Aug 8, 2024

✅ All Cypress E2E specs passed

@ivov ivov merged commit ee8c9a5 into master Aug 8, 2024
27 checks passed
@ivov ivov deleted the pay-1823-error-sqlite_ioerr-disk-io-error branch August 8, 2024 10:04
@@ -69,7 +69,7 @@ export const initErrorHandling = async () => {

if (
originalException instanceof QueryFailedError &&
originalException.message.includes('SQLITE_FULL')
['SQLITE_FULL', 'SQLITE_IOERR'].some((errMsg) => originalException.message.includes(errMsg))
Copy link
Contributor

Choose a reason for hiding this comment

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

Are these errors still logged to console for example? They are noise in Sentry, but for someone maintaining the n8n instance it's probably something you would be interested in knowing

Copy link
Member

Choose a reason for hiding this comment

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

these were already not being logged. but now that they are not being sent to Sentry either, maybe we should start logging these? 🤔

MiloradFilipovic added a commit that referenced this pull request Aug 9, 2024
* master:
  fix(core): Prevent XSS via static cache dir (#10339)
  fix(editor): Enable credential sharing between all types of projects (#10233)
  refactor(core): Extract webhook request handler to own file (#10301)
  feat: Allow sharing to and from team projects (no-changelog) (#10144)
  refactor(editor): Convert ChangePasswordModal to composition api (no-changelog) (#10337)
  docs: Change display name for WhatsApp Trigger API Credential (#10334)
  fix(core): Do not load ScalingService in regular mode (no-changelog) (#10333)
  docs: Update wording in X credentials (#10327)
  fix(editor): Fixing XSS vulnerability in toast messages (#10329)
  fix(core): Rate limit MFA activation and verification endpoints (#10330)
  refactor(core): Decouple emailing and workflow sharing from internal hooks (no-changelog) (#10326)
  refactor(core): Stop reporting disk I/O error to Sentry (no-changelog) (#10324)
@janober
Copy link
Member

janober commented Aug 15, 2024

Got released with n8n@1.55.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Enhancement outside /nodes-base and /editor-ui n8n team Authored by the n8n team Released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants