cristhian
dc3960809a
validate / validate (push) Successful in 59m16s
The build command was `pip install .`, which is what upstream and the dora docs use because `--uv` rewrites it. Spelling it `uv pip install .` means the dataflow never installs through pip at all, whether or not `--uv` was passed. The cost is that the node then needs a virtualenv to install into, so it must be run with `--uv`; the README says so. The second dataflow is gone. It existed to wire this node into dora-image-view just to see the frames, which pulled another repository over the network and needed a tag there. PREVIEW=true now opens a local window of the frames as they are published, so checking a camera, an encoding or a flip needs this repository alone. It shows the frame after the flip and the resize, so what is on screen is what is sent, and it never opens under CI, where there is no display. That a source node can display its own output overlaps with what a viewer node does. The overlap is the point: the alternative was a second repository in the loop before you can tell whether a camera works.
18 lines
506 B
YAML
18 lines
506 B
YAML
# The camera alone, and the CI gate: with CI=true a failed read publishes a
|
|
# placeholder frame rather than raising, so this runs on a machine with no
|
|
# camera.
|
|
strict_types: true
|
|
|
|
nodes:
|
|
- id: camera
|
|
path: dora-webcam
|
|
build: uv pip install .
|
|
inputs:
|
|
tick: dora/timer/millis/33
|
|
outputs:
|
|
- image
|
|
|
|
# Nothing consumes the frames: the point is that the node opens, encodes and
|
|
# publishes. Set PREVIEW=true to watch them in a local window instead of
|
|
# wiring a viewer node.
|