Releases: omegaup/omegajail
Releases · omegaup/omegajail
v3.8.6
enable parsy on python (#28)
v3.8.5
RIIR 🦀 (#19) This change rewrites omegajail in Rust. This is due to the fact that there are now some races with cgroups that we can't quite work around unless a slightly different architecture is used.
v3.8.4
Add the `omegajail-cgroups-wrapper` binary (#26) This change adds a new binary that can be called before the `omegaup-runner` such that it hs the correct cgroups setup for calling omegajail, in either cgroups v1 or v2.
v3.8.3
Support selecting the cgroup (#25) This change allows the runner to specify the cgroup path. This is a forwards-compatibility feature that allows the new version of omegajail (which is compatible with cgroup v1 and v2) to coexist with this version.
v3.8.2
Tweak the Go and JavaScript memory limits (#24) Turns out that Go wants to use a lot more address space to start. JavaScript has a very hefty VM that we need to account for.
v3.8.1
Allow `ioctl` to use the `TIOCGWINSZ` flag (#23) This is needed for Rust compilation errors.
v3.8.0
Fix release versioning (#21) This was broken when we renamed the `master` branch. Now it should work correctly. #none
v3.8.0-afb46cb
Allow Node.js to call `ioctl` to get the sound timer (#20) Although the call is `EPERM`ed. #patch
v3.8.0-cc0ce6d
Rootfs update This is a big #minor change. It updates: - Python3.9 - NodeJS 16 - Java 16 - Kotlin v1.6.10 - gcc-10 - Rust 1.56.1 - Go 1.18 (beta) - dotnet 6.0
v3.7.0
Improve the CPU-affinity-mask-setting code #minor (#16) This change stops inconditionally setting the CPU affinity mask to the first core, and instead chooses the first core that appears in the process' CPU affinity mask. This allows multiple instances of omegajail to run on different CPUs, if this is needed.