Hi Marc,
On 15-11-15 21:55, Marc Furon wrote:
Tobias Werth wrote:
Jaap was wrong. We follow the CLICS standard and do only support accounts for non-teams in the accounts.tsv. In these cases, the password is cleartext. (Although you might hack team password import into that function.)
However, you might do it the other way around: use the "manage team passwords" page to export a userdata.tsv for all teams (or teams without password) and use that file to set your passwords for the machines.
I worked around it another way--I imported all the accounts as jury accounts to get the account information in with passwords, then went into MariaDB and changed the account type to team. I then separately mapped the accounts to the teams inside MariaDB as well. That did the trick.
I believe that team user import capability should be provided as a standard feature.
Indeed, this is on our todo list.
I will also contribute my other modifications to the code base.
Patches are always welcome!
The Southern California regional contest was held yesterday and DOMjudge generally ran very well. There were just a couple of instances where a judgedaemon halted, generally after reporting that the chroot environment still had processes running when it was being stopped. I made sure the daemon was stopped, restarted it, and it seemed to recover properly in each case. The rest of the package worked flawlessly. Thanks again to the team for this contest control system!
This typically happens when a judgedaemon crashes on some issue. Were there any particular reasons, or did this seem to happen randomly?
I hope to see the development team in Phuket...
We hope to be there too! ;-) That's not confirmed yet, but we have good hope.
Best, Jaap