366 Create a api-logs file containing the logs #367
Closed
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
Coverage report
Test suite run success180 tests passing in 64 suites. Report generated by 🧪jest coverage report action from 4fd07bc |
|
366 - add prismaClientInitialization errors to the catch decorator This commit also doesn't seem to solve the problem of catching the base init error |
|
I think we can close this one since we tackled the problem differently in podkrepi-bg/frontend#1110 |
kachar
deleted the
366-feature-dump-error-logs-to-a-file-with-an-artifact-in-the-cicd
branch
|
Solved the file logging by running |
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.
Partly solves #366
Added a
PodkrepiLogger, extending the NestJS logger to now write to a file logs of level higher than LOG in addition to logging in the conosle.That was suggested by @imilchev since we couldn't debug a backend error while running in GitHub actions.
However I found that errors such as database connections or some unexpected crashes are not passed through the Logger which defeats the point, especially considering most of the errors in GitHub Actions are probably of that type! I still haven't found a solution and would appreciate help.