AbortController exception in the wrong place and cannot be caught

[uriva]

Version

23.1.0

What steps will reproduce the bug?

the code in question is https://github.com/webtorrent/bittorrent-tracker/blob/master/lib/client/http-tracker.js#L147

I'm getting the DOMException from the line where the AbortController is created, that is outside the try/catch

How often does it reproduce? Is there a required condition?

Haven't been able to reproduce it locally, happens on a google cloud run instance

What is the expected behavior? Why is that the expected behavior?

The exception should be caught by the try/catch

What do you see instead?

The exception is thrown from an unexpected location.

[avivkeller]

Can you provide a minimal reproduction?

[uriva]

@redyetidev I think this is fixed by nodejs/undici#3354 which iiuc is part of unidici 7.0.0

Any idea how I can get this fix in my docker image today? (I don't care which node I'm running)

[avivkeller]

You can manually use undici? Or build Node.js manually with the upgraded version.

[uriva]

Actually I see this still hasn't been fixed. There is an active discussion about fix/WAI/bug that I haven't been able to fully figure out.

[geeksilva97]

Actually I see this still hasn't been fixed. There is an active discussion about fix/WAI/bug that I haven't been able to fully figure out.

Could you leave a repro on this issue then?

[uriva]

@geeksilva97 I don't have a repro, it happens in production under unknown conditions, but others have experienced the same issue, and the same fix works for everyone. You can see the discussion in the pr I linked above.