Closed leontastic closed 7 months ago
It doesn't seem to be Deno. I ran a regression using Deno 1.4x.x versions and Oak v12 with the latest Superoak without issues. However, the problem starts to happen when I bump Oak to v13.
I couldn't find yet any change in Oak that would cause the API AbortController to throw an error.
Just an update on this. I opened a PR to fix this issue on the Oak v14.0.0 module and it looks good now.
The fix submitted by @petruki for this: https://github.com/oakserver/oak/pull/639
Landed in version 14.0.0 https://github.com/oakserver/oak/blob/main/CHANGELOG.md#version-1400
Thank you sir 🙏
It doesn't seem to be Deno. I ran a regression using Deno 1.4x.x versions and Oak v12 with the latest Superoak without issues. However, the problem starts to happen when I bump Oak to v13.
It would still be very good if Deno could handle it, as not everyone is using Oak. In my project I had to implement an ugly hack to prevent this "Bad Resource ID" crash. Actually Deno should allow to catch this exception similar to Node to prevent process restart.
I feel like this should work out of box, but for some reason it doesn't. Since I don't see any mentions of
Bad Resource ID
onoak
orsuperoak
repositories I suspect it is an issue with deno.Deno version:
Reproduction:
Output: