Skip to content

Don't export entire env? #318

Closed
#319
Closed
Don't export entire env?#318
#319

Description

@lilyminium
lilyminium
opened on Apr 21, 2026

Ah, would it be possible not to print out the entire env in the wrapper run scripts? (e.g.

forcebalance/src/data/runcuda.sh

Lines 123 to 129 in ec4c4de

echo "#=======================#"
echo "# ENVIRONMENT VARIABLES #"
echo "#=======================#"
echo
env
) This could be quite dangerous -- I just carelessly uploaded an npt.out file that wound up containing a github access token.

Activity

  1. leeping commented on Apr 21, 2026

    @leeping
    leeping
    on Apr 21, 2026
    Owner

    Sure, let's comment that out. It was only there for troubleshooting, as it can be hard to determine why a remote job isn't running properly.

  2. lilyminium commented on Apr 21, 2026

    @lilyminium
    lilyminium
    on Apr 21, 2026
    CollaboratorAuthor

    Awesome -- thanks @leeping! I just opened #319 to do so.

  3. leeping
    closed this as completedin #319on Apr 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions