-
Notifications
You must be signed in to change notification settings - Fork 81
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
Fix "RET503", # Missing explicit return
at the end of function able to return non-None
value
#1357
Conversation
… to return non-`None` value Signed-off-by: Jiri Daněk <[email protected]>
Robot Results
|
Signed-off-by: Jiri Daněk <[email protected]>
Signed-off-by: Jiri Daněk <[email protected]>
|
I'm not sure why I'm being asked to review this? Did you mean to request a review from someone else? |
I clicked all the autosuggestions from github, should be based on who edited the files recently. It's possible i missclicked. If so, sorry about the disturbance. |
@jiridanek has this been tested indeed? I can see following failure in our job 🤔
|
The initial version was semantically equivalent code. The changes I did at @kobihk 's suggestion do have potential to break things. And no, I did not test it before merge. |
The fix is to add
at the top of the file. Be cause file is nor run with python3 11 but with some older python. I'll put it in when I get to the office in 1.30 hours or so. |
…ion able to return non-`None` value (red-hat-data-services#1357)" This reverts commit b791898. This change caused a TypeError issue when trying to do the ocm login, see [1] [1] red-hat-data-services#1357 (comment)
…ion able to return non-`None` value (#1357)" This reverts commit b791898. This change caused a TypeError issue when trying to do the ocm login, see [1] [1] #1357 (comment)
@jiridanek maybe without the definition of return type it could work |
No description provided.