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

Uncaught errors #10567

Closed
rafaelromcar-parabol opened this issue Dec 10, 2024 · 0 comments · Fixed by #10580
Closed

Uncaught errors #10567

rafaelromcar-parabol opened this issue Dec 10, 2024 · 0 comments · Fixed by #10580
Assignees
Labels

Comments

@rafaelromcar-parabol
Copy link
Contributor

rafaelromcar-parabol commented Dec 10, 2024

Issue - Bug

  • How serious is the bug? P3
  • OS: macOS / Linux / Windows / ? -
  • Browser: Chrome / Safari / Lynx / ? + version -
  • Node version: node --version 20.18.1
  • NPM version: npm --version
  • Parabol v8.10.0

Errors

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:                   
Error: Non-nullable value is undefined                                                                                                                                                                             
    at NullableDataLoader.loadNonNull (/home/node/parabol/dist/gqlExecutor.js:154819:13)                                                                                                                           
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)                                                                                                                                  
    at async sendEnterpriseOverageEvent (/home/node/parabol/dist/gqlExecutor.js:152682:18)

Acceptance Criteria (optional)

Errors are caught and logged using json format + sent to Sentry
Triage is performed to find the root cause of the bug, timeboxed to ~1 hour.

Estimated effort: 1 hour to triage. More if root cause is already identified.

@rafaelromcar-parabol rafaelromcar-parabol changed the title Uncatched errors Uncaught errors Dec 10, 2024
@Dschoordsch Dschoordsch self-assigned this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants