Fix exception on 204 when collecting jobs#5300
Merged
Merged
Conversation
CamilleTeruel
force-pushed
the
5083_exception_on_204
branch
3 times, most recently
from
f4c26c0 to
7c52e91
Compare
CamilleTeruel
force-pushed
the
5083_exception_on_204
branch
from
7c52e91 to
4c7ee4a
Compare
chenggui53
pushed a commit
to chenggui53/incubator-devlake
that referenced
this pull request
Jun 6, 2023
* fix: Do not raise APIException when status < 400 * fix: Let jobs endpoint handle 204 NO CONTENT status --------- Co-authored-by: Camille Teruel <camille.teruel@meri.co>
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.
Summary
Fix error when collecting jobs of builds that failed because of bad
azure-pipelines.yaml.Does this close any open issues?
Closes #5083