-
Notifications
You must be signed in to change notification settings - Fork 378
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
Experiment.add_artifact with bytes, documentation vs code #924
Comments
Hi @mrzv! The documentation is actually correct, that's (almost) the type annotation of What is your use-case that you can't dump the file to disk before logging? |
Oh, I see. I must misunderstand the meaning of bytes in this case. My use case doesn't prevent me from dumping the file to disk, it's just an extra, inconvenient step, when the data's only purpose is to land in sacred's database. |
The documentation for
Experiment.add_artifact
suggests that it's possible to passbytes
, but it doesn't work, and I don't see it in the code. It would be tremendously useful to be able to save arbitrarybytes
as an artifact. Is there a way to access this functionality?The text was updated successfully, but these errors were encountered: