Add status code check for response to _store_bytes putcall
#1089
Labels
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Nov 13, 2023
closes #1089 When doing a `PUT` to write artifact data, we are currently not raising an error directly. Likely an error will still occur when something downstream tries to *use* the artifact data (unless it's the last artifact in a pipeline...), but we should fail more explicitly when the error first occurs.
neutralino1
pushed a commit
that referenced
this issue
Apr 3, 2024
closes #1089 When doing a `PUT` to write artifact data, we are currently not raising an error directly. Likely an error will still occur when something downstream tries to *use* the artifact data (unless it's the last artifact in a pipeline...), but we should fail more explicitly when the error first occurs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now in the API client,
_store_bytesmakes aputcall to write data bytes after getting the signed URL to write them to. If that call fails, it will do so silently right now.The text was updated successfully, but these errors were encountered: