manuel

manuel closed issue JOJ/JOJ3#68

2025-05-29 13:50:58 +08:00

scoreboard and failed table refactoring and redesign

manuel commented on issue JOJ/JOJ3#68

2025-05-29 13:50:57 +08:00

scoreboard and failed table refactoring and redesign

probably not. i guess we can close now that we have joj-mon. reopen is necessary...

manuel commented on issue JOJ/JOJ3#78

2024-11-27 16:52:09 +08:00

heathcheck forbiden files

fixed, closing (heathcheck sensitive to "extra" spaces)

manuel opened issue JOJ/JOJ3#78

2024-11-27 15:51:06 +08:00

heathcheck forbiden files

manuel commented on issue JOJ/JOJ3-config-generator#8

2024-11-22 08:45:10 +08:00

Advanced documentation

document git lfs issue (as part of a FAQ?) (https://focs.ji.sjtu.edu.cn/git/JOJ/JOJ3/wiki/Gitea-tips-and-tricks-for-TAs)

manuel commented on issue JOJ/JOJ3-config-generator#8

2024-11-22 08:43:29 +08:00

Advanced documentation

doc on how to bind mount point extra dir in go-judge (eg. 477 latex / 482 lemondb)

/etc/go-judge/mount.yaml (warning: check weither /proc is needed or not)
adjust systemd config to…

manuel opened issue JOJ/JOJ3-config-generator#7

2024-11-17 09:36:09 +08:00

toml generation guidelines doc

manuel commented on pull request JOJ/JOJ3-config-generator#6

2024-11-12 14:01:12 +08:00

WIP: dev

any path in toml should probably be defined relative to /home/tt/.config/joj and be in a subdirectory. this is where all config must be. then they can specify projects/p2/.cang-tidy or…

manuel opened issue JOJ/JOJ3-config-generator#5

2024-11-02 16:05:26 +08:00

changes on conf.json format

manuel opened issue JOJ/JOJ3#72

2024-11-01 12:58:22 +08:00

more clangtidy checks

manuel commented on issue JOJ/JOJ3#71

2024-10-27 21:05:49 +08:00

JOJ3 result as issue comments

even for tt that will be easy to see the what happened along the way

manuel commented on issue JOJ/JOJ3#71

2024-10-27 21:05:17 +08:00

JOJ3 result as issue comments

yes that's the best

manuel commented on issue JOJ/JOJ3#71

2024-10-27 20:41:39 +08:00

JOJ3 result as issue comments

sounds like the best stragegy. 1 unique issue pr task with 1 comment (with its history)

manuel opened issue JOJ/JOJ3#71

2024-10-27 16:55:00 +08:00

JOj result as issue comments

manuel opened issue JOJ/JOJ3-config-generator#3

2024-10-26 12:46:24 +08:00

generate all config files

manuel closed issue JOJ/JOJ3-config-generator#1

2024-10-26 12:25:41 +08:00

meta config file format

manuel commented on issue JOJ/JOJ3-config-generator#1

2024-10-26 12:25:41 +08:00

meta config file format

outdated, closing

manuel closed issue JOJ/JOJ3-config-generator#2

2024-10-26 12:25:16 +08:00

Integration and enhancement on config generator development

manuel commented on issue JOJ/JOJ3-config-generator#2

2024-10-26 12:25:16 +08:00

Integration and enhancement on config generator development

should now be fine, closing

manuel commented on issue JOJ/JOJ3#68

2024-10-19 07:43:04 +08:00

scoreboard and failed table refactoring and redesign

that's why we need this issue: we have to first clarify where we want to go (what features to implement) before we start implementing anythng. this is especially important as it might involve…