feature: redesign the edge worker status and storage check - #600
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
/demo/_healthreports whether Backblaze accepts its keys (feature: cloudflare workers and deploy scripts 5stack-panel#634). An older worker shows as needing an update.testDownloadaction in feature: storage check reads the test file back api#431), then the worker. Each step shows its result and timing; why a step failed goes in a note underneath..env-examplepointed the relay at relay.5stack.gg, which doesn't exist; it's tv.5stack.gg.testDownloadis added to the generated zeus types by hand; the next codegen after api#431 deploys produces the same.