Skip to content

Regex escaping in job specification #34

@troycomi

Description

@troycomi

Working through some error reporting issues and I realized we don't escape any regex characters in the job specification. For example, a job specification like cmd.super would have the . match any character or find -name '*.out' | grep help would have issues possibly with the * and the | as they would be interpreted as regex characters.

I'm debating leaving that as a feature (something like \d+ could be useful) but probably safer to escape in the JobSpec initialization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions