-
Notifications
You must be signed in to change notification settings - Fork 4
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
offline bundling crash #60
Comments
@kfox1111 Offline bundling isn't really a thing, I'm not sure what would be gained by an offline bundle as the metadata wouldn't be resolvable. Querying more metadata wouldn't be possible either. What's the difference between an offline bundle and simply taring up the files you've specified with any local configuration? |
It use to be, but maybe not anymore, that you could bundle up something that you were going to upload, but not upload it. Say, you had an instrument that you wanted to generate the upload from that had no connectivity, take it to another machine, then finish the upload with it. Is that no longer possible? Sure you could add an extra tar/untar step in the process, but capturing the metadata wouldn't necessarily happen at the best time in that case. It might be best handled at the instrument. |
@kfox1111 Okay I think I get what you are talking about now. A |
Pacifica CLI Tool version
[Version of the pacifica software where you are encountering the issue]
Pacifica Core Software versions
NA
Platform Details
Docker
Scenario:
Bundling a file offline does not work but instead crashes.
Steps to Reproduce:
Expected Result:
A bundle to be produced
Actual Result:
The text was updated successfully, but these errors were encountered: