The constgrep tool could probably be a bit faster. I'm not sure what's making it so slow at the moment. It shouldn't take ~2 seconds to look up a value.

$ time constgrep EPERM
#define EPERM 1
constgrep EPERM  1.12s user 0.43s system 88% cpu 1.751 total

https://github.com/picoCTF/picoCTF/blob/4755964b596bdfeea12bcec8ad508874e9e4e905/picoCTF-web/web/jsx/profile.jsx#L315
https://github.com/picoCTF/picoCTF/blob/55d51acfb688c3769beb888636b5c0ed3a502037/picoCTF-web/web/jsx/front-page.jsx#L797

This instruction text does not explain a concern due to identifier case-insensitiveness. For example, once the team name der Hacker is registered, all vari

Cirrus success styling on toasts looks really bad, but we should pass it in as toast({ type: 'success' }) to retain the semantic meaning.

To alleviate the styling issue, we should override the styles on the success Cirrus toast class with something that is not neon green.

We may need to refactor other parts of the codebase to pass in success for what is semantically a "success" too

Request for new feature: In the scoring configuration, add another section that you can define a penalty for wrong answers.

Describe the solution you'd like
GitHub Actions for the Project

Additional context
Recommend and add new GitHub actions, which this project can leverage use of.

References:

1. smaranjitghose/girlscript_chennai_website#160
2. https://github.com/smaranjitghose/girlscript_chennai_website/issues/122

It should just show a message stating there are no divisions. As of right now it throws a 500 error.

A docker Image would be nice

• Add new challenge
• Edit challenge
• Delete challenge
• Activate a challenge manual
• Deactivate a challenge manual
• Activate a challenge base on conditions
• Deactivate a challenge base on conditions