-
-
Notifications
You must be signed in to change notification settings - Fork 271
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IssueHandle::delete_label
panics
#456
Comments
Correction: It is returning an error, rather than panicking (the backtrace was throwing me off). However, the root cause of the issue remains: it's trying to parse a response that the API does not provide. |
Thank you for your issue! I don't have time to fix this myself right now, but the solution is simple, we just need use |
I actually wrote a fix (running on the tool I was writing to find this),
and I'll file a PR later today.
…On Tue, 5 Sept 2023 at 07:21, XAMPPRocky ***@***.***> wrote:
Thank you for your issue! I don't have time to fix this myself right now,
but the solution is simple, we just need use _delete instead of delete
which doesn't try any of the parsing of the request.
—
Reply to this email directly, view it on GitHub
<#456 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGLD24C4A3DB7SUC6RRJLDXY4DK5ANCNFSM6AAAAAA4LRMI54>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I think the PR I just submitted yesterday, #503 should resolve this. |
Thank you for your issue! |
(Code is using
octocrab = "0.30.1"
)When calling
IssueHandle::delete_label
,IssueHandle
panics. This appears to be because it expects a response in Json format, but according to github's documentation, the endpoint does not return any data (on success, it yields 204 No Content).The text was updated successfully, but these errors were encountered: