cubing / cubepb Goto Github PK

Here's a screenshot:

Specifically Safari. This is because not all browsers are able to parse dates in the Date constructor in the YYYY-MM-DD format.

HH:MM:SS.SSS

Suggested by Stone Amsbaugh on Discord

Like Megaminx LSLL, PLL Time attack, etc.

I'm documenting the infrastructure used by github.com/cubing project at https://github.com/cubing/infra , so that we we can pass on knowledge and access over time.

@big213, could I ask your help documenting infra info?
(Nothing about the hosting has to change, I'm just documenting what's where.)

From https://github.com/cubing/CubePB/blob/main/.github/workflows/frontend-deploy.yml it looks like this is hosted using Firebase. It doesn't seem to be in the shared cubing.org project on Google cloud, so I presume it's in a separate project?

Here's a rundown of this bug as best as I can.

I set 2 PBs on 4x4 in the same day. The times are 1:19.25 followed by a slightly faster 1:19.07. I try to save them and get this exact error message:

GiraffeqlBaseError: Score must be worse than future scores.

It lets me save the PB as happening tomorrow but I'm unable to save them on the same day.

• Ability to flag a user as featured
• Ability to view featured users (who also must be public users)

These PBs would be 100% customizable, event names would be stored as string, and would only be visible to the current user

Suggested by Oxzowachi on Discord

To better describe what exactly the event is

like MM/DD/YYYY, suggested by BlueAcidball on discord

Suggested by eff on Discord

This is for FMC averages and means. May consider storing it in the same manner as time_elapsed (as 1000 x actual moves count), or as a decimal with up to 2 decimal places.

Requested by Stone Amsbaugh on discord

Entry of an invalid time like 1:75.123 currently passes the regex check when it should not.

Requested by Tazzlyn on Discord

Possible ideas:

• if enough people flag a PB as suspect, it will automatically be sent for review and hidden
• Moderators have the ability to flag a PB as suspect

First reported by eff on discord

There's an oauth url with a scope defined in a few places in this repo:

• https://github.com/cubing/CubePB/blob/6f8d7a584eed59be26a4dc562fce5fb7c1f83ef0/frontend/.env.example
• https://github.com/cubing/CubePB/blob/e80625da5de3f275cc43cee8113308af5e83d703/.github/workflows/build-frontend.yml
• https://github.com/cubing/CubePB/blob/99c192a881601878c369ba395c3ae95740d141d3/.github/workflows/frontend-deploy-alpha.yml
• https://github.com/cubing/CubePB/blob/d4a6fa3f31f22228a2c2a034d71aab91fc34c084/.github/workflows/frontend-deploy.yml

All of those have scope=public+dob+email+manage_competitions. Do you really need dob and manage_competitions? If you do, it would be nice to have an explanation of why when I log in.

Neat project, btw! I look forward to learning more about it =)

This will prevent issues of users trying to enter . and : and instead throwing off the auto-formatter for that text box.

First reported by Stone Amsbaugh (2018AMSB02) on Discord

For example, 1:05.28 will fail the regex and not be allowed to submit.

Reported by Tfresh on Discord

Dependent on this PR being merged: cubing/icons#67