评测机
Go to file
2019-12-30 19:32:17 +08:00
client update documentations 2019-12-30 19:32:17 +08:00
cmd/judge update documentations 2019-12-30 19:32:17 +08:00
data update documentation 2019-08-28 23:51:07 -07:00
file update documentations 2019-12-30 19:32:17 +08:00
judger update documentations 2019-12-30 19:32:17 +08:00
language add environment setting to language 2019-10-15 23:54:02 -07:00
pkg code cleanup 2019-12-26 21:23:20 +08:00
problem fixed typo 2019-09-07 18:03:19 -07:00
runner update documentations 2019-12-30 19:32:17 +08:00
taskqueue update design 2019-09-29 15:19:36 -07:00
types update documentations 2019-12-30 19:32:17 +08:00
.gitignore syzoj support demo.. 2019-12-25 21:54:55 +08:00
go.mod update documentations 2019-12-30 19:32:17 +08:00
go.sum update engine.io 2019-12-26 20:22:35 +08:00
LICENSE Initial commit 2019-08-24 15:32:38 -07:00
README.md update documentations 2019-12-30 19:32:17 +08:00

go-judge

Under designing.

The goal to to reimplement syzoj/judge-v3 in GO language using go-sandbox.

Planned Design

Container Root Filesystem:

  • necessary lib / exec / compiler / header readonly bind mounted from current file system: /lib /lib64 /bin /usr
  • work directory tmpfs mount: /w (work dir), /tmp (compiler temp files)
  • additional compiler scripts / exec readonly bind mounted: /c
  • additional header readonly bind mounted: /i

Brokers and interfaces:

  • client: receive pushed judge tasks from website (websocket / socket.io / RabbitMQ)
  • data: interface to download, cache, lock and access test data files from website by data_id
  • taskqueue: message queue to send run task and receive result (GO channel / (RabbitMQ, Redis))
  • file: general file interface (disk / memory)
  • language: programming language compile & execute configurations

Workers:

  • judger: execute judge logics (compile / standard / interactive / answer submit) and distribute as run task to queue
  • runner: receive run task and execute in sandbox (dumb runner)

Models:

  • JudgeTask: judge task pushed from website (type, source, data)
  • JudgeResult: judge task result send back to website
  • JudgeSetting: problem setting (from yaml) and JudgeCase
  • RunTask: run task parameters send to run_queue
  • RunResult: run task result sent back from queue

Utilities:

  • Config: read client config from TOML file
  • pkg/runner: run a group of programs in parallel

Planned API

Progress

Client is able to report progress to the web front-end. Task should maintain its states

Planned events are:

  • Parsed: problem data have been downloaded and problem configuration have been parsed (pass problem config to task)
  • Compiled: user code have been compiled (success / fail)
  • Progressed: single test case finished (success / fail + detail message)
  • Finished: all test cases finished / compile failed

TODO

  • syzoj problem yml parser
  • syzoj data downloader
  • syzoj compile configuration
  • file io
  • special judger
  • interact problem
  • answer submit
  • demo site

Done

  • socket.io client with namespace
  • judge_v3 protocol