Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channels added twice #57

Open
dopplershift opened this issue Jul 26, 2020 · 2 comments
Open

Channels added twice #57

dopplershift opened this issue Jul 26, 2020 · 2 comments
Labels
type:bug Something isn't working

Comments

@dopplershift
Copy link

I'm seeing channels being added twice with this action, once under:

# Applying conda configuration...
#################################

and another under:

# Applying conda configuration after update...
##############################################

This results in warnings:

C:\windows\system32\cmd.exe /D /S /C "C:\Miniconda3\condabin\conda.bat config --add channels conda-forge"
##[warning]Warning: 'conda-forge' already in 'channels' list, moving to the top

Warning: 'conda-forge' already in 'channels' list, moving to the top
C:\windows\system32\cmd.exe /D /S /C "C:\Miniconda3\condabin\conda.bat config --add channels conda-forge/label/testing"
##[warning]Warning: 'conda-forge/label/testing' already in 'channels' list, moving to the top

Warning: 'conda-forge/label/testing' already in 'channels' list, moving to the top

The problem is that these warnings appear in the top-level output of my workflow, which is kinda of annoying since they will never go away. Here's my config if it helps:

    - name: Set up Python ${{ matrix.python-version }}
      uses: goanpeca/setup-miniconda@v1
      with:
        auto-update-conda: true
        miniconda-version: "latest"
        python-version: ${{ matrix.python-version }}
        channel-priority: strict
        channels: conda-forge/label/testing,conda-forge
        show-channel-urls: true
        use-only-tar-bz2: true
@goanpeca
Copy link
Member

Hi @dopplershift, thanks for the report.

Yes, it is indeed something I added to ensure things worked properly (that is why the title say after update).

I could add an extra check to avoid the warning.

@dopplershift
Copy link
Author

Well personally I'd love to have the option to make things quiet.

Btw, I really appreciate having this action available. It saved me a ton of effort.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants