cms-dev / cms-dev/cms

Provide a tool to check whether tokens have been played correctly

Open
#233 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
1k
Forks
412
Avg merge
6d 10h
Merged PRs (30d)
3

Description

When messing up with timings and token parameters during a contest (which you shouldn't do, but sometimes are forced to), you may end up in a situation in which a token have been played in a moment when retrospectively the user didn't have it available. This may lead the contest to be unfair towards certain users.

It would be nice to provide a tool in AWS that contest administrators can use to check whether there are tokens that are not legal (and which are they).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing how contests record token timings and token parameters, then determine where an AWS administrator tool could inspect those records. Done means the tool identifies tokens that were played when the user did not legally have them available; the issue names no files, tests, or entry points.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, python
Domain
backend, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.