bug: fix recursion error during docker compilations #147
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 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.
Fixes #146, though to be honest I'm not sure why the issue randomly started cropping up to begin with. I tracked down the issue being a change introduced in #141. I started with the
schema.prismachanges and the problem presented immediately once I added those in. There have been multiple passing docker builds since this PR, which is why it is so puzzling that this fix is now all of the sudden needed.The musl version in the docker images I use did change a week ago from
1.1.24to1.2.3, which seems to correspond to the last successful PR run, but I'll have to look into whether that is a potential cause another time.I updated prisma while I was at it