Fix initialization race conditions and improve error resilience. #323
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.
getServerByNamenow propagates errors from the internalset-namerequest instead of silently swallowing them.onStartfailures no longer permanently brick the Durable Object. Errors are caught insideblockConcurrencyWhile(preserving the input gate) and the status is reset, allowing subsequent requests to retry initialization.fetch()now retries initialization when a previousonStartattempt failed, instead of skipping it because the name was already set.fetch()(includingonStartfailures and malformed props) are now caught and returned as proper 500 responses instead of crashing as unhandled exceptions.webSocketMessage,webSocketClose,webSocketError) are now wrapped in try/catch so that transientonStartfailures don't kill the connection — the next message will retry.