Mathias Nedrebø
Mathias Nedrebø
I also support this use case. With a big heterogenous runner pool (100+ runners with 2-64 core CPUs) with lots of label variations and attached HW it is very hard...
This feature would also be very valuable when using libraries with return codes/bools where you need to remember to check them all the time :sweat:
This is what we do in the official wrapper: * https://github.com/zivid/zivid-python#test-matrix * https://github.com/zivid/zivid-python/blob/master/.github/workflows/main.yml#L14 The main goal is to have one dimension per minor Python version per Win/Linux. Then we assume...
As you can see we are missing 3.9 on Linux, but that is tracked by https://github.com/zivid/zivid-python/issues/107.
I am not sure I understand correctly what you ask for, but you must install all headers to be able to lint. Code that cannot compile successfully cannot be analyzed.
Yes, I think you should first make all dependencies available in CI, then you don't need to do the weird workaround.
I think binaries should be distributed as part of SDK. That will make it easier for end users, which must install the SDK anyway to be able to run the...
This looks nice. We do not have a contributes agreement (CLA) in place for this repository. I will try to get one in place so we can process this PR....
Thanks for the reminder. I was in the process of implementing CLA, but got stuck with other tasks. I will resurrect the efforts here.
We'll also look into the CI error.