Hi all,
I finally got around fixing https://github.com/DOMjudge/domjudge/issues/310 which caused the latest 5.2.1 and 5.3.1 releases to break.
So we now have bugfix releases 5.2.2 and 5.3.2 available to correct this and also #311 and a small documentation improvement.
Download as usual at https://www.domjudge.org/
Best,
Jaap
On 07/11/17 23:13, Jaap Eldering wrote:
> Hi all,
>
> This is to warn that the 5.3.1 and 5.2.1 releases from a few days ago are broken due to a regression bug in runguard: https://github.com/DOMjudge/domjudge/issues/310
>
> We're still investigating the precise cause before releasing a fix. As a workaround we recommend using 5.3.0 instead of 5.3.1, since the actual changes (besides this bug) are minimal. For 5.2.1 the changes are _slightly_ larger, but we still recommend downgrading to 5.2.0, or alternatively, revert
>
> https://github.com/DOMjudge/domjudge/commit/bbd05895d83cff22b374a30e749e49c…
>
> and apply the patch
>
> https://github.com/DOMjudge/domjudge/commit/9bad6d6dd02542ebbfbccfa0115217d…
>
>
> Sorry for the inconvenience!
>
> Jaap
>
>
> On 03/11/17 00:12, Jaap Eldering wrote:
>> Hi all,
>>
>> We released (minor) bugfix releases 5.1.4, 5.2.1 and 5.3.1 for all current branches. Download as usual at https://www.domjudge.org/
>>
>> These various fixes from the last few weeks, including:
>> - Fix runguard reusing cpuacct cgroup potentially giving wrong runtimes.
>> - Increase length of auditlog.action DB column, fixing SQL error when updating some configuration settings.
>> - Fix testcase download filename.
>> - Various small documentation fixes.
>> - Fix display of user IP address on jury interface.
>> - Fix automatic setting of clarification category in jury interface.
>> - Delete team scoreboard cache data when deleting a team.
>>
>> This also marks the end of life of the 5.1 branch. We recommend upgrading to either of the 5.2 or 5.3 branches.
>>
>> Best,
>> Jaap
>>
>
>
>
>
