New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The difference between written and read binary files #2195
Comments
did you configure the credentials? |
No (besides, as i mentioned, for a non binary file (i checked text ones) the problem is not reproducible) |
please configure the credentials. It is related to how the client works. |
I configured the credentials and it did not affect in any way, the problem remained |
@chrislusf Hi, anything new? |
How to reproduce step by step:
|
Thanks for reporting! This is a bug introduced from 2.51. |
Thank you for the prompt solution of the problem. It is strange that no one noticed this before, it looks like a very serious problem for those who use it, for example, to store important data. In the near future I will definitely check and write down the result. |
@chrislusf Thanks again for the promptness, everything works, the problem does not reproduce on my data and tests |
Sponsors SeaweedFS via Patreon https://www.patreon.com/seaweedfs
Report issues here. Ask questions here https://stackoverflow.com/questions/tagged/seaweedfs
Please ask questions in https://github.com/chrislusf/seaweedfs/discussions
example of a good issue report:
#1005
example of a bad issue report:
#1008
Describe the bug
We write a binary file, download it - we get completely different hashes, sizes and contents.
For text files, there seems to be no such problem, for the rest I did not check.
System Setup
Expected behavior
Identity of written and subtracted files
Additional context
The text was updated successfully, but these errors were encountered: