New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TypeError in tracer.ts when getActiveConfig() returns undefined #14
Comments
Hmm.. that is certainly interesting. It shouldn't be possible for Do you have that scenario in this particular case? |
Yep, there is a call to storage inside a |
Yes, I have confirmed reproduction with this test class:
Note it only fails if the worker calling the DO is also instrumented, otherwise it seems to work as expected. |
Awesome! Thanks for the repro.. I am trying to work out the best way to fix this. Hopefully I'll have it fixed in the next few hours :) |
Ok.. a fix for this should be released as part of |
I'm observing this issue when running tests locally with EDIT: it looks related to how miniflare re-initializes the DO in between requests. |
Also got the error in production in a DurableObject, not sure why but the pattern is globally:
Using |
Also getting this same error, same exact situation and repro as @SamyPesse |
I have not attempted a simple repro so I don't know the root cause of this, but this error occurs in my worker reliably:
I was able to resolve it by modifying
getActiveConfig
to return a default value instead of undefined, but this may or may not be appropriate/desired behavior.main...palp:otel-cf-workers:main
The text was updated successfully, but these errors were encountered: