A code sandbox implemented in Golang, aimed at providing a secure, reliable, and efficient containerized environment for running code. Developers only need to provide the programming language and code content to obtain the results of code execution. The underlying containers of this project use go-judge.
| Language | Version |
|---|---|
| C++ | 17 |
| C | 17 |
| Golang | 1.19 |
| Java | 17 |
| Python | 3.11.2 |
| JavaScript | 18 |
| TypeScript | 5.53 |
Clone the project:
git clone [email protected]:axliupore/judgeIn the root directory, run the following commands:
make all
make runOr use Docker without Nsq by simply running the following command:
docker run -d --privileged --shm-size=2048m -p 6048:6048 --name=judge trialoj/judge --http=6048If using Nsq, you need to specify where Nsq is running. By default, Nsq is placed on the host machine in this project:
docker run -d --privileged --shm-size=2048m -p 6048:6048 --name=judge --add-host="host.docker.internal:host-gateway" trialoj/judge --http=6048curl -X POST -H "Content-Type: application/json" -d '[{"language": "cpp", "code":"#include <iostream>\nusing namespace std;\nint main() {\ncout << \"judge\" << endl;\n}"}]' http://127.0.0.1:6048When using the nsq message queue for message passing, you need to create a producer to pass information to the consumer. The topic is judge_topic. To pass the code execution results using nsq, a parameter nsq must be passed to the consumer; otherwise, the code execution results cannot be received. Detailed code can be found here.
| Parameter | Description |
|---|---|
| Language | Code language, currently supported languages can be viewed in the judge directory |
| Content | File content |
| Input | Input content |
| CpuLimit | CPU time limit |
| MemoryLimit | Memory limit |
| StackLimit | Stack space limit |
| ProcLimit | Process count limit |
| Nsq | topic for the response information received by the producer when using the message queue |
| Parameter | Description |
|---|---|
| Code | Status code, viewable under pkg/status |
| Msg | Information about execution failures is stored here |
| Data | Response data for successful execution, such as execution time, output content, and memory usage |
In the development of this project, I would like to thank criyle for providing a lot of help. Without his assistance, this project would not have been realized.