Closed xriter closed 6 months ago
I'm not sure why the previous issue was closed, the linked PR only affects logging. As for the bug itself, I can't reproduce the it but the issue is clearly with nodejs/undici - it assumes the iterator will always have a return()
function, whereas it is supposed to be optional in the iterator protocol.
Considering undici is on v6 but embedded within node 18, 20, and 21 is v5, an upstream PR won't help. We probably have to do a workaround. I'm guessing a no-op return()
will do.
Astro Info
Describe the Bug
The problem as described below, was first mentioned in #10184, but seems to be still an issue.
The following error is being logged sometimes:
I have not been able to reproduce it consistently yet. The stack trace doesn't point to any custom code, so it seems like it is a problem in the node code?
What is the
TypeError: iterator.return is not a function
it is referring to?Anyone else experiencing this?
Could be related to #9614 Supposedly fixed by #10197 - but the error is still thrown for unknown reasons.