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
The fix is to explicitly pass in std::ios::binary when opening the file stream. On Windows using a clang toolchain and libc++, trying to upload a binary file without the flag set will result in a rather cryptic exception:
libc++abi: terminating due to uncaught exception of type std::__1::ios_base::failure: ios_base::clear: unspecified iostream_category error
It may be a good idea to add some binary files to the automated tests instead of only text files as well. ;)
The text was updated successfully, but these errors were encountered:
If we are going to add binary files to tests I would like to have a generator of these files in our repository. Could be as simple as a python script, but please no binary files from users that can have encoded whatever data (hello xz utils).
The fix is to explicitly pass in std::ios::binary when opening the file stream. On Windows using a clang toolchain and libc++, trying to upload a binary file without the flag set will result in a rather cryptic exception:
libc++abi: terminating due to uncaught exception of type std::__1::ios_base::failure: ios_base::clear: unspecified iostream_category error
It may be a good idea to add some binary files to the automated tests instead of only text files as well. ;)
The text was updated successfully, but these errors were encountered: