[BUGFIX] Corriger getPgQueriesMetric lorsque le résultat est null #112
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
|
Une fois l'application déployée, elle sera accessible à cette adresse https://db-stats-pr112.review.pix.fr |
alipix
approved these changes
Aug 13, 2024
pix-service-auto-merge
force-pushed
the
fix-get-pg-queries-metrics-when-null-result
branch
from
a3c2058
to
9e1e459
Compare
pix-service-auto-merge
deleted the
fix-get-pg-queries-metrics-when-null-result
branch
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.
🦄 Problème
Nous avons eu des erreurs pendant quelques heures à cause d'une valeur null retournée, apparemment, par l'API de Scalingo. Cette valeur n'était pas gérée dans le code.
🤖 Solution
Ne pas lancer d'exception lorsque le résultat des running queries est null.