Nicky Gerritsen

> Probably we need to tell the user what length we expect when we present the form? Not reject it after submission with a surprise limit that was never communicated...

The spec says that you should specify the filename in the JSON/YAML: https://ccs-specs.icpc.io/draft/contest_package#file-references

I agree. I believe there is an undocumented agreement that the filename matching the property is the way to go, so that would be `problemset`.

Thanks! I wonder if waiting for an upstream fix is the best thing to do for now? Or alternatively, shall we specify a specific MariaDB version in the proposed docker...

From Googling, I found this: https://github.com/elkarbackup/elkarbackup/issues/581 > I stumbled into this problem when installing Elkarbackup on a QNAP NAS. To get rid of the error, i had to enable "advanced...

Very cool. I think @ubergeek42 is the person inside our team who is best to look into this.

> > @LDAP do you have any links to the DinD Judgehost replacement (Very intrested)? Does it need to run with a `--privileged` flag? > > Have a look at...

Well I think I am kinda lying. We *should* show two attempts, because we don’t want to let people know if one is a compiler error until we resolve. However...

I propose to maybe also look into making a Docker image with a checktestdata binary in it when we do static releases. I agree with the rest of your ideas