fix(sweeps): sweeps schedulers handles multi word parameters #4640
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.
Fixes https://wandb.atlassian.net/browse/WB-11742
Description
We slightly modify an existing hack-y parameter ingesting mechanism to support multi-word params, exposed when pushing to a queue that had spaces in the name.
This does not solve the case where backslashes are in the name, we escape them properly on the backend, but then assume they are already escaped when printing, resulting in half as many backslashes. We should probably just tell users in the frontend they can't use backslashes. I don't think XSS is possible here but why would anyone want a backslash in the name if they weren't doing something nefarious?