You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fixup: bound the shared import by the dataflow's until and alias re-exports
The shared import synthesised its own bound one step past `as_of` instead of
passing the dataflow's `until`, and documented the result as serving
single-time dataflows only. The maintenance import passes `(as_of, until)` and
follows the trace when `until` is empty, and nothing about the shared import
needs a different bound. The router already sends only single-time dataflows to
the interactive runtime, so the two bounds were equal for every dataflow that
reached the import, and the narrowing bought nothing. The variant's single-time
note and the `Timestamp::MAX` special case go with it.
An export whose arrangement is an imported shared arrangement was
`unreachable!`. Nothing in the optimizer promises that a peek dataflow never
re-exports its import under the export key, and a panic on either runtime aborts
the process. Both export paths now alias the export's id to the imported
publication point, the shared analogue of the `Trace` arm. The alias has no
`TraceBundle`, so `report_frontiers` reads the frontier through the registry.
`import_shared_index` is renamed `import_published_index` so it no longer reads
as a permutation of the `import_index_shared` method that calls it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VDm7opomJLxbNUEP3r9BLk
0 commit comments