wehub-resource-sync
c56bef871b
CodeQL / Analyze (python) (push) Has been cancelled
Update Platform Components Table / update (push) Has been cancelled
Docker image release / Build base image (push) Has been cancelled
Sync docs with Docusaurus / sync (push) Has been cancelled
Tests / Check if changed (push) Has been cancelled
Tests / format (push) Has been cancelled
Tests / check-imports (push) Has been cancelled
Tests / Unit / macos-latest (push) Has been cancelled
Tests / Unit / ubuntu-latest (push) Has been cancelled
Tests / Unit / windows-latest (push) Has been cancelled
Tests / mypy (push) Has been cancelled
Tests / Integration / ubuntu-latest (push) Has been cancelled
Tests / Integration / macos-latest (push) Has been cancelled
Tests / Integration / windows-latest (push) Has been cancelled
Tests / notify-slack-on-failure (push) Has been cancelled
Tests / Mark tests as completed (push) Has been cancelled
13 lines
706 B
YAML
13 lines
706 B
YAML
---
|
|
enhancements:
|
|
- |
|
|
Document the input ordering behavior of auto-promoted lazy variadic sockets in
|
|
``Pipeline.connect()``. When
|
|
multiple senders are connected to the same list-typed receiver socket, ordering
|
|
depends on the pipeline class. With ``Pipeline``, items are ordered alphabetically
|
|
by sender component name (because ``Pipeline.run()`` schedules components in
|
|
alphabetical order for deterministic execution), not by the order of ``connect()``
|
|
calls. With ``AsyncPipeline``, no ordering is guaranteed, since components in
|
|
different branches may run in parallel. The docstrings now point users to a
|
|
dedicated joiner component when they need explicit ordering.
|