-
Notifications
You must be signed in to change notification settings - Fork 1
gh deploy resulting in TypeError: expected string or bytes-like object
#164
Comments
|
Was the pull request that caused this https://github.com/apiaryio/apiary/pull/5380 ? you seem to have changed the argument to invalid one in the report steps. If so, I wonder if it is because it has empty description, perhaps API returns null and therefore the description past to |
Nope, it was this one https://github.com/apiaryio/apiary/pull/5377 |
I tested my guess about empty descriptions out and GitHub API does return an empty string instead of None. Not sure how to reproduce this one. I tested by applying patch to my black-belt dev version: diff --git a/blackbelt/handle_github.py b/blackbelt/handle_github.py
index ab6c723..3a92b38 100644
--- a/blackbelt/handle_github.py
+++ b/blackbelt/handle_github.py
@@ -178,6 +178,8 @@ def merge(pr_url):
"""
pr_details = get_pr_details(pr_url)
+ print(get_pr_ticket_id(pr_details['body']))
+ raise Exception('prevent next steps and deploy')
# Check if PR is ready to merge - OPEN status
verify_pr_state(pr_details) This patch for you should raise the same exception as before, perhaps using it we can debug this further on your end. |
Got the same thing yesterday with https://github.com/apiaryio/apiary/pull/5382 deploy. Yes, with the patch it reports the same exception. So it seems it is the 'description' being empty.
|
@opichals Want to add |
@kylef Sure, the result of |
Migrated to apiaryio/bb#23 |
Using
bb version
=0.15.10
and issuingI got the following error at the end
The text was updated successfully, but these errors were encountered: