Skip to content

Fix ambiguity issue with numpy artifact retrieval #387

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

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

kzscisoft
Copy link
Collaborator

When returning a numpy artifact the statement return content or content.response will throw an ambiguity error due to the assertion of a numpy array being ambiguous. This fix switches to checking explicitly for None.

@kzscisoft kzscisoft added the bug Something isn't working label Jun 5, 2024
@kzscisoft kzscisoft added this to the v1.0 milestone Jun 5, 2024
@kzscisoft kzscisoft self-assigned this Jun 5, 2024
@wk9874
Copy link
Collaborator

wk9874 commented Jun 5, 2024

Tested and works :)

@wk9874 wk9874 merged commit 7f45da3 into dev Jun 5, 2024
4 of 10 checks passed
@kzscisoft kzscisoft deleted the hotfix/handle-numpy-object-response branch June 10, 2024 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants