Remove mention of Downloads.jl having threading issues #594
Conversation
The mentioned issues are closed: - JuliaLang/Downloads.jl#110 (closed in Nov 2021 - JuliaLang/Downloads.jl#182 (closed in Apr 2022)
|
@ericphanson commented this 9 months ago in this commit. I think we should just need to test and confirm the usages here to make sure it works as intended? |
|
I think HTTP.jl v1 may also have fixed a lot of its concurrency issues. I myself haven't tried any threading experiments w/ HTTP.jl v1 or Downloads.jl on Julia 1.8 yet though, and haven't seen any discussion from other folks. But I think it makes sense to limit the warnings to talk about only HTTP.jl pre-v1.0 and Downloads.jl pre-julia-1.8 since there aren't open issues as far as I know w/ the newest versions. |
|
BTW I think it would be great to have some kind of open source example application demonstrating high throughput to s3 (or between ec2 and s3) w/ different object sizes and backends which could also be used as a smoketest here to check for concurrency issues/regressions/which versions actually work correctly, as well as to show known-good patterns for doing that through the julia ecosystem. |
|
Canceled. |
Co-authored-by: arnaudh <[email protected]>
The issues mentioned in the comment are closed, and seem fixed based on a cursory look at the comments there:
download()multi-thread error JuliaLang/Downloads.jl#110 (closed in Nov 2021)Is it fair to say Downloads.jl doesn't have threading issues anymore? I have zero knowledge around this, just trying to understand how safe it is to use this backend for our use case (at Invenia) where threading might be used.