This repository has been archived by the owner on Jan 12, 2023. It is now read-only.
try removing the latest version to see if it's a node thing #220
Conversation
This file contains 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
GItHub Actions reliably fails, saying "Connection terminated unexpectedly". At first, I thought the CI was calling
docker-compose downafter one of the tests was over, causing the others to lose connection; however, this doesn't seem to be the case.I've also ruled out tmpfs and docker-compose v1 vs v2 as a reason why it might be locally but not in Actions as well.
For whatever reason, in the official Postgres v13 image, they introduced a regression where it just... fucking refuses and/or drops connection in the CI, again reliably so.
For now, I'm pinning it to v12 but this is fucking bullshit of a solution.