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

BB-680: Fun runner and Marathoner achievements are broken #982

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

mr-loop-1
Copy link

Problem

BB680 - Fun runner and Marathoner achievements are broken

Solution

The ticket mentions about how consecutive days are not being considered. I fixed that issue by generating a date series and then seeing where user's dates are being broken and counting upto that.

It looks like the ticket and associated github link were outdated as when I went to the actual fork to do the change, the issues was already fixed. But since I already spent time on it and it is more semantic and maybe efficient this way, hence raising this PR.

Areas of Impact

achievements where streak is a factor.

@mr-loop-1 mr-loop-1 changed the title Moved calculation to Postgres database BB680 - Fun runner and Marathoner achievements are broken Apr 3, 2023
@mr-loop-1 mr-loop-1 changed the title BB680 - Fun runner and Marathoner achievements are broken BB680: Fun runner and Marathoner achievements are broken Apr 5, 2023
@mr-loop-1 mr-loop-1 changed the title BB680: Fun runner and Marathoner achievements are broken BB-680: Fun runner and Marathoner achievements are broken Apr 5, 2023
@mr-loop-1 mr-loop-1 marked this pull request as draft April 6, 2023 09:56
@MonkeyDo
Copy link
Contributor

MonkeyDo commented Jun 6, 2023

Hi @mr-loop-1 !

You marked this PR as a draft, I was wondering if you wanted to discuss a way forward, if you had more things you wanted to add, or if I should test and review it.

Let me know :)

@mr-loop-1
Copy link
Author

mr-loop-1 commented Jun 26, 2023

Hi @mr-loop-1 !

You marked this PR as a draft, I was wondering if you wanted to discuss a way forward, if you had more things you wanted to add, or if I should test and review it.

Let me know :)

Hi @MonkeyDo

This pr was supposed to be my base for GSoC proposal. I was a bit late to the party (basically on the last day) and chose this open issue. I solved the issue but ended up not submitting my application.
I don't remember how extensively I tested the code but you may now review it.

Also, written above

It looks like the ticket and associated github link were outdated as when I went to the actual fork to do the change, the issues was already fixed. But since I already spent time on it and it is more semantic and maybe efficient this way, hence raising this PR.

@mr-loop-1 mr-loop-1 marked this pull request as ready for review June 26, 2023 12:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants