Ada Böhm
Ada Böhm
This is still implemented only for scheduler testing
I am quite confused what you want to achieve and I have feeling that storing closures in structs is not the right thing. After quick review, it seems to me...
Why you wanted to avoid it?
You can store a reference to the client in a session (with lifetime templates) and then compiler do the checks. But it would be little bit complicated to use such...
(1) It is ok, mut/non-mut in Rust is different concept than C++ const/non-cost. If it compiles and you do not use "unsafe" then it is safe:) (3) Dashboard is quite...
It is checked at runtime; multiple borrows causes panic, so it safe. If you want to continue, you can wrap build-in functions (e.g. concat). However, it still makes sense to...
Probably yes. I still would like to have something like matching logs stdout/stderr with monitoring events (e.g. to analyse that a task uses only 1 cpu after writing "xyz" on...
Hi, We are now implementing our dashboard. It will take some time to have production ready output, but we already have all information in the server as an event log,...
@giovannipizzi In general, multi-node ~~allocations~~ tasks are on our roadmap and we definitely want to include them in HQ, but it does not have a top priority for us right...
@giovannipizzi I am sorry, I used a wrong term in my previous text. We are supporting multinode (PBS/SLURM) allocations. What we are not supporting right now is multi-node tasks.