Add strategy for waiting for remote workers. Closes #6 #7
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Depends on ChimeraPy/Engine#108 |
edavalosanaya
approved these changes
Feb 20, 2023
There was a problem hiding this comment.
Good update to integrated with id-based tracking of Workers. We discussed this before, but I'm curious how we are going to address remote Worker connectivity without relying on using id/name that are closely related or the same. How are we going avoid name collisions in a more structured way? Could we think of the desired behavior (i.e. use-case) that the researcher/system user will go through for connecting remote Workers that reduces setup complexity?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.