Albert Zeyer

For reference, one copy I found is via [pardata](https://pardata.readthedocs.io/en/latest/): https://github.com/CODAIT/pardata/blob/1d1600ad3eed6894da7dbddc451cd38aa03c770c/tests/schemata/datasets.yaml#L42C21-L42C99 But it's not exactly the same file (tar.gz instead of zip), but it looks like it has the same content...

I did not found the zip files anywhere. But I was using the tar.gz files instead which I linked above, which seem to contain the same content.

I think v2.13 was the last version with check_argument_types and check_return_type? I'm not affiliated with those projects, so I can only tell for myself why I don't like decorators: -...

On `dmesg`, some common errors: Very common: ``` [Jan28 18:18] pcieport 0000:80:03.0: AER: Corrected error received: 0000:80:03.0 [ +0.000013] pcieport 0000:80:03.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)...

> highly site-specific problem Is it? It might be specific to NVIDIA GPUs, and maybe also Linux, but this is rather generic then? > One problem that I see is...

> > Is it? It might be specific to NVIDIA GPUs, and maybe also Linux, but this is rather generic then? > > maybe someone who buys server-grade hardware does...

I just noticed, when I see the warning "Job marked as running but logging file has not been updated", that is when `task.running(task_id)` returns False. However, when the usage file...

As you see, this hangs in `ppid_map`. So I wonder now, maybe also in all the other cases when we see this warning "Job marked as running but logging file...

Hm, very strange, I then attached via `strace` to debug this further, and it said that the proc got a SIGSTOP? But from whom? Then, I send a `SIGCONT` to...

Again a hanging job. So, now debugging why I actually get the warning "Job marked as running but logging file has not been updated". Current procs: ``` % ps a...