Wrap function callbacks
@robertgoss is already working on this.
Since Jul 16, 2020.
Assessment
This issue has not been assessed yet.
Description
Currently function callbacks are passed directly over the interface as arguments.
This leads to 2 issues:
- We cannot journal calls into these callbacks from within the implementation - which we would like to do in the future
- This does not follow the hourglass isolation pattern as an exception thown in the callback might not be safely able to percolate in the implementations code.
To get around this we should wrap the function call backs we are passed from the binding in the implementation.
- 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