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

Lichess rating graphs are missing some days and all dates older than March 31st are wrong #15169

Closed
Alayan-stk-2 opened this issue Apr 29, 2024 · 0 comments · Fixed by #15179
Closed
Labels

Comments

@Alayan-stk-2
Copy link

Exact URL of where the bug happened

Any player's rating graph

Steps to reproduce the bug

  1. Go to any player rating graph that was updated after the 1st of April 2024
  2. Hover with the mouse to check out the rating graph rating/date
  3. Notice that the March 31st 2024 is missing
  4. Although that's not obvious, all the previous rating/date combos are wrong because the date are off. For example, the rating shown for March 30th 2024 is actually the rating for March 31st 2024

Another way to confirm the bug is:

  1. Find a player with a "best rating" date in some variant that's older than March 31st 2024.
  2. Check the rating graph and notice that the date associated with the rating record on the rating graph is wrong. Older records appear to be off by more days.

What did you expect to happen?

Correct dates

What happened instead?

See steps to reproduce

Operating system

Irrelevant

Browser and version (or alternate access method)

Irrelevant

Additional information

Likely related to the switch from winter time to summer time, which occurred on the day that's missing.

@Alayan-stk-2 Alayan-stk-2 changed the title Lichess rating graphs are missing some days and all dates older than the March 31st are wrong Lichess rating graphs are missing some days and all dates older than March 31st are wrong Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant