Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Channel priority changed in 2.1.0 release
See original GitHub issueDistributed’s CI specifies the conda channels to use inside a conda environment file where we prefer to use conda-forge where possible and fallback to using defaults when needed.
After the setup-miniconda 2.1.0 release we started observing many more packages being installed from defaults instead of conda-forge (see the links below which compare the packages installed using setup-miniconda=2.0.1 and setup-miniconda=2.1.0). Was this an intentional change that requires users to make changes to our GitHub actions workflow?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
To be clear, we’re still using
setup-minicondabut are utilizing theuse-mamba, etc. settings you pointed out (the full set of changes we’re using as at https://github.com/dask/distributed/pull/4585/files)Welp, dunno if you’ve moved on entirely, but 2.1.1 now has fixed and under test. I’ll close this, please re-open if any related issues arise!