8000 FIX: Resource monitor would not ever start tracking by oesteban · Pull Request #1051 · nipreps/mriqc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

FIX: Resource monitor would not ever start tracking #1051

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

Merged
merged 1 commit into from
Feb 3, 2023

Conversation

oesteban
Copy link
Member
@oesteban oesteban commented Feb 3, 2023

This was likely caused by a change in Python of how Event() is initialized.

Clearing the event before entering the loop seems necessary now.

In addition, a more reliable initialization of the logfile pathname is also done here.

@oesteban oesteban requested a review from esavary February 3, 2023 10:05
This was likely caused by a change in Python of how `Event()` is
initialized.

Clearing the event before entering the loop seems necessary now.
@oesteban oesteban force-pushed the fix/resource-monitor-done-set branch from d7c47d7 to 30e8184 Compare February 3, 2023 10:13
@oesteban oesteban merged commit 8100c9b into master Feb 3, 2023
@oesteban oesteban deleted the fix/resource-monitor-done-set branch March 2, 2023 14:44
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
0