Conversation
This was an attempt to fix a problem with the GitHub workflow. The worflow fails on GitHub although it passes locally. I had a linting problem when I initially pushed. I fixed this and force-pushed. I'm afraid it may be caching the pre-force-push code and running the workflow against that. Hoping these commits will invalidate that cache, if that is in fact the issue.
The old version I had installed locally was satisfied with the code, but the new version running on CI was not. This should allow the code to pass.
The tests all fail with this decorator applied even though this is recommended in FastAPI's documentation
Also run tests in a test database.
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
2 participants
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.
Add automated tests to protect against our most recent issue that broke the FastAPI example project