[explorer/rest] fix: fail startup on Symbol database initialization errors and return 503 on runtime failures - #2581
Draft
daoka wants to merge 1 commit into
Conversation
…rrors and return 503 on runtime failures
daoka
added this pull request to stack #2582
September 18, 2026 05:47
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## explorer/backend/rest-receipts #2581 +/- ##
==================================================================
- Coverage 97.43% 97.25% -0.18%
==================================================================
Files 368 359 -9
Lines 27148 25514 -1634
Branches 251 251
==================================================================
- Hits 26451 24814 -1637
- Misses 690 693 +3
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
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.
What is the current behavior?
SymbolRestFacade creates its own database and catches initialization errors, allowing the application to start without a usable database. Block detail requests can then return 404 despite the database being unavailable.
This PR builds on #2580 and targets
explorer/backend/rest-receipts.What's the issue?
Database initialization failures are hidden behind a running application, and unavailable data can be confused with a missing resource. Database construction and cleanup also lack a clear application-level owner.
How have you changed the behavior?
Startup compatibility changes: deployments that previously started without a database now fail during application creation. HTTP paths and response schemas are unchanged.