Skip to content

BUG: Negative Time Displayed in Submission Countdown Timer #4594

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

Open
RishabhJain2018 opened this issue Apr 16, 2025 · 6 comments · May be fixed by #4608
Open

BUG: Negative Time Displayed in Submission Countdown Timer #4594

RishabhJain2018 opened this issue Apr 16, 2025 · 6 comments · May be fixed by #4608

Comments

@RishabhJain2018
Copy link
Member

Description:

We encountered a UI bug where the countdown timer for the next set of submissions displays a negative value for seconds. This happened right after hitting the submission limit for the day.

Steps to Reproduce:

  1. Submit until the daily limit is reached.
  2. Observe the countdown timer for when submissions will be available again.

Expected Behavior:
The countdown timer should not display negative values. It should reset cleanly to 0 seconds or roll over appropriately.

Actual Behavior:
The seconds field briefly or persistently displays a negative number, e.g., -1 seconds.

Screenshot:
Image

@Amarta113
Copy link

Hello @RishabhJain2018 I'm new to this codebase, but I'm excited to give this a try. Let me know if that's okay!

@RishabhJain2018
Copy link
Member Author

Sure, please give it a try!

@Amarta113
Copy link

@RishabhJain2018 only the PR from the first contributor who commented is considered acceptable, but it looks like he made his submission without knowing that.

@Sekhar-Kumar-Dash
Copy link

Sekhar-Kumar-Dash commented Apr 21, 2025

@RishabhJain2018 only the PR from the first contributor who commented is considered acceptable, but it looks like he made his submission without knowing that.

@Amarta113 Sorry as this was not assigned to you and it was not solved i thought it would be fine if i take this one

@Amarta113
Copy link

Hi @Sekhar-Kumar-Dash, the issue was actually assigned to me. It seems you may have missed the earlier comment and the announcement in the channel:

Issues will be assigned on a first-come, first-served basis. The first person to comment on an issue will be assigned to it, and any other PRs for the same issue will be closed.
Please take only one issue at a time and focus on completing your assigned task before picking another.
There are plenty of issues available for everyone, so no rush—take it easy!

@Sekhar-Kumar-Dash
Copy link

hey @Amarta113 I get that . Actually i meant the issue is not assigned to you meaning this issue does not have any assignees thats the reason i got confused and thought this may be open for everyone.
My bad sorry again for this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment