bufferlist: get() is not actually nullable in its return value

Passing an out of bounds index is the only way to get a NULL buffer but this causes an assertion so is not to be considered for the annotations.

added Merge in 2 days label

since it can still return NULL when g_return_val_if_fail() triggers, but not with valid usage, are there rules how bindings are supposed to handle that? We ignore the invalid usage scenario and it's up to bindings to handle that gracefully but if not that's ok too because at some point everything's tainted and might crash at any point anyway?

resolved all threads

added 1 commit

• 27e1cfd1 - bufferlist: get() is not actually nullable in its return value

Compare with previous version

removed Merge in 2 days label

assigned to @gstreamer-merge-bot

mentioned in commit slomo/gstreamer@0a0c9672

added 17 commits

• 27e1cfd1...0f8b599d - 16 commits from branch gstreamer:main
• 0a0c9672 - bufferlist: get() is not actually nullable in its return value

Compare with previous version

assigned to @slomo and unassigned @gstreamer-merge-bot

I couldn't merge this branch: CI failed! See pipeline https://gitlab.freedesktop.org/slomo/gstreamer/-/pipelines/1183898.

added 1 commit

• 65f9a304 - bufferlist: get() is not actually nullable in its return value

Compare with previous version

assigned to @gstreamer-merge-bot and unassigned @slomo

mentioned in commit slomo/gstreamer@1a8e7aa9

added 17 commits

• 65f9a304...0f8b599d - 16 commits from branch gstreamer:main
• 1a8e7aa9 - bufferlist: get() is not actually nullable in its return value

Compare with previous version

merged

changed milestone to %1.25.1