feat(题目): 「运行例子」「自己输入」改用和提交同一台判题机——例子上跑出什么样,提交在这几个例子上就是什么样
Deploy / deploy (push) Canceled after 0s

原来试运行走另一台 Judge0:C 是 GCC 9、编译参数也不一样,Python 的语法错误回来的是运行错误,
没有题目的时间内存限制和代码模板,例子上的结果常和提交对不上。现在走本站判题机
(POST /trial-runs),同一套编译命令、这道题的限制和模板,对不对也由判题机比。

- 不落库、不算提交、不进判题队列:api 进程里自己排队,全站同时 TRIAL_CONCURRENCY 批
  (服务器 2、机房 4),每人最多两批,排满或等超过 30 秒就请学生过一会儿再点
- 死循环不停打印时判题机回包会很大,超过 16MB 就掐断,告诉学生输出太多、停不下来
- Python 语法错误用和提交一样的说明:第几行、中文标点标红、一键换成英文
- 运行时错误和提交用同一个解析,说清楚第几行、为什么(下标越界、int() 转换失败、段错误……);
  比赛里照旧只给按结果码的那一句
- 语法没过、服务没跑成时,标题不再说「N 个例子没对上」
- 后台「生成测试点」一并迁过来,编译警告不会再写进 .out;Judge0 的地址和调用全部删掉

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
xuyueandClaude Opus 5.5 committed 2026-09-29 08:09:44 +08:00
1 parent 8834536135
commit eb32676de4
27 files changed
+691 -169

No files matched your search

+22 -7
View File
@@ -25,7 +25,7 @@ import { readInfo } from "../services/test-case"
import { readFile } from "node:fs/promises"
import { resolve as resolvePath } from "node:path"
interface JudgeCase {
export interface JudgeCase {
cpu_time: number
memory: number
result: number
@@ -35,17 +35,17 @@ interface JudgeCase {
[key: string]: unknown
}
interface JudgeResponse {
export interface JudgeResponse {
err: string | null
data: JudgeCase[] | unknown
}
function statusValue(value: number): JudgeStatusValue {
export function statusValue(value: number): JudgeStatusValue {
const statuses = new Set<number>(Object.values(JudgeStatus))
return statuses.has(value) ? (value as JudgeStatusValue) : JudgeStatus.SYSTEM_ERROR
}
function templateForLanguage(value: unknown, language: string) {
export function templateForLanguage(value: unknown, language: string) {
const template = asRecord(value)[language]
return typeof template === "string" ? template : null
}
@@ -67,16 +67,18 @@ function astRulesForLanguage(value: unknown, language: string): AstRule[] {
/**
* `testCase` 是测试点目录名(正常判题),或者内联的测试点(诊断重跑,见
* diagnoseRuntimeError)。`output` 只在诊断时打开:它让判题机把每个测试点的
* diagnoseRuntimeError)。`output` 只在诊断和试运行时打开:它让判题机把每个测试点的
* 程序输出原样带回来,正常判题开着的话,死循环打印能把 worker 内存撑爆。
*
* 只发请求、不读响应体:试运行(judge/trial.ts)要边读边数字节,超了就掐断。
*/
async function requestJudge(
export async function postJudge(
language: string,
code: string,
timeLimit: number,
memoryLimit: number,
testCase: string | { input: string; output: string }[],
output = false,
{ output = false, signal }: { output?: boolean; signal?: AbortSignal } = {},
) {
const languageConfig = judgeConfigFor(language)
if (!languageConfig) throw new Error(`Unsupported judge language: ${language}`)
@@ -84,6 +86,7 @@ async function requestJudge(
const token = createHash("sha256").update(config.judgeServerToken).digest("hex")
const response = await fetch(new URL("/judge", config.judgeServerUrl), {
method: "POST",
signal,
headers: {
"content-type": "application/json",
"X-Judge-Server-Token": token,
@@ -106,6 +109,18 @@ async function requestJudge(
if (!response.ok) {
throw new Error(`JudgeServer returned HTTP ${response.status}`)
}
return response
}
async function requestJudge(
language: string,
code: string,
timeLimit: number,
memoryLimit: number,
testCase: string | { input: string; output: string }[],
output = false,
) {
const response = await postJudge(language, code, timeLimit, memoryLimit, testCase, { output })
return (await response.json()) as JudgeResponse
}