-
Notifications
You must be signed in to change notification settings - Fork 748
[Bug] - Incorrectly handled absolute paths #1057
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
Draft
jakubno
wants to merge
18
commits into
main
Choose a base branch
from
bug-absolute-paths
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+222
−69
Draft
Changes from 15 commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
7d231e6
Add tests
jakubno 87e401c
Lint
jakubno 5acc917
wip
mishushakov be1dfd1
fixes absolute and ../ file upload (JS)
mishushakov 47b68ea
remove unused imports
mishushakov 42fd855
fixed python version
mishushakov 358f44e
format, lint
mishushakov 6bc2d0e
updated implementation
mishushakov 740df7d
uncommented
mishushakov 130fa0e
removed console.log
mishushakov 789c1a7
fixes python test
mishushakov 8270c49
fix python tests
mishushakov 98df64a
normalize relativized path
mishushakov c1df732
updated python test
mishushakov 77abafa
get all files in path, ignore root_dir when path is absolute
mishushakov a34000c
fixes js
mishushakov d7d5308
minor fix in src_path
mishushakov e2096cf
update test
mishushakov File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
JS sends unfiltered
filePathto backend, Python doesn'tThe JS
serializemethod passes the entirestepsarray directly to the API, including the newfilePathfield which contains the original absolute path and is of typePathLike(could be Buffer/URL). In contrast, Python's_serializeexplicitly constructs new step objects with onlytype,args,force,filesHash, andforceUploadfields, filtering outfilePathandresolveSymlinks. This inconsistency means the JS SDK sends potentially sensitive path information and non-stringPathLikeobjects to the backend that the Python SDK properly excludes.