Closed janpio closed 2 years ago
Can you describe more clearly the steps you did and when the error message appeared?
Downloaded app, installed app, started app first time, created database with parameters shown (but default port), tried to start once, got error message that port already in use, edited prot to 5436
instead, tried to start again, then got error message (with undefined
as message, unfortunately no screenshot), upon checking app again I see "Running" though (see screenshot above)
I can't reproduce that but maybe it's happening for some again so we can find something in common.
@tpetry I was able to reproduce this on my gaming PC that's running Windows 11 Pro 21H2.
[Window Title]
StackBricks.exe
[Main Instruction] Unhandled Error
[Content]
Error: Connection terminated unexpectedly
at Connection.
[OK] [Copy error]
When clicking OK, the errors keeps popping up.
I've also tested **PostgreSQL 9.2** (latest version), which **does work**! But with 9.0 (latest version) it gives me the same error. So it seems to be related to those old PostgreSQL versions.
That‘s strange. When docker says the container is running but you can‘t connect it‘s a docker issue. But StackBricks shouldn‘t throw errors.
really weird, will have to debug that.
PostgreSQL 9.2? Seriously? 🤣
I am testing whether the database has fully started by connecting to it. I guess this old PostgreSQL version is using a different binary protocol. @mchristofides do you know more?
PostgreSQL 9.2? Seriously? 🤣
Well, when testing you click around wildly to make it break. I think we achieved that :D
Do both of you still have the error using the newest PostgreSQL version?
Yes, at least I do not get this error.
I'm only able to reproduce this with 9.1 or lower. I'm not using those versions myself but just tried to see if I got the same error.
If I can help you out by testing something else, please let me know.
In general I would not mind to just not support those old Postgres versions as those are unsupported since 2016 anyway.
I'm also able to reproduce the behaviour in macOS (Monterey), intel MacBook, using StackBricks 0.5.0.
I used the same spec, as in the initial post, except that I picked Postgres 9.0 (latest).
When I shut down the container (after it finally starts) I get completely spammed with another popup for each fatal error message I saw in the container log. I clicked the 'ok' button a few times before screen recording, and I can also confirm it disappeared after holding escape for quite some time. I'd say it was as many popups as error messages in the container log, but didn't count.
The loading spinner is also going really bonkers (more blinking than spinning), but seemingly spins when trying to recording it. Not really the error itself, but I'd say related to the errors, causing the graphics to glitch.
I basically just started it all, hoping to get some error messages that may be of value to debug. I did also try both Posgres 10 (latest), Postgres 11 (latest), and Postgres 14 (latest), and all of them starts in seconds without issues.
I recall Postgres changing the 'healthcheck' binary somewhere in Postgres 9 to a new one (or renamed). Not sure if that'd be related.
Edit: Decided to record the whole thing and added that as well.
Thanks all for the information. Will work on a fix next week.
The bug was that the PostgreSQL connection when connected loaded meta information about the PostgreSQL instance and some of these relations had not been available in PostgreSQL 9.0. The meta information is no longer accessed, the bug is fixed with 0.5.1
.
Can confirm this works now.
Just installed on Windows and tested for the first time, got a error message
undefined
afterwards but now the database is shown as status "Running".