[exec] on/continues_on hits __not_a_scheduler diagnostics under the debug environment when STDEXEC_ENABLE_EXTRA_TYPE_CHECKING=ON
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the failure with exec::any_sequence_sender and exec::on or exec::continues_on using -DSTDEXEC_ENABLE_EXTRA_TYPE_CHECKING=ON. Trace the extra-type-checking debug environment and its scheduler-query lookup; done means these transformations no longer produce __not_a_scheduler diagnostics while scheduler queries still reach the wrapped environment.
Written by the indexing model from the issue text.
Description
Requested by @ericniebler in #2271 — follow-up found while verifying that PR with -DSTDEXEC_ENABLE_EXTRA_TYPE_CHECKING=ON. Fails on pristine main, so it is separate from the fix in #2271.
Description
Pipelines that transform sequence senders with exec::on / exec::continues_on produce __not_a_scheduler diagnostics under extra type checking. The debug environment injected by the extra-type-checking machinery appears to shadow or alter scheduler-related queries, so the transformation's scheduler lookup sees the debug proxy environment instead of the real one and concludes there is no scheduler.
Reproduction
Compose an exec::any_sequence_sender with exec::on / exec::continues_on and build with -DSTDEXEC_ENABLE_EXTRA_TYPE_CHECKING=ON.
Suggested fix direction
Make the debug env forwarding query-aware for scheduler queries (forward get_scheduler / get_delegatee_scheduler to the wrapped environment), or exclude scheduler queries from the debug proxy.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/stdexec
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·