Memory and output limits are not available through the API

[ningit]

Description of the enhancement request

Unlike the time limit, the memory and output limits of a problem cannot be obtained using the API. All of them are available via the web interface.

The methods of the API that return the time limit could also return the memory and output limits.

The goal you want to achieve

Obtaining the memory and output limits through the API.

Expected behaviour

The method api/v4/contests/{cid}/problems/{id} should return

{
  "id": "string",
  "time_limit": 1,
  "memory_limit": 1,
  "output_limit": 1,
  "etc.": "...",
}

instead of only time_limit. This also applies to api/v4/contests/{cid}/problems, the problems events of the event feed, etc.

Alternatively, these values could be made available using other specific methods.

[vmcj]

I've checked and time_limit is the only one which should be there according to the spec (https://ccs-specs.icpc.io/2023-06/contest_api#problems)

What is your use case for needing this data via the API (as it's another code branch so I would like a reasonable reason for adding it)?

[nickygerritsen]

The other two have never been specced. I don't see a real reason not to expose these, since they are shown on the team page (for memory limit) and in the documentation (for output limit).

[ningit]

What is your use case for needing this data via the API (as it's another code branch so I would like a reasonable reason for adding it)?

A tool that listens to the event feed of a contest and reruns RTE submissions with instrumentation in order to find out the reason for the runtime errors (among other things). We are starting using it in some undergraduate programming courses. The memory and output limits are used to execute the program in the same conditions.

Accessing them through the API is not strictly needed, we are already using web scrapping to obtain what is not available through the API (like the testcases). However, I suggested it as it may facilitate this and other similar use cases, and for completeness (indeed, we are only using the memory limit, not the output one).

[meisterT]

Interesting tool!

I think there is no reason not to expose them, I would use memory and output as key to match the problem.yaml keys: https://icpc.io/problem-package-format/spec/2023-07-draft.html#limits

[eldering]

Interesting tool!

I think there is no reason not to expose them, I would use memory and output as key to match the problem.yaml keys: https://icpc.io/problem-package-format/spec/2023-07-draft.html#limits

In the problem package format these are keys under a limit global key. In the Contest API, I think memory_limit and output_limit might make more sense. I'll put it on the agenda for the next meeting. I don't see a problem with adding it, but better have agreement with others so we don't later have to change it if it is added to the spec with a different name.