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

Precompilation IO issue #15

Closed
MilesCranmer opened this issue Mar 30, 2024 · 10 comments
Closed

Precompilation IO issue #15

MilesCranmer opened this issue Mar 30, 2024 · 10 comments

Comments

@MilesCranmer
Copy link

Seeing this message whenever I pre-compile micromamba_jll:

micromamba_jll Waiting for background task / IO / timer.
[pid 2148] waiting for IO to finish:
 Handle type        uv_handle_t->data
 timer              0x2b43820->0x7efe88aee5f0
This means that a package has started a background task or event source that has not finished running. For precompilation to complete successfully, the event source needs to be closed explicitly. See the developer documentation on fixing precompilation hangs for more help.

I'm not sure if this is the right repo to post this or not but thought I would just point this out if unaware.

@t-bltg
Copy link

t-bltg commented Apr 7, 2024

@MilesCranmer
Copy link
Author

Quick update — it looks like the actual code is here:
https://github.com/JuliaBinaryWrappers/micromamba_jll.jl/blob/main/src/wrappers/aarch64-apple-darwin.jl

not sure where to report this though.

@MilesCranmer
Copy link
Author

cc’ing @cjdoris just in case you aren’t getting notified on this repo.

I wonder if there’s a new Yggdrasil build script or something that deals with this sort of thing?

@cjdoris
Copy link
Collaborator

cjdoris commented Apr 7, 2024

Up until a few days ago, the micromamba_jll had not been rebuilt for about 9 months. So if this is a new issue then probably it is an upstream issue - in JLLWrappers maybe?

A few days ago (after you reported this issue) I triggered a new build of micromamba_jll just in case it helped. I suspect not.

@t-bltg
Copy link

t-bltg commented Apr 7, 2024

For reference, this only occurs on julia ≥ 1.10, see https://docs.julialang.org/en/v1/devdocs/precompile_hang.

@MilesCranmer
Copy link
Author

I've noticed this precompilation warning for micromamba_jll since the start of 1.10 but only posted the issue now because it is one of the few packages left still giving the warning. I think at the beginning of 1.10 there were a ton of packages with this warning (because people didn't realize such issues existed) but now there are only a couple left.

@cjdoris
Copy link
Collaborator

cjdoris commented Apr 9, 2024

Maybe try the tips in https://docs.julialang.org/en/v1/devdocs/precompile_hang to try and figure out where the issue lies?

@cjdoris
Copy link
Collaborator

cjdoris commented Apr 9, 2024

Here's what I get installing micromamba_jll into a new depot:

Precompiling project...
  5 dependencies successfully precompiled in 35 seconds
  1 dependency had output during precompilation:
┌ micromamba_jll
│   Downloading artifact: micromamba
│
│  [pid 1501] waiting for IO to finish:
│   Handle type        uv_handle_t->data
│   timer              0x1d34340->0x7f1084111ae0
│  This means that a package has started a background task or event source that has not finished running. For precompilation to complete successfully, the event source needs to be closed explicitly. See the developer documentation on fixing precompilation hangs for more help.
│
│  [pid 1501] waiting for IO to finish:
│   Handle type        uv_handle_t->data
│   timer              0x1d34340->0x7f1084111ae0
│  This means that a package has started a background task or event source that has not finished running. For precompilation to complete successfully, the event source needs to be closed explicitly. See the developer documentation on fixing precompilation hangs for more help.
└

What is suspicious to me is Downloading artifact: micromamba despite the fact that the artifacts are marked as lazy and so should not be getting downloaded here IIUC. Maybe there's some bug in the lazy artifacts logic?

@cjdoris
Copy link
Collaborator

cjdoris commented May 12, 2024

Just asked about this on Slack.

It’s a bug in Downloads.jl on 1.10 JuliaLang/Downloads.jl#234 (comment)

It’s fixed on 1.11+

On 1.10 any download leaves a worker running after it for a period of time in case another download needs it

https://julialang.slack.com/archives/C674ELDNX/p1715542984972079?thread_ts=1715542984.972079&cid=C674ELDNX

So it's an upstream issue. Closing as there's nothing to do from this end.

@cjdoris cjdoris closed this as completed May 12, 2024
@MilesCranmer
Copy link
Author

Ah gotcha. Thanks!

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

3 participants