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.

Sign up for GitHub

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

Jump to bottom

distributed=2022.6.0 used by v0.1.0 contains regression #306

Closed
hendrikmakait opened this issue Sep 5, 2022 · 1 comment
Closed

distributed=2022.6.0 used by v0.1.0 contains regression #306

hendrikmakait opened this issue Sep 5, 2022 · 1 comment
Labels
cause: upstream (dask) Upstream Dask issue (e.g. API breakage) regression

Comments

@hendrikmakait
Copy link
Member

In distributed=2022.6.0, a regression was introduced (dask/distributed#6624) that causes issues with map_overlap. This regression has been fixed in 2022.6.1 (dask/community#258 (comment)). I suggest a new minor release of coiled-runtime that bumps the version of dask and distributed.

XREF: This causes a newly created test for #305 to fail.
@hendrikmakait hendrikmakait added cause: upstream (dask) Upstream Dask issue (e.g. API breakage) regression labels Sep 5, 2022
@hendrikmakait hendrikmakait changed the title distributed version used by v0.1.0 contains regression distributed=2022.6.0 used by v0.1.0 contains regression Sep 5, 2022
@hendrikmakait hendrikmakait mentioned this issue Sep 6, 2022
Open
@ncclementi ncclementi mentioned this issue Sep 6, 2022
Closed
@hendrikmakait hendrikmakait mentioned this issue Sep 6, 2022
Merged
@ian-r-rose ian-r-rose mentioned this issue Sep 15, 2022
Closed
@jrbourbeau jrbourbeau mentioned this issue Sep 29, 2022
Merged
@ncclementi ncclementi mentioned this issue Nov 15, 2022
Merged
@ncclementi
Copy link
Contributor

Closing this as we are planning on releasing 0.2.0 soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cause: upstream (dask) Upstream Dask issue (e.g. API breakage) regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@hendrikmakait @ncclementi