Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I didn't look into the details, but I think
optimize_ticks
used to convert any input to Float64 when calculating ticks. This was changed in JuliaPlots/PlotUtils.jl#124 so a Float32 input now results in Float32 ticks. Occasionally ticks are off by a bit, e.g.This also happened before, but on the Float64 level.
Showoff.jl ignored the single bit differences in Float64, but not in Float32, so now we get long tick labels:
See JuliaGraphics/Showoff.jl#44
As a quick fix converting our ticks to Float64 before passing them should work.
Example from CI in #1512: (This is short_test_67.png)