cjc7373
cjc7373
> 比赛中的题目重测没有确定的逻辑，比如 先 wa（代码正确测试用例错误导致） 后来 ac （代码是错误，符合错误的测试用例） > > 这样更正测试用例之后，应该怎么处理这两次提交呢？ > > 如果有官方的重测逻辑，麻烦贴一下可以参考。 在domjudge中是可以选择是否重测已经ac的代码，在重测结束后可以选择是否保留重测结果。
I think this could be an opt-in feature. So people who enable it should have enough knowledge what they are doing and where to find their credentials.
Just out of curiosity, why moving from rst to markdown?
AFAIK the only way to fix this is to rewrite the whole history. Github/F-droid server has some git settings like `transfer.fsckObjects` set, so they run `git fsck` when reciveing/fetching objects,...
@kLiHz This simple fix just works fine.
I think what we need here is an endpoint from syncthing that returns every file matches the pattern `*.sync-conflict-*`. Maybe an extension of `/rest/db/browse`? I'll look into that.. And then...
Well I just tested that, and these events do emit for conflicted files, like: ``` [{ "id": 1418, "globalID": 1665, "time": "2023-03-12T01:22:58.620227647+08:00", "type": "RemoteChangeDetected", "data": { "action": "modified", "folder": "xxx",...
I have the same problem, and I also have `[cplayer] Run command: stop, flags=64, args=[flags=""]` in my log. I tried `--no-config` and it seems mpv no longer unexpectly exit. But...
I do have `mpv-mpris` installed. And this may explain why `--no-config` solves the problem (I only checked user script before and missed scripts installed by system package manager). I'll investigate...