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
Currently, a GET to /utilities/view returns a string with the given file content. Would it be possible to have a binary version of it?
E.g. if I do view of a tar.gz i get
Status code: 400
JSON: {'description': 'Error on head operation', 'error': "'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte"}: 'utf-8' codec can't decode byte 0x8b in position 1: invalid start byte
More generally (maybe this is not intended for binary files?) it would be important also for text files, in case e.g. they were written in some other non UTF-8 encoding, that would likewise fail.
The text was updated successfully, but these errors were encountered:
The idea of this endpoint is to see the content of a plain text file, thinking on the use case of checking what is being written in SLURM output or error files, or to show configuration files of a simulation, for instance.
I wouldn't use this to check the content of a binary file, moreover, if you try to see the content of a binary file without specific software you would get bytes without proper encoding (I guess).
In the case you are mentioning, we can try to include UTF-8 files in the same endpoint.
I am basically copying this issue by @giovannipizzi from pyFirecREST: eth-cscs/pyfirecrest#7
Currently, a
GET
to /utilities/view returns a string with the given file content. Would it be possible to have a binary version of it?E.g. if I do view of a tar.gz i get
More generally (maybe this is not intended for binary files?) it would be important also for text files, in case e.g. they were written in some other non UTF-8 encoding, that would likewise fail.
The text was updated successfully, but these errors were encountered: