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

Set the monitor_running event to unblock the main thread #506

Merged

Conversation

agrare
Copy link
Member

@agrare agrare commented Jun 26, 2020

Without setting the monitor_running concurrent event the main event_catcher worker thread doesn't ever leave the do_before_work_loop which means it can't be shutdown cleanly until the first event is raised.

Related to: ManageIQ/manageiq-providers-amazon#633

Without setting the monitor_running concurrent event the main
event_catcher worker thread doesn't ever leave the do_before_work_loop
which means it can't be shutdown cleanly until the first event is
raised.
@miq-bot
Copy link
Member

miq-bot commented Jun 26, 2020

Checked commit agrare@9eb72e1 with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.28.0, and yamllint
1 file checked, 0 offenses detected
Everything looks fine. 🍰

@chessbyte chessbyte self-assigned this Jun 27, 2020
@chessbyte chessbyte merged commit 5aaa3a7 into ManageIQ:master Jun 27, 2020
simaishi pushed a commit that referenced this pull request Jul 1, 2020
…running

Set the monitor_running event to unblock the main thread

(cherry picked from commit 5aaa3a7)
@simaishi
Copy link
Contributor

simaishi commented Jul 1, 2020

Jansa backport details:

$ git log -1
commit 4cd1360df24adf9aa03bda874d9598f8abcadaff
Author: Oleg Barenboim <chessbyte@gmail.com>
Date:   Fri Jun 26 23:08:18 2020 -0400

    Merge pull request #506 from agrare/event_monitor_never_sets_monitor_running

    Set the monitor_running event to unblock the main thread

    (cherry picked from commit 5aaa3a7d8c61741185616f3f0d932edf9a788fc6)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants