redpanda-data / redpanda-data/connect

Kinesis compressed input crash (appears due to third party lib)

Open
#2,929 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
8.8k
Forks
969
Avg merge
1d 13h
Merged PRs (30d)
64

Description

We're seeing a panic when running kinesis to kafka:

bufio.(*Reader).ReadByte(0xc00d39e6c0)
	/usr/local/go/src/bufio/bufio.go:271 +0xa5
compress/flate.(*decompressor).huffSym(0xc0011bb908, 0xc0011bb938)
	/usr/local/go/src/compress/flate/inflate.go:720 +0x102
compress/flate.(*decompressor).huffmanBlock(0x0?)
	/usr/local/go/src/compress/flate/inflate.go:495 +0x45
compress/flate.(*decompressor).Read(0xc0011bb908, {0xc00195c000, 0x2000, 0xc0020ec090?})
	/usr/local/go/src/compress/flate/inflate.go:348 +0x5b
compress/gzip.(*Reader).Read(0xc001f57348, {0xc00195c000, 0x2000, 0x2000})
	/usr/local/go/src/compress/gzip/gunzip.go:252 +0xa2
net/http.(*gzipReader).Read(0xc00d2c6660, {0xc00195c000, 0x2000, 0x2000})
	/usr/local/go/src/net/http/transport.go:2911 +0x195
github.com/aws/aws-sdk-go-v2/aws/transport/http.(*timeoutReadCloser).Read.func1()
	/go/pkg/mod/github.com/aws/aws-sdk-go-v2@v1.30.4/aws/transport/http/timeout_read_closer.go:48 +0x43
created by github.com/aws/aws-sdk-go-v2/aws/transport/http.(*timeoutReadCloser).Read in goroutine 18606
	/go/pkg/mod/github.com/aws/aws-sdk-go-v2@v1.30.4/aws/transport/http/timeout_read_closer.go:47 +0xfb

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reproducing the panic in the kinesis-to-kafka path with compressed input and inspect the dependency versions involved, especially the AWS transport stack. Done means the compressed input no longer crashes the process and the failure behavior is covered by a reproducible test.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, go, kafka
Domain
backend, data-engineering, stream-processing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.