-
Notifications
You must be signed in to change notification settings - Fork 36
Unvendor all libraries #120
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
Open
crusaderky
wants to merge
10
commits into
explosion:master
Choose a base branch
from
crusaderky:ft
base: master
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.
Open
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
11c9aa9
Unvendor libraries
crusaderky 11d63a2
Tweak msgpack
crusaderky 921ef77
Test that YAML is safe
crusaderky 8a5b00b
Test srsly.yaml_dump vs. arbitrary objects; clarify test_yaml_safe
crusaderky 6483817
Fix backwards compatibility imports
crusaderky d8b93b9
Reduce diff to test_msgpack_numpy
crusaderky f71c206
Reinstated bunch of tests
crusaderky 257f9f1
YAML test clarification
crusaderky 9940c65
BREAKING: Remove legacy embedded modules
crusaderky cfbd084
Tweak ccomment
crusaderky 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
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
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.
It would be a little more convincing if this test used
srsly.write_yamlorsrsly.yaml_dumpsinstead.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.
Neither of those functions, by design, allow you to serialize an arbitrary python object.
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.
A test demonstrating that would be more useful than what's here IMO. I searched and there are zero uses of
srsly.ruamel_yamlin the explosion stack outside srsly itself. Testing the public API is what's important.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.
This test does not test
srsly.ruamel_yaml.This test verifies that a YAML-legal malicious payload, which can only be crafted either with unwrapped
ruamel.yaml.YAMLor PyYAML, cannot cause arbitrary code execution insrly.yaml_load.I've now added a test that shows that you get a meaningful error message in
srsly.write_yamlwhen trying to write arbitrary objects, and removed the lines that useruamel.yaml.YAML()to load the payload back in order to prevent confusion.Are you suggesting to not introduce the dummy
srsly/ruamel_yaml.pyetc. backwards compatibiity modules, incurring in a slight risk that third-party packages may (trivially) break?