redpanda-data / redpanda-data/connect
FFI processor example uses incorrect glibc SONAME (libc.6.so vs libc.so.6)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.8k
- Forks
- 969
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 64
Description
Description
The FFI processor's example uses incorrect glibc naming:
- Summary says: "loading libc.so"
- library_path uses:
libc.6.so
The correct Linux glibc SONAME is libc.so.6, not libc.6.so.
Location
The example appears in the FFI processor definition (likely in internal/impl/ffi/processor.go or similar).
Current Example
pipeline:
processors:
- ffi:
library_path: libc.6.so # Should be libc.so.6
function_name: memcmp
args_mapping: 'root = ["foo", "bar", 3]'
signature:
return:
type: int32
parameters:
- type: byte*
- type: byte*
- type: int64
Expected
library_path: libc.so.6
And update the summary text to use libc.so.6 consistently.
Impact
This affects the auto-generated documentation at https://docs.redpanda.com/redpanda-connect/components/processors/ffi/
Found via CodeRabbit review on rp-connect-docs#435.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the FFI processor definition, likely internal/impl/ffi/processor.go, and find the example containing the library_path and summary text. Change both references to use libc.so.6 consistently, then verify the auto-generated FFI processor documentation reflects the corrected example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100