Amazing, @Frederik — thanks for
Amazing, @Frederik — thanks for confirming it's an issue on your end, and we're looking forward to a fix! 🙏
16 Replies
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Hi Frederik, thanks for getting back to me! This morning I have been doing some testing, but unfortunately we're still running into this issue. We're still seeing issues where the returned date by
.getWebSocketsAutoResponseTimestamp(mysocket) is too old. There have definitely been more recent ping/pongs that our clients have received from the auto-response, but it looks like the last auto-response timestamp still isn't reliably getting updated 😞Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Ohhh, that's somewhat good news then. I was about to sit down and try to make a minimal replication of it, but maybe I can spare myself the effort in that case. Thank you very much! We're anxiously awaiting the fix! 🙏
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
@Frederik In case it will help, here is a minimal replication of the bug:
https://github.com/nvie/cloudflare-repros/tree/gwsart-bug?tab=readme-ov-file#the-replication
Demo video using that minimal replication: https://share.cleanshot.com/nzVS2sMSHgz7YLcrTdXZ
@Frederik I've also opened a GitHub issue for this one: https://github.com/cloudflare/workerd/issues/2025 — hope this helps to get this resolved! 🙏
GitHub
🐛 Bug Report —
.getWebSocketAutoResponseTimestamp() not returning...The return value of the state.getWebSocketAutoResponseTimestamp() method doesn't return the correct timestamp in production. It does, however, work locally. Minimal replication Here is a minima...
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Appreciate the help, @Frederik !
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
@Frederik Thanks! Would you mind sending us a message when the fix is in production? Then we can do a final check and inform our customers.
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
@Frederik Any updates here? We noticed the
.getWebSocketsAutoResponseTimestamp() bug seemed to be fixed briefly yesterday afternoon, but today the bug is back again. Was a roll-out attempted but rolled back, perhaps?Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
Will do – thanks for the update!
Our issues are definitely trending down, this is great! Thank you so much for getting this addressed!
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View