Open janbuchar opened 5 months ago
I know that the reproduction example is a very bad use of the method. I made it this way to make the code crash deterministically.
Same here, not sure where to look for the problem... seems like a missing try/catch or a improperly handled rejection, or a missing error listener somewhere in the library code.
Hey @janbuchar, why is this a bad use of the method? I'm running into a similar error.
Hey @janbuchar, why is this a bad use of the method? I'm running into a similar error.
It calls enqueueLinks
with the complete set of URLs for each URL in the set. This is completely unnecessary and slow. The correct approach would be calling enqueueLinks
once, with a selector.
Even though it's bad usage, it uncovered a bug that's worth fixing, which is why I put the sample here.
Which package is this bug report for? If unsure which one to select, leave blank
None
Issue description
Executing the snippet below results in the following error:
Also, it's strange that the traceback doesn't lead to user code.
Code sample
Package version
3.7.3
Node.js version
v21.6.1
Operating system
Linux
Apify platform
I have tested this on the
next
releaseNo response
Other context
No response