nuxt-4 (canary) Test Failed #18026

Activity

1. github-actions

   added

   Type: Tests

   Waiting for: Product Owner

   on Oct 24, 2025
2. getsantry

   moved this to Waiting for: Product Owner in GitHub Issues with 👀 3on Oct 24, 2025
3. getsantry

   added this to GitHub Issues with 👀 3on Oct 24, 2025
4. linear commented on Oct 24, 2025

   

   linearBot

   on Oct 24, 2025 – with Linear

   More actions

   JS-1092
5. logaretm

   self-assigned this

   on Oct 24, 2025
6. logaretm commented on Oct 24, 2025

   

   logaretm

   on Oct 24, 2025 – with Linear

   Last edited by logaretm

   Member

   More actions

   Looks like a flake from the middleware test, re-running it is making it pass. Checking to see if the test can be tightened up or if there is actually a possibility that middleware error capturing didn't go through.
7. getsantry

   removed

   Waiting for: Product Owner

   on Oct 24, 2025
8. getsantry

   moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3on Oct 24, 2025
9. logaretm commented on Oct 24, 2025

   

   logaretm

   on Oct 24, 2025 – with Linear

   Member

   More actions

   I managed to reproduce the issue, it is very flakey (once every 10 runs sometimes).

   Looks like theMiddleware error handling had a race condition where errors were sometimes captured with with mechanism auto.function.nuxt.nitro instead of auto.middleware.nuxt.

   I found that the error was being bubbled up to the h3 error capture, but our captureException should've checked already if it was captured by the middleware. This doesn't seem to always work since the error thrown is H3Error and not the original thrown error inside the handler.
   
   I checked to see if the .cause property would contain the original error and if it was marked as captured and it was, so it feels like we need to check for these as well otherwise we may end up capturing errors twice, or swallow the exact mechanism but I'm not sure if this is something we need to consider for the core package as well.
   
   Creating a PR and starting a discussion around it.
10. logaretm

    linked a pull request that will close this issuefix(nuxt): check for H3 error cause before re-capturing #18035on Oct 24, 2025
11. logaretm

    closed this as completedin #18035on Oct 24, 2025
12. github-actions commented on Nov 5, 2025

    

    github-actionsBot

    on Nov 5, 2025 – with GitHub Actions

    ContributorAuthor

    More actions

    A PR closing this issue has just been released 🚀

    This issue was referenced by PR #18035, which was included in the 10.23.0 release.