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
I found this working with statements API, but it does effect all file endpoints and as part of the upstream OpenAPI Generator code, effect all file transfers. The header "content-transfer-encoding"=>"binary" is never acknowledged making the files functionally corrupt.
The monkey patch to verify this looks something like this
Thank you for the report and going the extra mile to submit a patch to the openapi tools generator. We'll keep an eye out for their next release, but we probably won't be able to pick this up for another week or two (and hopefully by then they'll have pushed out that minor version update).
I found this working with statements API, but it does effect all file endpoints and as part of the upstream OpenAPI Generator code, effect all file transfers. The header
"content-transfer-encoding"=>"binary"
is never acknowledged making the files functionally corrupt.The monkey patch to verify this looks something like this
The text was updated successfully, but these errors were encountered: