-
Notifications
You must be signed in to change notification settings - Fork 0
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
Problems with conda-build #87
Comments
One idea I have for fixing this is to change our @hookimpl
def conda_session_headers(host: str) -> Iterator[CondaRequestHeader]:
"""Return a list of custom headers to be included in the request."""
try:
if context.plugins.anaconda_telemetry:
if host in REQUEST_HEADER_HOSTS:
yield from validate_headers(_conda_request_headers())
except Exception as exc:
logger.debug("Failed to collect telemetry data", exc_info=exc) Basically, we would just move accessing the |
I think that's just hiding the source of the problem. If conda-build isn't correctly initializing conda plugins, that's an issue. |
@travishathaway When looking at the traceback carefully, I wonder if it didn't set up the plugin setting hook implementation correctly, best would be to try to reproduce the conda build run on mac os to see if we can retrace this |
I have an additional observation that might help: this problem only seems to occur in the base environment. When I run the build in a separate environment, this goes away: conda/conda-standalone#125 This would explain why canary builds still work without problems. |
Here's an additional location we are seeing this error: |
Were you ever able to recreate this locally? I'm struggling with that at the moment. I have tested across most of the major platforms now ( |
Yes, I have on macOS 14. Steps to reproduce:
|
Strange, this only fails the first time. When I retry the build, the error does not occur. |
It seems fairly flaky. The tests fail after installing test dependencies with the following errors:
|
@travishathaway and I made some progress in debugging this and believe that it's related to the way conda loads plugin settings that depend on an import-time side effect accidentally and how conda-build calls conda-internal API. We have some ideas how to fix this in conda-build and maybe in a minor release for the plugin, and lastly how to make conda's plugin settings loading more resilient. |
This update to conda would fix this issue: I would still like to add a fix to this repository too though. PR incoming... |
Checklist
What happened?
The following issue was encountered on CI for conda-standalone:
https://github.com/conda/conda-standalone/actions/runs/12586646383/job/35080929499?pr=123
Conda Info
Conda Config
Conda list
Additional Context
There was another independent report of this bug that also encountered using conda-build on
osx-arm64
.Traceback
The text was updated successfully, but these errors were encountered: