Skip to content

Conversation

@nickygerritsen
Copy link
Member

I'm open to discussing these changes, since they might not be preferred by everyone.

I am in favor of the first change for sure (since teams could measure this on their own machine anyway). The second might be more controversial.

This was requested at SEERC and I think it makes sense in general.

Also updated the logic to only show these limits when `show_limits_on_team_page` is set.
Algotester does this so we needed it for SEERC and I think having this as an option can make sense.
<th>Runtime</th>
<td>{{ judgingRun.runtime }} sec</td>
</tr>
{% if showLimits %}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer to not have this option, and first come up with a good reason why this shouldn´t be public.

If there is a good reason we should also add tests for this to make sure that we don´t expose that information, for now I miss the change to also expose this in the API to keep those in line.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine always doing it but if we have that setting for limits turned of I think it's weird.
As for the API, I'm fine adding the memory limit there as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants