Skip to content
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

Start-day jump can make yellow shading leak onto bad side of red line #230

Open
1 of 2 tasks
dreeves opened this issue Aug 16, 2021 · 2 comments
Open
1 of 2 tasks

Comments

@dreeves
Copy link
Member

dreeves commented Aug 16, 2021

Desiderata

Preview Give feedback

HT shanaqui who screenshotted this on one of their goals in the wild:

Replicata

  1. Create a new odometer goal with a starting value of 10 and rate of 1/day
  2. In the graph editor (static or dynamic), add a 2nd graph matrix row with the same date as tini and a value of 20
  3. Edit the final segment to continue at a rate of 1/day until an end value of 100

Expectata

Resultata


See leaky-yellow.bb in privatesuite. I can replicate this in production (both in pure-Beebody with the static editor, and in graph.beeminder.com) but not locally in dev.

UPDATE: also yellow_shading_wrong_side.bb

Things Nicky checked: rebraining doesn't fix, refreshing doesn't fix, incognito mode doesn't fix, logged in or out doesn't matter, admin or not doesn't matter.

Verbata: graph aesthetics, baneful bugs, leaky shading,

@dreeves
Copy link
Member Author

dreeves commented Nov 25, 2021

Another example -- leaky-yellow2.bb -- that leaks yellow in production (but not in dev):

image

@bsoule
Copy link
Member

bsoule commented Jun 10, 2022

ooh, i think that this latest bb file I just uploaded is an instance of this bug too:
https://github.com/beeminder/privatesuite/commit/c4e1b5c0fef18b4b904951c2eca58503a3bf192e
data/yellow_shading_wrong_side.bb

@dreeves dreeves changed the title Start-day jump => leaking yellow shading Start-day jump can make yellow shading leak onto bad side of red line Mar 1, 2023
@dreeves dreeves added cnr (closed as) could not reproduce and removed cnr (closed as) could not reproduce labels Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants