Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
Race condition in CPU JIT configuration
We use pystencils in concurrent build steps (`ninja -j N`) to generate different kernels in parallel. Every once in a while our CI fails with the error ``` Traceback (most recent call last): File "/builds/hyteg/hog/generate_all_operators.py", line 33, in <module> from hog.cse import CseImplementation File "/builds/hyteg/hog/hog/cse.py", line 21, in <module> import pystencils as ps File "/builds/hyteg/hog/env/lib/python3.10/site-packages/pystencils/__init__.py", line 12, in <module> from .kernelcreation import create_kernel, create_staggered_kernel File "/builds/hyteg/hog/env/lib/python3.10/site-packages/pystencils/kernelcreation.py", line 10, in <module> from pystencils.cpu.vectorization import vectorize File "/builds/hyteg/hog/env/lib/python3.10/site-packages/pystencils/cpu/__init__.py", line 1, in <module> from pystencils.cpu.cpujit import make_python_function File "/builds/hyteg/hog/env/lib/python3.10/site-packages/pystencils/cpu/cpujit.py", line 236, in <module> _config = read_config() File "/builds/hyteg/hog/env/lib/python3.10/site-packages/pystencils/cpu/cpujit.py", line 197, in read_config loaded_config = json.load(json_config_file) File "/usr/lib/python3.10/json/__init__.py", line 293, in load return loads(fp.read(), File "/usr/lib/python3.10/json/__init__.py", line 346, in loads return _default_decoder.decode(s) File "/usr/lib/python3.10/json/decoder.py", line 337, in decode obj, end = self.raw_decode(s, idx=_w(s, 0).end()) File "/usr/lib/python3.10/json/decoder.py", line 355, in raw_decode raise JSONDecodeError("Expecting value", s, err.value) from None ``` My first guess is that this is a race condition between concurrent pystencils invocation. It tries to find a config file and if it does not exist, then creates it. There is a chance that the next build job (which we run in parallel) finds a partly written config file. IMHO pystencils should not write config files to disk automatically. Especially, considering that we do not even use the JIT. In any case, it should be robust to concurrent invocations.
issue