Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Read-only DB messaging
See original GitHub issueBug Report
Expected behaviour
A postgres database in read-only mode should pass messages back to the UI properly.
Actual behaviour
After setting read-only mode (http://longwayaround.org.uk/notes/read-only-postgres-database/), the UI just displays [HTTP 500] Internal Server Error: [object Object] on operations. In the web service log we can see messages like ERROR: cannot execute INSERT in a read-only transaction or ERROR: cannot execute UPDATE in a read-only transaction which would be more descriptive.
Environment (Browser or OS and Dockstore version)
DockstoreUI - 1.2.3 DockstoreApi - 1.2.3
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Huh, I wonder if this is a side-effect of using hbm2ddl validate, what’s the error message on start-up? (Oh, and re-reading, we actually don’t care about a read-only database specifically. That’s just a (or maybe was) a simple test case. The larger issue is that database errors were being suppressed as a generic 500 error. We can probably rainstorm some creative reproducible DB error conditions to test with instead on Monday/Tuesday)
Was able to test by just disabling index creation on start-up temporarily. Added a few more error conditions caught and displayed by the ui2
https://github.com/ga4gh/dockstore/pull/1090 https://github.com/dockstore/dockstore-ui2/pull/164