Sync upstream GStreamer into ignis-main

[github-actions]

This PR merges the latest upstream GStreamer main branch into ignis-main while preserving Ignis changes.

---

Note

Medium Risk
Broad upstream merge touches core parsing, tracing, and platform video memory paths; regression risk is typical of a large sync rather than a single isolated fix.

Overview
Large upstream merge bringing GStreamer 1.29.2-era API/docs and CI/fuzzing updates into ignis-main.

CI tailors pipelines for the gstreamer-security project: Windows/macOS (and related Cerbero) jobs are skipped, and ci/scripts/test.sh omits --check-bugs for that repo name.

OSS-Fuzz expands build-oss-fuzz.sh to build selected good and bad demux/parser plugins (was mostly core-only), adds several new LLVM fuzz targets under ci/fuzzing/ (audio converter/caps, caps/value/structure parsing, video converter/metadata), seeds/corpus paths for discoverer and gst-value, and wires them in meson.build.

Public API (GIR) documents new 1.30 tracer span/event APIs (GstTraceFormat, GST_TRACE_* macros) and deprecates GstTracerRecord in favor of them; adds Android AHardwareBuffer allocators/caps and GST_VIDEO_FORMAT_AHARDWARE_BUFFER; CUDA GstCudaAggregator / GstCudaConverter and gst_cuda_fill_video_frame; gst_base_parse_set_allow_duplicated_pts plus clearer PAUSED→READY reset notes on GstBaseParse helpers; gst_egl_image_create; RISC-V vector CPU probe; discoverer stream-number contract docs. Plugin-base micro version bumps appear in generated GIR.

Conformance: MV-HEVC Fluster reference hashes updated in JCT-VC-MV-HEVC.json.

^{Reviewed by Cursor Bugbot for commit 36c4354. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Validate synthesis omits first details

Medium Severity

In _do_report_synthesis, the first report in each issue group still gets level and “Detected on”, but gst_validate_report_print_details no longer runs for that entry. Critical and full-detail issues that only appear once (or sit at the list head) lose their Details block in synthesized output.

 

^{Reviewed by Cursor Bugbot for commit 048051e. Configure here.}

[cursor]

Dot-dir uses wrong timestamp

Low Severity

The new dot-dir branch builds dot filenames from raw gst_util_get_timestamp(), while the default path uses GST_DEBUG_BIN_TO_DOT_FILE_WITH_TS, which stamps elapsed time since GStreamer start. Mixed runs produce incomparable or misleading dot names for the same scenario action.

 

^{Reviewed by Cursor Bugbot for commit 048051e. Configure here.}

[cursor]

Span start logs as error

Low Severity

_maybe_begin_setup_new_stack_span emits GST_ERROR_OBJECT whenever a normal stack-setup trace span starts. That treats expected composition updates as errors and can fail CI or confuse operators when tracing is enabled.

 

^{Reviewed by Cursor Bugbot for commit 048051e. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 5 total unresolved issues (including 4 from previous reviews).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 36c4354. Configure here.}

[cursor]

Converter fuzzer can exhaust memory

Medium Severity

The audio converter path calls gst_audio_converter_convert on the full fuzz payload with no frame or output-size cap. With large inputs and extreme rate ratios, that API allocates out_frames * bpf unbounded, so the fuzzer can OOM. The resampler path in the same file already guards with MAX_FRAMES and MAX_RESAMPLE_BYTES.

 

^{Reviewed by Cursor Bugbot for commit 36c4354. Configure here.}