Incompatible with conda-incubator/setup-miniconda@v2 GitHub Action

This is a terrific tool and have used it successfully in the past to debug some complex scripts. Had to debug a problem build recently, but as soon as I connect to the build server (via url link or direct ssh in a separate terminal), the connection is terminated in less than 60 seconds. Not sure if others have experienced the same.

If it helps, here are the key config elements I am working with:

jobs:
  build:
    name: Build (${{ matrix.os }})
    runs-on: ${{ matrix.os }}
    strategy:
      matrix:
        os: ["ubuntu-latest"]
        python-version: ["3.8"]
        
    steps:
      - uses: actions/checkout@v2
      - uses: conda-incubator/setup-miniconda@v2
        # https://github.com/marketplace/actions/setup-miniconda
        with:
          miniconda-version: "latest"
          channels: conda-forge
          auto-update-conda: true
          python-version: 3.8
          environment-file: environment.yml  
...
      # Debugging session
      - name: Setup tmate session
        uses: mxschmitt/action-tmate@v3

[gbarter]

If I do type -a tmate after miniconda it fails with /home/runner/work/_temp/b2117145-5a5a-4545-8e3d-34690dd3eb68.sh: line 1: type: tmate: not found

I will try your other debugging steps in a bit.

[dscho]

@mxschmitt figured out the root cause:

  // Bash profiles
  let bashExtraText: string = `
  # ----------------------------------------------------------------------------
  # Conda Setup Action: Basic configuration
  set -eo pipefail`;

This (along with other lines) will be appended to the user-wide Bash profile (i.e. to ~/.profile, but also to ~/.bash_profile, just to make sure).

The -e option, set via set -eo pipefail, is what is the bad thing here. It tells the Bash to exit whenever a command failed.