-
Notifications
You must be signed in to change notification settings - Fork 32
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
blockUntilReady and cf workers #70
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
bump |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Is this going to be addressed eventually? This is a serious concern that most users will probably not be aware of. |
We’ll see what we can do and if we can’t find a good solution, we’ll document in our docs. Sorry for late reply. |
Issue is finally addressed here in the docs: upstash/docs#121 |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. |
blockUntilReady relies on Date.now, but in cf worker env, Date.now does not reliably progress as in nodeJS or browser env.
https://developers.cloudflare.com/workers/runtime-apis/web-standards/
Maybe this could get added to docs, it might safe a few people from headaches.
The text was updated successfully, but these errors were encountered: