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

Catch query timeout exceptions #5680

Merged
merged 1 commit into from
May 31, 2024
Merged

Conversation

thomtrp
Copy link
Contributor

@thomtrp thomtrp commented May 30, 2024

Query read timeouts happen when a remote server is not available. It breaks:

  • the remote server show page
  • the record table page of imported remote tables

This PR will catch the exception so it does not go to Sentry in both cases.

Also did 2 renaming.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

  • Introduced handling for query timeout exceptions across various services
  • Renamed filterException to shouldFilterException for clarity
  • Added isQueryTimeoutError utility function to identify query timeout errors
  • Configured query timeout settings in TypeORM metadata and main DataSource
  • Renamed assertIsValidUuid.util.ts for consistency in file naming conventions

@charlesBochet charlesBochet merged commit c60a3e4 into main May 31, 2024
6 checks passed
@charlesBochet charlesBochet deleted the tt-catch-query-timeout-exceptions branch May 31, 2024 08:39
Weiko pushed a commit that referenced this pull request May 31, 2024
Query read timeouts happen when a remote server is not available. It
breaks:
- the remote server show page
- the record table page of imported remote tables

This PR will catch the exception so it does not go to Sentry in both
cases.

Also did 2 renaming.
arnavsaxena17 pushed a commit to arnavsaxena17/twenty that referenced this pull request Oct 6, 2024
Query read timeouts happen when a remote server is not available. It
breaks:
- the remote server show page
- the record table page of imported remote tables

This PR will catch the exception so it does not go to Sentry in both
cases.

Also did 2 renaming.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants