The code from https://cp-algorithms.com/graph/push-relabel.html doesn't work.
Very easy to see that it is buggy, since the code doesn't use the target vertex t at all.

Description: Task and contest configuration file lack documentation

I am not able to find a complete specification of the configuration files for tasks and contests in YAML format (italy_yaml).

Looking at the examples in the test contest repository - such as con_test/batch/task.yaml - there is no information.

Here'

The current test suite in webapp/tests/ is a start but not very satisfactory.

Some ways to improve:

• Remove duplication between the tests and clean them up
• Create a good clean template to test e.g. jury interface functionality that can easily be populated for the various data types;
• Add tests using said template;
• Add tests for the API

I have written two pages in Japanese.

• https://online-judge-tools.readthedocs.io/en/master/introduction.ja.html
• https://online-judge-tools.readthedocs.io/en/master/run-ci-on-your-library.html

These documents should be translated to English.

Hi friends, since many of you are starting to contribute for Hacktoberfest.

To not disallow beginners to contribute to the project, this issue can be taken up by anyone starting to learn data structures and algorithms.

You need to start solving the problems in the Hackerrank's Tracks and add your solutions in the branch named trackname in a new f

Is your feature request related to a problem? Please describe.

More flexible head comments (like adding current time and so on).

Describe the solution you'd like

Set some identifier. When the template was loaded, replace the identifier (like the template of cf-tools).

This would allow a user's choice to persist across browsers, cookie clears, etc.

Use https://github.com/stopstalk/stopstalk-deployment/blob/79911cdaf9e8ff0da963d044b286893144b189ec/modules/sites/codechef.py#L204 to replace
https://github.com/stopstalk/stopstalk-deployment/blob/79911cdaf9e8ff0da963d044b286893144b189ec/modules/sites/codechef.py#L139

We sometimes want to run tests which are not associated to specific problems (e.g. generating inputs using srand() and rand(), and check the output with assert()). For this, we can use Hello World as a dummy problem.
However, this technique is not trivial, so we should print hint messages when test files with no PROBLEM