-
Notifications
You must be signed in to change notification settings - Fork 132
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
TransactionScope enlistment regression in 1.20.2 #331
Comments
I didn't dig deep yet, but it appears that the issue is in version 1.20.2 and it's my fault. |
I've made draft PR #332 The example code runs as expected, jobs execute immediately.
I haven't checked it properly yet, unfortunately I don't have time right now. If someone could check, I would appreciate it. |
I don't think there's anything else to check. Code looks fine, tests are green, your own test shows the expected behavior like it was before the issue started. Unless you have some extra stuff planned for your draft, I'd say we merge it and publish. |
I will check the case with several workers now, because of which I initially made the changes. |
@azygis , quick tests in my multi-worker, multi-queue environment were successful as well: jobs executed immediately, and the count of fetching queries did not increase. I've removed the Draft label. |
Fix new jobs signalling in case of ambient transaction #331
@Tinyakov thanks for super quick resolution! |
Enqueuing a job inside a transaction scope no longer runs as expected after updating from 1.20.1 to 1.20.2.
It might be related to the following change:
Fixing Enqueued Job Trigger for Multiple Queues
Runnable example code:
Output with Hangfire.PostgreSql 1.20.2:
Output with Hangfire.PostgreSql 1.20.1 (runs as expected):
The text was updated successfully, but these errors were encountered: