logging/src/lib.rs:46 and logging/src/lib.rs:48 will panic if an IO error occurs. Maybe consider to not panic and print another error to the console, informing about the writing problems, rather than crashing the program as logging is not a crucial feature for the program's functioning
logging/src/lib.rs:102 will panic if any code requests write-lock on config::CONFIG and then panics. Consider using Arc to ensure immutability and accessibility to the configuration from any thread at any time
It is mentioned here, that each level includes the previous ones, but including explicit ordinals is still a good idea.
I suggest some stability changes:
LogVerbosity doesn't specify values, but logging/src/lib.rs:75 assumes order -> Accidental reordering of the enum would lead to errors
…
Ich würde eigentlich auch lieber in Zukunft auf Gitea's eigenes CI/CD setzten, da das besser intigriert ist - wenn es denn nur vernünftig arm supporten würde.
Ja, wobei ich finde, dass…
fixed it :) (by restarting, which should not have worked but let's not worry about it)
It happens from time to time. Restarting once or twice always fixed it.
tf, you what now????? https://drone.libre.moe/KomuSolutions/WANessa/353/3/1
Just retry the pipeline once or twice.
Okay ich verstehe das aber irgendwie nicht. Es soll drone abloesen, hat aber noch nicht die gleichen Features und man kann darauf source code hosten? Ist das dann nicht basically gitlab? Ich…
are we sure that it really is using the same runner?
At least the amd64 should be the same, since my runner is not active anymore.