3 Commits

Include renames

Author	SHA1	Message	Date
cristhian	43759f7e00	lint markdown recursively ... `scan *.md` only matched the repository root, so a file added under any subdirectory would have stopped being checked without the CI step noticing. Scanning recursively follows the files instead of the layout, and --respect-gitignore keeps it off .venv and .dora.	2026-09-15 06:20:11 -03:00
cristhian	dc700106c5	move the workflow to .github/workflows ... act looks in .github/workflows by default, and running it locally before a commit is one of this repository's rules; keeping the workflow where act cannot see it meant every invocation needed -W. Gitea Actions reads both locations, so only one of them may exist or a push fires the run twice.	2026-09-15 06:13:53 -03:00
cristhian	3c0e0f327d	add dora-webcam node ... Captures frames from a V4L2 camera and publishes them as std/media/v1/Image: an Arrow struct of width, height, encoding and data, so a receiver needs nothing from the message metadata. For a compressed encoding the recorded dimensions are the image's, not the length of the payload. Based on opencv-video-capture from dora-hub, with three changes. The output is the typed image struct rather than a flat UInt8 buffer plus metadata. Camera selection by id reads /dev/v4l/by-id/ only; the upstream macOS system_profiler and Windows PowerShell enumeration is not carried. CAPTURE_FRAMES bounds a run so a test ends on its own, in place of upstream's ten-second CI cutoff -- a timeout would have made the CI step exit non-zero. CI=true keeps a failed capture from raising, publishing a labelled black frame instead, which is what lets dataflow.yml run on a machine with no camera. Two dataflows, run one at a time, as dora has no cross-dataflow wiring: dataflow.yml is the camera alone and the CI gate; dataflow_view.yml wires it into dora-image-view and is not run by CI, since it fetches that node over the network and needs a tag to exist there.	2026-09-15 06:04:25 -03:00