Skip to content
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

624 publish on error #864

Merged
merged 2 commits into from
Oct 11, 2022
Merged

624 publish on error #864

merged 2 commits into from
Oct 11, 2022

Conversation

binocarlos
Copy link
Contributor

It turns out we are actually publishing results to IPFS (or whatever the publisher is configured as) in the case of contianer exit code >= 1

I've added a test for this case and we also now have WaitOptions which we can pass to the wait function so we can configure aspects of the wait function without bloating the input params

…ting the params of Wait - keep the existing function as is but trigger WaitWithOptions which uses the new options struct
@lukemarsden
Copy link
Contributor

lukemarsden commented Oct 11, 2022

ok (and thanks!) but what's the user experience of getting those logs?

@binocarlos
Copy link
Contributor Author

The test does basically the same as a bacalhau get <job-id> - i.e. it's the same UX as getting results for a successful job

@binocarlos
Copy link
Contributor Author

We could at some point think about bacalhau logs <job-id> which wraps get and cat stdout

@binocarlos binocarlos merged commit 80d2d14 into main Oct 11, 2022
@philwinder philwinder deleted the 624-publish-on-error branch October 21, 2022 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants