Error string propagation for global methods
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by tracing RegisterErrorMessage on the base class and the CWrapper handling for global methods such as CreateApp. Confirm how exceptions are caught on the component side and wrapped by the bindings; the work is done when global-method exceptions propagate their error strings through the bindings like component-method exceptions.
Written by the indexing model from the issue text.
Description
Currently, the error string propagation works by calling RegisterErrorMessage on the base class whenever an exception is caught on the component side, which is then propagated to the binding and wrapped into a new exception.
This doesn't work for the global (CWrapper) methods, as there is no base class instance to register the error message on.
We ran into this issue as our "application" object is created and initialized using a global CreateApp method, which was throwing a std::exception due to missing runtime libraries. I would suggest to add the same mechanism to the CWrapper class so it too can propagate error messages.
- Dominant language
- Go
- Stars
- 54
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Contributor guide
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 Autodesk/AutomaticComponentToolkit
-
Autodesk/AutomaticComponentToolkit#226 · 5 comments · 3 reactions · 3 assignees ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Autodesk/AutomaticComponentToolkit#213 · 1 comment · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Autodesk/AutomaticComponentToolkit#188 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Autodesk/AutomaticComponentToolkit#183 · 1 comment ·
-
Autodesk/AutomaticComponentToolkit#162 · 1 reaction · 2 assignees ·
All issues in Autodesk/AutomaticComponentToolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NVIDIA/gpu-operator#2955 ·
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 90/100
cisagov/vulnrichment#337 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100