You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @DyfanJones ,
thanks for the fix and apologies for the delayed response! I was on a lengthy business trip with limited hands-on-keyboard time. You were correct with your remark regarding the return object, which should and now is a json in raw bytes. Your fixes solved the issues described above.
After the latest release of paws.common-v0.7.1, I only found one minor difference in paws compared to boto3 for invoke_model.
The default contentType value is application/json (see boto3 documentation here), as shown below, re-using the Python example from above.
Hi @DyfanJones ,
thanks for the fix and apologies for the delayed response! I was on a lengthy business trip with limited hands-on-keyboard time. You were correct with your remark regarding the return object, which should and now is a json in raw bytes. Your fixes solved the issues described above.
After the latest release of
paws.common-v0.7.1
, I only found one minor difference in paws compared to boto3 forinvoke_model
.The default
contentType
value isapplication/json
(see boto3 documentation here), as shown below, re-using the Python example from above.However, the R equivalent returns the following:
The behavior stays the same even when setting the
contentType
explicitly:Originally posted by @alex23lemm in #749 (comment)
The text was updated successfully, but these errors were encountered: