Client: handle 409 HTTP code #130
Labels
No Label
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
lgtm/done
lgtm/need 1
lgtm/need 2
reviewed/invalid
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: JonasFranz/go-sdk#130
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Author: @noerw Posted at: 04.12.2018 22:02
This is helpful, as
POST /api/v1/releases
returns no HTTP body for a 409 request,eg when there already is a release for the specified
tag
.The underlying problem is bigger:
The Client cannot handle error responses which do not contain a valid JSON body.
I tried to solve it by still printing a usable error message instead of a JSON parsing error