Giters
ProgSoc
/
FuzzJudge
Randomised input Judging server for ProgComp.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
2
Watchers:
3
Issues:
43
Forks:
ProgSoc/FuzzJudge Issues
websocket subscriptions, and 'diff' based updating
Updated
25 days ago
content negotation
Updated
a month ago
consider CORS issues for independently hosted clients
Updated
a month ago
alternate auth options (basic auth can be a bit hard to work around)
Updated
a month ago
file bug on zstd wasm dependency
Updated
25 days ago
graceful shutdown/restart for debugging - clients also need to handle dropped server
Updated
a month ago
add way to get fuzzjudge current git ref in code (and report to clients)
Updated
a month ago
manually judge ability
Updated
a month ago
(client): <pre><code> on validation errors
Closed
a month ago
Comments count
1
dump submissions
Updated
a month ago
websocket reconnect return missed messages
Updated
25 days ago
problem links broken in backend
Closed
a month ago
reorganise repo structure
Closed
25 days ago
Comments count
1
need to add in routes for problems (instead of catchall :id)
Updated
25 days ago
question updating
Updated
25 days ago
(server): send initial data on websocket connections
Closed
a month ago
(client): integrate with new scorebaord
Closed
a month ago
(server): correct asset links (potentially take raw markdown from server)
Closed
a month ago
(server): clock competitor backend
Closed
a month ago
(client): integrate with clock backend
Closed
a month ago
incorrect json mime type
Closed
a month ago
comp clock api design
Closed
a month ago
500 when GET http://localhost:1989/comp/prob/01-hello/judge
Closed
a month ago
(server): domjudge scoring & scoreboard backend
Closed
a month ago
admin account don't reset password on restart
Closed
a month ago
rate limit should respond with 429
Closed
a month ago
submission logging
Closed
a month ago
asset serving needs to be whitelisted
Closed
a month ago
user admin panel (backend)
Closed
a month ago
competition clock
Closed
a month ago
Comments count
1
Question numbers
Updated
25 days ago
Comments count
3
Scoreboard updates subscription system
Closed
a month ago
rate limiting
Closed
a month ago
settle on API user discovery
Closed
a month ago
Comments count
1
LaTeX rendering in markdown
Closed
a month ago
Comments count
1
(backend) better routing
Closed
a month ago
Comments count
1
inline asset and image support
Closed
2 months ago
test suite support
Updated
2 months ago
Goal: FuzzJudge as a Spec
Updated
25 days ago
allow for tests in problem descriptions
Updated
2 months ago
problem fuzz+solver description to allow for env vars + validator
Closed
2 months ago
template for sample problems
Updated
3 months ago
make exec section for problem config
Closed
3 months ago
Comments count
1