You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the protobuf schema in Confluent Schema is big, based on my debugging, this step
let proto_payload = encoder
.encode(&buf,"production.iot.Motor",SubjectNameStrategy::TopicNameStrategy(topic.to_string(),false),).await.expect("Failed to encode with schema registry");
will cause the app fail with error:
thread 'main' has overflowed its stack
fatal runtime error: stack overflow
If I change to less fields such as 400 temperature fields in Confluent Schema Registry, this line works well and won't crash.
let proto_payload = encoder
.encode(&buf,"production.iot.Motor",SubjectNameStrategy::TopicNameStrategy(topic.to_string(),false),).await.expect("Failed to encode with schema registry");
The text was updated successfully, but these errors were encountered:
hongbo-miao
changed the title
thread 'main' has overflowed its stack. fatal runtime error: stack overflow
Got "fatal runtime error: stack overflow" when the schema in Confluent Schema Registry is big
Oct 29, 2024
Can you share the stacktrace please? I wonder if it's an issue with the implementation of logos or something else. maciejhirsz/logos#400 might be related.
Describe the bug
When the protobuf schema in Confluent Schema is big, based on my debugging, this step
will cause the app fail with error:
To Reproduce
Download the producer code at https://github.com/hongbo-miao/hongbomiao.com/tree/c60ab834456279df00ec55b1e2c7a245df82e277/hm-kafka/kafka-client/kafka-rust/proto-producer
Change to 500 temperature fields for
Motor
inmain.rs
file:Click to expand!
src/protos/production.iot.motor.proto
file,:Click to expand!
Expected behavior
I expect the app not crash.
Additional context
If I change to less fields such as 400 temperature fields in Confluent Schema Registry, this line works well and won't crash.
The text was updated successfully, but these errors were encountered: