An easier way to configure test cases

[undefined-moe]

config.json like this:

{
  "time":1,
  "memory":128000,
  "cases":10
}

And your file should be like this:

• 1.in
• 1.out
• 2.in
• 2.out
• ...
• 10.in
• 10.out

[twd2]

Why is this format necessary? Which OJ is currently using this format?
This format does not have any more feature compared with config.ini format.

[undefined-moe]

Some users just want to add config files easily.
And by adding this format,they don't need to copy&paste lines like
foo1.in|foo1.out|1|10|128000 or

- <<: *default
  input: bar1.in
  output: bar1.out

It allow users to config it easily.
Maybe I will add some extra features later.
e.g.

• search for input&output files automatically (without cases field required)
• support file prefix like foo.in foo.out

[twd2]

A better way may be enhancing the existing yaml format.

[undefined-moe]

Got it.
I'll make some changes later.

[undefined-moe]

Write config.yaml like this:

time: 1
memory: 128000
count: 10

[twd2]

Please add some necessary spaces.
And, please ensure your code can run before commit.

For example, i+'.in' should be str(i) + '.in'

[twd2]

These suggestions are about the code style, and, @iceb0y PTAL
BTW, we appreciated if you can give an example for each new format.

[moesoha]

Please mark conversation resolved immediately after you made some changes.

[moesoha]

Thanks for contribution!

[undefined-moe]

It seems that the problem is fixed now.

[twd2]

@iceb0y PTAL

[moesoha]

LGTM, @iceb0y review plz😭

[undefined-moe]

@iceb0y 😢 are you there?

[twd2]

PTAL @iceb0y , please

[iceboy233]

Instead of doing this, can you create a SDK to generate config file?

[twd2]

Creating an SDK to generate config files seems to be a new issue.
so, can I merge this PR?

[undefined-moe]

I've written an SDK.
But it seems that it will be more convenient as user can use the same .zip file for all oj.(like luogu,hustoj,qingdaou/onlinejudge)

[iceboy233]

Actually we have a luogu dev @moesoha here. What about create a common library for parsing and creating case packages? The library can be multi-language if needed. Note that we also had intention to move case storage to git repositories.

If we wanted to merge this alone, we need to refine both logic and implementation (as discussed in vijos-dev privately). For logic, we need to make "config file missing" = "empty config" = "scanning files in zip". For implementation, we should use names from canonical_dict instead of zip_file.

[undefined-moe]

You mean create a new repo for parsing packages?

[twd2]

Please refine both logic and implementation as @iceb0y said so that this PR can be merged.

[undefined-moe]

I don't understand what to do.

[twd2]

for filename in canonical_dict.keys():

[iceboy233]

This looks very slow. Consider using a expanding buffer (like c++'s std::vector).

Also str is unicode in python 3, but the byte to char conversion is not needed here.

[undefined-moe]

a,b is a int, so convert is needed.
These changes are not going to be merged now.
It's only a self-test as we also need to modify vj4/handler/judge.py & vj4/ui/templates/record_detail.html .