-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add traversal paths #748
Conversation
Codecov Report
@@ Coverage Diff @@
## main #748 +/- ##
==========================================
+ Coverage 81.49% 81.76% +0.27%
==========================================
Files 17 17
Lines 1232 1212 -20
==========================================
- Hits 1004 991 -13
+ Misses 228 221 -7
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to add some test cases
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
traversal path should not be handled in CAS, user should first traverse and then send via client |
The executors in the CAS will then be uploaded to the hub. So I think the |
No description provided.