| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
This looks like the axes have become linear?!? |
Sorry, something went wrong.
|
They haven't, but on such a small range they'll look linear (#8768 (comment)). |
Sorry, something went wrong.
|
+lots for this, but definitely an API change so should get a note! |
Sorry, something went wrong.
|
done |
Sorry, something went wrong.
|
putting on the backport queue, though not strictly necessary... |
Sorry, something went wrong.
|
Woops. API change note is not there. Did you forget to push? |
Sorry, something went wrong.
... by switching to AutoLocator when the minor LogLocator would produce no more than one tick.
|
Indeed, it got lost on the way. Fixed. |
Sorry, something went wrong.
|
Owee, I'm MrMeeseeks, Look at me. There seem to be a conflict, please backport manually. Here are approximate instructions:
$ git checkout v3.0.x $ git pull
$ git cherry-pick -m1 f0931295930b708cc32a8228430d5cbba991463a
$ git commit -am 'Backport PR #12865: Avoid 1-tick or 0-tick log-scaled axis.'
git push YOURFORK v3.0.x:auto-backport-of-pr-12865-on-v3.0.x
And apply the correct labels and milestones. Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon! If these instruction are inaccurate, feel free to suggest an improvement. |
Sorry, something went wrong.
|
@jklymak You labelled as 3.0.3. Any interest in backporting? I would be fine with just leaving it in 3.1 as it's not a regression. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
... by switching to AutoLocator when the minor LogLocator would produce
no more than one tick.
The examples below come from #8768, which this fixes.
PR Summary
PR Checklist