Skip to content

issues in batch connect when run_script isn't executable. #948

Description

@johrstrom

What problem does this solve? Please describe.

In batch connect if the run_script isn't executable, it will fail to run.

It's this line here.

Describe the solution you'd like

This should likely chmod +x the file isn't executable so that we can correctly execute the file.

Describe alternatives you've considered (optional)

We could source it if it isn't, but I don't know the difference between source and ./ to really understand if it'd be better or now.

Additional context
None.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Fields

    Priority

    Low

    Effort

    Light

    Impact

    Limited

    Source

    Maintainers

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions