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
Fix UnboundLocalError when running celery worker in foreground #6833
Conversation
This pull request introduces 1 alert and fixes 1 when merging 7b1647d into 171ab02 - view on LGTM.com new alerts:
fixed alerts:
|
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.
Whoops, looks like a conflict resolution mistake when backporting 6e5580 onto the 5.0 release branch (as 56a6246). Those two commits should be pretty much identical but the merge from master into #6599 probably confused things.
lgtm! Thanks for the PR @michael-k. Leaving for @thedrow to merge due to the pending review or I'll aim to come back and hit the button myself later today.
Interesting that I can't seem to start the unit test checks on this PR... I assumed it was because @michael-k might be a first time contributor but that's not the case :/ Perhaps we need to amend to workflow rules to match our stable/release branch names as well? |
yup |
I have updated the workflow. |
There are no new commits in branch Edit: I've recreated the commit to trigger a new workflow run. |
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.
needs another rebase
Rebase onto what? Before I can rebase, you need to push something to branch |
This pull request fixes 3 alerts when merging 3927a84 into 171ab02 - view on LGTM.com fixed alerts:
|
Yes I should have cherry-picked it myself.🤦 Sorry. |
CI will run now in this branch. |
The CI still isn't running so this needs more work. I'll keep you posted. |
Codecov Report
@@ Coverage Diff @@
## 5.0 #6833 +/- ##
==========================================
- Coverage 75.42% 75.41% -0.02%
==========================================
Files 138 138
Lines 16418 16422 +4
Branches 2050 2050
==========================================
+ Hits 12384 12385 +1
- Misses 3818 3821 +3
Partials 216 216
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This pull request fixes 1 alert when merging cd61c10 into b221d69 - view on LGTM.com fixed alerts:
|
Looks like the CI failures are unrelated to this diff. Also the pre-commit job put a huge, nasty style commit on the end of this PR which should be sorted out on 5.0 (or master and cherry picked back) rather than here. py10 failure
Hmm, I think this should be pypy3 failure
Seems like we need 6c8c93c, which was part of the #6635 diff to get CI working of pypy3. The squashed merge commit is 117cd9c and should probably be cherry picked onto the 5.0 branch and then have this rebased on top. lint failure
lint failureIt's trying to run under python3.7 which isn't available in the job environment. Surprising, I thought the lint job was supposed to run using tox in a python3.9 environment. |
for more information, see https://pre-commit.ci
This pull request introduces 1 alert and fixes 1 when merging fb6b8a6 into b221d69 - view on LGTM.com new alerts:
fixed alerts:
|
@maybe-sybr Thanks for helping me with the investigation. ❤️ |
Description
Add the indentation missed in commit 56a6246. The bug is not present in branch
master
.Fixes #6830