Tracing calls into OCP
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- observability, tooling
Research direction
No files, tests, or entry points are identified. Start by mapping the CadQuery/Build123d-to-OCCT boundary and reviewing existing logging or tracing facilities, then agree on the scope, default-off behavior, and diagnostic output needed before defining completion criteria.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- C++
- Stars
- 200
- Forks
- 48
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CadQuery/OCP
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Python 3.14t buildOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
OCCT8
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
tensorflow/tflite-micro#3784 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agentic-workflows automation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tenstorrent/tt-metal#57946 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aristocratos/btop#1857 ·
Maintainers usually reply within 3 days