Skip to content

[Distributed] Return value obtained from call_on_owner directly#43398

Merged
Sacha0 merged 1 commit intoJuliaLang:masterfrom
krynju:kr/distributed-remote-fetch-fix
Dec 11, 2021
Merged

[Distributed] Return value obtained from call_on_owner directly#43398
Sacha0 merged 1 commit intoJuliaLang:masterfrom
krynju:kr/distributed-remote-fetch-fix

Conversation

@krynju
Copy link
Copy Markdown
Contributor

@krynju krynju commented Dec 11, 2021

Fixes #43396
Caused by this: #42339

v_local stores the value obtained through call_on_owner.

I forgot this value is not wrapped in Some and the code was attemptingto unwrap it with something at the end of the function.

Worked well for non-nothing values, but when fetch was actually returning a nothing value then an error was thrown due to something(nothing) being illegal

2nd test case is not related to the issue, but added it for safety in case there's any further work done on this part of code

Copy link
Copy Markdown
Member

@Sacha0 Sacha0 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superficially LGTM! Thanks for the amazingly rapid fix @krynju! :)

@DilumAluthge DilumAluthge requested a review from vtjnash December 11, 2021 17:38
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

Successfully merging this pull request may close these issues.

New PkgEval failures after merging #42339 ([Distributed] Worker local race condition between put! and fetch for Futures)

4 participants