fix(app): when a gitlab project does not exist log a warning not error #763
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.
There can be many occasions when a gitlab project is found to not exist when the code expects it to exist.
In all such cases flasks logger is used to post an error. However this is then also picked up by sentry and it causes unnecessary notifications.
I was able to reproduce this error by:
I can confirm that even though the gitlab project is deleted but the session still exists the notebooks service properly lists the session and does not crash or return code 500. But there is an error message in the logs every time a request to the API is sent.