Skip to content
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

[ safety ] Treat extra args in configs a bit smarter #271

Open
buzden opened this issue Nov 23, 2023 · 0 comments
Open

[ safety ] Treat extra args in configs a bit smarter #271

buzden opened this issue Nov 23, 2023 · 0 comments
Labels
problem Something isn't working

Comments

@buzden
Copy link
Collaborator

buzden commented Nov 23, 2023

See discussion in #270. We should treat single strings of extra configs as being able to pass several arguments, while disallowing unsafe things like leaving unescaped & and similar things. Simple stuff like splitting by a space can brake options containing spaces inside strings like "--opt1 --opt2=\"a b\"".

As an author of status quo, I'm going to think how can we sort this out in December, if no one would come with a solution earlier.

@buzden buzden added the problem Something isn't working label Jul 2, 2024
@buzden buzden changed the title [ safety ] Treat extra args in configs more smartly [ safety ] Treat extra args in configs a bit smarter Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
problem Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant