Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Don't manually invalidate cached lines in _update_transScale. #24654

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
Dec 7, 2022

Conversation

anntzer
Copy link
Contributor

@anntzer anntzer commented Dec 7, 2022

Resetting transScale just above will invalidate any nodes that depend on it as well. (The manual line invalidation came in in ff3c65f to "fix log/linear toggle", but that toggle clearly works fine even with this removal; I assume that transform invalidation became better since then.)

PR Summary

PR Checklist

Documentation and Tests

  • Has pytest style unit tests (and pytest passes)
  • Documentation is sphinx and numpydoc compliant (the docs should build without error).
  • New plotting related features are documented with examples.

Release Notes

  • New features are marked with a .. versionadded:: directive in the docstring and documented in doc/users/next_whats_new/
  • API changes are marked with a .. versionchanged:: directive in the docstring and documented in doc/api/next_api_changes/
  • Release notes conform with instructions in next_whats_new/README.rst or next_api_changes/README.rst

Resetting transScale just above will invalidate any nodes that depend on
it as well.  (The manual line invalidation came in in ff3c65f to "fix
log/linear toggle", but that toggle clearly works fine even with this
removal; I assume that transform invalidation became better since then.)
@ksunden ksunden added this to the v3.6.3 milestone Dec 7, 2022
@ksunden ksunden merged commit 85b1874 into matplotlib:main Dec 7, 2022
@lumberbot-app
Copy link

lumberbot-app bot commented Dec 7, 2022

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

  1. Checkout backport branch and update it.
git checkout v3.6.x
git pull
  1. Cherry pick the first parent branch of the this PR on top of the older branch:
git cherry-pick -x -m1 85b1874b0b7ed843329f962ed59d71c106da349f
  1. You will likely have some merge/cherry-pick conflict here, fix them and commit:
git commit -am "Backport PR #24654: Don't manually invalidate cached lines in _update_transScale."
  1. Push to a named branch:
git push YOURFORK v3.6.x:auto-backport-of-pr-24654-on-v3.6.x
  1. Create a PR against branch v3.6.x, I would have named this PR:

"Backport PR #24654 on branch v3.6.x (Don't manually invalidate cached lines in _update_transScale.)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the Still Needs Manual Backport label once the PR gets merged.

If these instructions are inaccurate, feel free to suggest an improvement.

@anntzer anntzer deleted the utsl branch December 7, 2022 17:54
rcomer pushed a commit to rcomer/matplotlib that referenced this pull request Dec 10, 2022
…in _update_transScale

Manual backport required due to simple conflict caused by the
first removed line being different in main and v3.6.x, having
previously been modified at matplotlib#24634.
oscargus added a commit that referenced this pull request Dec 10, 2022
Backport PR #24654: Don't manually invalidate cached lines in _update_transScale
@ksunden ksunden mentioned this pull request Feb 20, 2023
6 tasks
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.

4 participants