-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 crash from unexpected assignment #8839
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #8839 +/- ##
=======================================
Coverage 95.87% 95.87%
=======================================
Files 173 173
Lines 18508 18508
=======================================
Hits 17744 17744
Misses 764 764
|
π€ According to the primer, this change has no effect on the checked open source code. π€π This comment was generated for commit 5bdeb08 |
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.
Thanks @zenlyj!
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-maintenance/2.17.x maintenance/2.17.x
# Navigate to the new working tree
cd .worktrees/backport-maintenance/2.17.x
# Create a new branch
git switch --create backport-8839-to-maintenance/2.17.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e71f63b5ec623b5c128891453baf2bea63fa6eff
# Push it to GitHub
git push --set-upstream origin backport-8839-to-maintenance/2.17.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-maintenance/2.17.x Then, create a pull request where the |
(cherry picked from commit e71f63b)
Type of Changes
Description
A short fix for a rare case that causes a fatal error, due to illegal attribute access of the
AssignAttr
node.From my understanding, the relevant logic is supposed to check for the existence of an assignment that defines and uses the same variable, like
x = x
. LHS should always beAssignName
node.Closes #8754