how do i report an issue in production cloudflare (not wrangler or miniflare)?
its an issue about status code not being set in streaming html
17 Replies
Support AI
Hey 👋
It seems there may not be enough information in your post to effectively get support from the community. Please ensure you include as much as possible, you can check the channel guidelines for some examples of what kind of information to include.
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
Do you have a way to reproduce it you can publish?
yes
Would you mind posting it here?
gonna make a repo shortly
https://github.com/huseeiin/cloudflare-streaming-status
go to
src/entry-server.tsx to reproduce and unreproduce
and then go to https://production-url.pages.dev/url-does-not-exist
the status works with streaming disabled and doesn't with streaming enabled
hello?Have you tried checking with the Solid team? I do see the issue, only when deployed, but at least at a cursory glance, I can't see what is wrong without diving deeper into Solid's codebase
well i dived a lil deep into the solid start codebase and couldn't find any clues. this is why i reported it here instead (i also reported it to the solid team). it works in all other runtimes i tested bun, node, deno
Does this work for you? https://streamingstatus.goalastair.com/honk
yeah its 404
Huh ok, so looks like Workers doesn't have the issue, while Pages does. That might make it a weird issue with the adapter, but I'll try to esc
i already knew that too
if workers support streaming, that's weird that it only bugs in pages
idk what is "esc"
Escalate it to the relevant team
the hard part is making a minimal reproduction and send it to the nitro team (nitro is the server library used by solid sart)
Sorry, I meant I'm escalating it to the Pages team. I'm not sure if they are able to do anything, but I figure it is worth a shot at least
yeah its definitely worth a shot
Looks like the team would like the Solid/Nitro team to take a look first, to see if it is something funky with their Pages adapter.
either way it seems pages and workers work the same for my use cases
but it should still be fixed by the appropriate team
i found some new weird update on this: /favicon.ico returns 404 but /some-other-path doesn't
and i have no favicon.ico, just to be clear