-
Notifications
You must be signed in to change notification settings - Fork 265
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
Docker error: CODE_MOVED for unknown code block? #1472
Comments
I'm also getting this error, but not just in Docker. It seems to have been introduced in wrangler 3.18 or 3.19, as 3.17 does not have this issue for me. |
That's strange, our Docker env was using 3.17 but still got this error. |
This message is not really an error, at least not one that's relevant to most people. This is another example where our logging is highlighting bugs meant for the workers runtime team to look into. In this case V8's API for mapping JITed memory in order to construct stack traces isn't working the way we expect. This has been firing occasionally for a long time. There's actually no impact for workerd users since this information is only used when generating crash dumps in our internal codebase. |
Hmm, for me it's the only noticeable difference between my worker responding on 3.17 and hanging on 3.19. Maybe it just coincides with another breaking change rather than the cause? |
👋 If it helps in debugging this, I'm reliably seeing this for one set of our tests w/ Miniflare: https://github.com/cdnjs/api-server/actions/runs/7440877000/job/20242359379 |
TBH we should remove the logging for this error as it's unlikely anyone is going to spend time debugging it... it just doesn't matter that much. |
I got the same Pages site is not served, got thousands of 500 internal server error lines. |
@tddschn Sorry, the CODE_MOVED message has nothing to do with any other problems you're seeing. |
I am still seeing this issue in 3.36.0. Perhaps the priority of this issue can be bumped up a bit? Even if it is benign, it makes spotting other errors/warnings in logs more difficult. Actually, this warning disappears for me when I remove the |
I am starting to see them more often in CI and they seem to coincide with some process crashing. Since whenever I see these, my tests timeout. I know most comments indicate, that they should not be relevant, but could we get some more background info? |
Same here, we concluded the same results. But yeah more background info would indeed be nice. |
got the same error with wrangler 3.39.0 https://gist.github.com/Zxilly/9273aa5909f539db3f0dc8736aaab9bd
|
trying to batch insert rows into a d1 table when all of a sudden these error messages popped up (on random occassions within the process. the requests are still being completed though but still its irritating since you're debugging until you finally find these statements in this issue, that these are not related to your code. weird.
can we somehow catch them? or prepend them otherwise from being shown to the log? |
This log message indicates a problem with workerd itself, not with the application -- but it's a benign problem that doesn't cause any issues except possibly making crash dumps slightly less useful. This shouldn't be displayed to application developers, since there's nothing they can or should do about it. Fixes #1472.
I made a PR (#2037) to remove this log message. |
Running
wrangler dev --port=8000
inside Docker with:Everything works fine if I run this outside of Docker, but if I put everything in Docker, when I want to do the proxy, I get:
Individual URL for the host (eg. front-end) works fine from Docker.
Not exactly sure what the
headerBuffer.size()
and where that could be? Could this due to some host settings within Docker?The text was updated successfully, but these errors were encountered: