Skip to content

Name work_fn as the entry code of every observation (0.6.7) - #56

Draft
sotashimozono wants to merge 1 commit into
mainfrom
entry-code
Draft

sotashimozono wants to merge 1 commit into
mainfrom
entry-code

Conversation

@sotashimozono

Copy link
Copy Markdown
Member

Follow-up to QAtlasHub/DataVault.jl#56 (observation v2). Depends on DataVault 0.8.6 being registered in General. Until then CI cannot resolve it.

  • run! passes work_fn to DataVault.observe_sources(...; code=[work_fn]) on the master and on each worker. It travels the same way it will for pmap: a named function resolves to the worker's own, and a closure arrives as the master's code, which the observation names as "arrived from another process".
  • If a worker cannot receive work_fn, that is recorded as a failed observation (the worker's markers get observation=unknown and an observe_failed event) rather than failing run!.
  • DataVault floor 0.8.6; version 0.6.7.

Tests (test/run/test_run_observe.jl):

  • tokens are obs2-;
  • a work function defined in the test gives unverified, and the reason names it;
  • a closure fanned out to 2 real workers gives unverified, "arrived from another process".

Run locally against the DataVault branch: 18 checks pass.

🤖 Generated with Claude Code

With DataVault 0.8.6 an observation is unverified unless its entry code is named and checked.
run! now passes work_fn to observe_sources on the master and on each worker (it travels as it
will for pmap: a named function resolves to the worker's own, a closure arrives as the master's
code). A worker that cannot receive it records a failed observation instead of failing run!.
DataVault floor 0.8.6.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@sotashimozono
sotashimozono marked this pull request as draft September 22, 2026 11:40

This branch has not been deployed

No deployments
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.

1 participant