Skip to content

Rename one method of run_work_thunk() to run_work_thunk_remotevalue(); this fixes a JET error around matching methods for run_work_thunk(...)#181

Merged
DilumAluthge merged 1 commit intomasterfrom
dpa/run_work_thunk_rv
Feb 21, 2026
Merged

Rename one method of run_work_thunk() to run_work_thunk_remotevalue(); this fixes a JET error around matching methods for run_work_thunk(...)#181
DilumAluthge merged 1 commit intomasterfrom
dpa/run_work_thunk_rv

Conversation

@DilumAluthge
Copy link
Copy Markdown
Member

@DilumAluthge DilumAluthge commented Feb 21, 2026

This fixes the following JET error:

┌ run_work_thunk(rv::Distributed.RemoteValue, thunk::Bool) @ Distributed /workpath/Distributed.jl/src/process_messages.jl:79
│ no matching method found `run_work_thunk(::Bool, ::Bool)`: Distributed.run_work_thunk(thunk::Bool, false)
└────────────────────

This is an alternative to #168 (closes #168).

I like this better, because it makes the code a bit easier to read by making it more clear which method you're actually calling.

I searched the Julia manual and found no results for run_work_thunk, so I think this is not public API, and thus I think we're allowed to change it.

…e()`; this fixes a JET error around matching methods for `run_work_thunk(...)`

This fixes the following JET error:

```
  │┌ run_work_thunk(rv::Distributed.RemoteValue, thunk::Bool) @ Distributed /workpath/Distributed.jl/src/process_messages.jl:79
  ││ no matching method found `run_work_thunk(::Bool, ::Bool)`: Distributed.run_work_thunk(thunk::Bool, false)
  │└────────────────────
```
@DilumAluthge DilumAluthge changed the title Rename one method of run_work_thunk() to `run_work_thunk_remotevalu… Rename one method of run_work_thunk() to run_work_thunk_remotevalue(); this fixes a JET error around matching methods for run_work_thunk(...) Feb 21, 2026
@DilumAluthge DilumAluthge marked this pull request as ready for review February 21, 2026 05:48
@codecov
Copy link
Copy Markdown

codecov bot commented Feb 21, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.45%. Comparing base (d06aa73) to head (5fc61b4).
⚠️ Report is 3 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #181   +/-   ##
=======================================
  Coverage   79.45%   79.45%           
=======================================
  Files          10       10           
  Lines        1957     1957           
=======================================
  Hits         1555     1555           
  Misses        402      402           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Member

@JamesWrigley JamesWrigley left a comment

Choose a reason for hiding this comment

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

LGTM!

@DilumAluthge DilumAluthge merged commit 2adcd26 into master Feb 21, 2026
8 checks passed
@DilumAluthge DilumAluthge deleted the dpa/run_work_thunk_rv branch February 21, 2026 08:21
DilumAluthge added a commit to JuliaParallel/DistributedNext.jl that referenced this pull request Feb 22, 2026
…e()`; this fixes a JET error around matching methods for `run_work_thunk(...)` (#181)

This is a forward-port of JuliaLang/Distributed.jl#181 (JuliaLang/Distributed.jl@2adcd26).

This fixes the following JET error:

```
  │┌ run_work_thunk(rv::Distributed.RemoteValue, thunk::Bool) @ Distributed /workpath/Distributed.jl/src/process_messages.jl:79
  ││ no matching method found `run_work_thunk(::Bool, ::Bool)`: Distributed.run_work_thunk(thunk::Bool, false)
  │└────────────────────
```

(cherry picked from commit 2adcd26e81cec03dbf81fa94071b4c4499e539a1)
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.

2 participants