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

Using repodata_fns? #338

Open
bollwyvl opened this issue Apr 25, 2023 · 0 comments
Open

Using repodata_fns? #338

bollwyvl opened this issue Apr 25, 2023 · 0 comments

Comments

@bollwyvl
Copy link

bollwyvl commented Apr 25, 2023

Thanks for boa!

I've been investigating using it in more places, and have found there are a few performance issues. The first that jumped out at me was that it didn't recognize my repodata_fns setting (to get repodata.json.zst). This traceback (from cancelling during a slow download) shows the code path that's probably involved:

 /env/lib/python3.11/site-packages/boa/core/solver.py:127 in __init__

   124 │   │   self.output_folder = output_folder or "local"
   125 │   │   self.pool = libmambapy.Pool()
   126 │   │   self.repos = []
 ❱ 127 │   │   self.index = load_channels(
   128 │   │   │   self.pool, self.channels, self.repos, platform=platform
   129 │   │   )
   130

 /env/lib/python3.11/site-packages/mamba/utils.py:129 in load_channels

   126 │   use_cache=True,
   127 │   repodata_fn="repodata.json",
   128 ):
 ❱ 129 │   index = get_index(
   130 │   │   channel_urls=channels,
   131 │   │   prepend=prepend,
   132 │   │   platform=platform,

Not sure whether it's the job of boa or a mamba to get that value from the config, but it's definitely noticeable during builds with lots of solves and channels.

Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant