awslabs / awslabs/amazon-kinesis-client-nodejs
SEVERE: class FastBuffer extends Uint8Array {}]
- Dominant language
- JavaScript
- Stars
- 304
- Forks
- 198
- Avg merge
- 36m
- Merged PRs (30d)
- 2
Description
Used the KPL to ingest data and got this one:
INFO: Starting: Reading next message from STDIN for shardId-000000000017
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.MessageWriter call
INFO: Message size == 719833 bytes for shard shardId-000000000017
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [buffer.js:8] for shard shardId-000000000017
buffer.js:8
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [class FastBuffer extends Uint8Array {}] for shard shardId-000000000017
class FastBuffer extends Uint8Array {}
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [^] for shard shardId-000000000017
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [] for shard shardId-000000000017
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [RangeError: Maximum call stack size exceeded] for shard shardId-000000000017
RangeError: Maximum call stack size exceeded
Jul 11, 2017 9:05:28 PM com.amazonaws.services.kinesis.multilang.DrainChildSTDERRTask handleLine
SEVERE: Received error line from subprocess [ at Buffer.Uint8Array (native)] for shard shardId-000000000017
at Buffer.Uint8Array (native)
my dependencies:
"dependencies": {
"async": "^2.4.1",
"aws-kinesis-agg": "^2.2.2",
"aws-sdk": "^2.79.0",
"aws-xray-sdk": "^1.1.1",
"requestretry": "^1.12.0",
"util": "^0.10.3",
"uuid": "^3.1.0",
"winston": "^2.3.1",
"aws-kcl": "^0.6.0"
},
Contributor guide
Research direction
Start by reproducing the reported KPL ingestion failure with the listed dependencies and capture the Node.js runtime version. Inspect the reported buffer.js location and the Buffer/Uint8Array stack trace; done means identifying a reproducible cause and documenting or testing a compatible behavior without the stack overflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript, node.js
- Domain
- backend, stream-processing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100