Situation

Current solution will block the server.

Situation

The most general type of special judge needs to execute the check program from the problem author. Also pipe their standard I/O.

Expectation

Include checker in the problem pack, unpack and execute it when judging. Define spec of checker.

Situation

There are many file operations in challenge modules. It's really dangerous and unnecessary to do these with root permission.

Expectation

Drop the permission at most of the time. Only escalate privileges as and when needed.

Situation

The rlimit settings for test programs are default values now.

Expectation

Change rlimit setting to proper values.

Situation

There is no disk quota limitation now.

Situation

Currently, we use prefetch to solve issue #4 , but it's a little ugly and not reliable.

Expectation

Control memory limit dynamically in light of OOM events and memory usage analysis.

Situation

Need Python 3 judge support.

Expectation

Accept comp_type = python for problem configuration.

在/etc/default/docker檔案中添加
DOCKER_OPTS = "--storage-driver=devicemapper"

Situation

Sometime we need CE message to debug.

Expectation

Provide C++, Python CE message with limited length.

High Restrict Mode

• Block clone, fork, vfork

Resource Limit

• Unlimited stack

Refactor

• Pointers of Sandbox are messes.

Situation

Dockerizing the project makes it easy to be deployed.

Expectation

Create Dockerfile.

Situation

The file operations may block the event loop, which causes the performance to drop.

I wish I can use unique strings as challenge ids.

Situation

Currently, different judge instances have to run in separate directories; otherwise, the file operations will be conflict.

Expectation

Create separate working directory for each instance.

Situation

judge will mount /dev to standard/container/udev, but won't umount. So it's dangerous to do file operation in standard/container even the judge is stopped.

Expectation

Umount standard/container/udev before the judge exited. Also do check and umount in the build-container.sh

Situation

There is only tornado default SIGINT handler now. Some environment changes need to be recovered after exit.

Expectation

Handle SIGINT, clean sandboxes and containers.

Situation

Different Linux distributions have different file path. And their compilers have different environment requirements.

Situation

If test program can fork or clone, it will cause multiple measurement issues.
Since there is no need of allowing test programs to multithread currently, denying these actions is a solution.

Expectation

Use seccomp to block fork, vfork, clone syscalls.

Situation

The default scheduler of Linux is not suitable for judge workloads.

Expectation

Config the scheduler to improve the judge performance.

Situation

The code of event loop is copied from old code, need to refactor.

Situation

The set of tests can be stopped early if any tests failed.

Expectation

Reduce the usage of time on fail tests.

Situation

Because creating a task costs lots of memory, the challenge requests from frontend must be queued first to prevent from resource exhaustion.

Expectation

Pend the request in a request queue, and limit the number of concurrent processing request.

Situation

"memory.max_usage_in_bytes" of cgroup includes the size of page cache consumed by the programs.
This will cause over-approximation of the memory usage.

請問ARG是什麼?
我在build時跑出了這樣的東西，請問如何解決?
INFO[0000] Unknown instruction: ARG

Situation

When the code contains UTF-8 character, the python judge will report runtime error.

出題者可以傳標程，自動計算適當的 time limit。

Situation

Any exception during challenge will abort the judge, then the running task count won't be decreased. Finally stuck the judge.

Expectation

Correctly handle exceptions.

Situation

git clone in the Dockerfile will clone newest version, not travis ci version.

Expectation

Clone $TRAVIS_COMMIT version in the Dockerfile.

Situation

Sometime, the first SIGCHLD signal of child process won't deliver to the judge.

Situation

The websocket API is internal now only for the Sprout OJ.

Expectation

Design the new high-level websocket API and publish.

Situation

For now, most of exceptions in python code are not handled. Specially, the exceptions thrown by Future need to be well handled.

Description

When an exception happens, the websocket wasn't closed by the server.
Hence the "frontend" may be kept waiting for a reponse indefinitely.

How to reproduce

Send a request to the server with an invalid "res_path" (e.g. mis-spelt pathname).