Tracing calls into OCP

[42sol-eu]

Hi @adam-urbanczyk,
we would like to suggest additional tracing / logging calls in this or another fitting library between CadQuery/Build123d and OCCT.
The idea is to catch and investigate strange behaviour in OCCT and getting good examples to either build OCCT fixes or improve the usage of CadQuery and Build123d.

I would be willing to support or contribute the work. I am able to do it in Python or C++ being a Software-Engineer since 20 Year.
My opinion is that it would be best done in Python though I am open for other suggestions.

The tracing and logging should be definitively default off and only be used if an error occurs.

What is you take on that?

Thanks for all your great work and contribution
Sincerely from Germany
Felix

[adam-urbanczyk]

Hi there, weird repo for this issue. If you need tracing in Python then use trace from the standard lib or something like this. Am I missing something?

[42sol-eu]

Hi Adam, you are right my issue is more a message than an issue.

We are trying to investigate some weird cases in the OCCT library where users reported cases of library failures.

On first glimpse the 'hunter' package could be exactly what we need.

I will investigate this further.
Thanks Felix

P.S. if you're interested in some of the details we created a occt channel on the CadQuery discord server

[adam-urbanczyk]

BTW: if you find OCCT issues, @lorenzncode has experience with submitting them to the OCCT tracker. AFAIR it is preferred to provide MREs with draw.exe and use .brep files to store the direct inputs.