Luca Wehrstedt

Note that we cannot use `do_not_specialize` to work around this because that argument is in fact a stride thus we _want_ it to be specialized!

@Jokeren if I set that value in the config it will be set both during benchmarking and during the "real" launch, right? What I want is to only set this...

I don't see how that would help: `do_not_specialize` only affects the `triton.jit` decorator, but my issue isn't about _compiling_ the kernel multiple times, it's about _running_ the kernel multiple times...

The automatic tagging doesn't seem to be working for the `tensorpipe` module: #37784 was tagged with `module: Tensorpipe` but neither I nor @beauby were tagged by the bot. Is it...

@mrshenli renamed the tag and made it lowercase and this fixed the problem, thanks!

> It should also be configurable when to do the rounding: for each subtask, for each task, for the whole contest... Specifying the contest-level rounding may not be that easy...

Well, surely not in cms.conf. There's no need to put them there and to force to restart the services in case these values change. It's enough to put them on...

Yes. You're proposing two score rounding rules, one at task-level (used to round the score of a user on a task, i.e. the the score of a submission) and one...

Partially fixed in c6ced820cb6744c773d3296ea3faa89c31b298f5. That is, rounding task- and contest-level scores works fine all across CMS (from CWS to AWS and RWS). The subtask/testcase/etc. rounding stuff is missing (the one...

At the IOI we were rounding the subtask scores to two decimal places, while the task- and contest-level scores were rounded to the nearest integer. (I already wrote that in...