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.
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
Transport:
AsyncTransport
plugin #6626base: main
Are you sure you want to change the base?
Transport:
AsyncTransport
plugin #6626Changes from all commits
91ea017
b22338e
eb3930f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 123 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L123
Check warning on line 156 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L154-L156
Check warning on line 159 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L159
Check warning on line 190 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L190
Check warning on line 464 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L464
Check warning on line 473 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L473
Check warning on line 476 in src/aiida/engine/daemon/execmanager.py
Codecov / codecov/patch
src/aiida/engine/daemon/execmanager.py#L476
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this change is related, can you move it to another PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Command execution from
asyncssh
library required this annotation, otherwise will not await it, therefore this change is related to this PR.I've checked this change and it has no effect on expected behavior of command execution in
paramiko
, so everything is safe.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you write some comments on why this change does not affect the behavior of bash?
If I have a scheduler that is not direct but still run the bash command will it conflict with asyncssh?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only thing I can see happen is that the printed PID with
echo $!
is printed after the next command because it is run concurrently due to this change. This would be critical, if we would rely on the printed PID, so we would parse the PID from the echo command but get instead a different output. But as far as I checked the schedulers, we do not rely on the printed PID but retrieve the pid using some long ps command (see_get_joblist_command
).The gist is I don't think it interferes.