question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

schema: should listen for avro records failed

See original GitHub issue

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I’m commenting on this issue too often, add the flakybot: quiet label and I will stop commenting.


commit: c6d1750de45bbad0f599d328c37085f1f4246f9b buildURL: Build Status, Sponge status: failed

Test output
4 DEADLINE_EXCEEDED: Deadline exceeded
Error: 4 DEADLINE_EXCEEDED: Deadline exceeded
    at Object.callErrorFromStatus (/workspace/node_modules/@grpc/grpc-js/build/src/call.js:31:26)
        -> /workspace/node_modules/@grpc/grpc-js/src/call.ts:81:24
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client.js:179:52)
        -> /workspace/node_modules/@grpc/grpc-js/src/client.ts:338:36
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:336:141)
        -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:426:34
    at Object.onReceiveStatus (/workspace/node_modules/@grpc/grpc-js/build/src/client-interceptors.js:299:181)
        -> /workspace/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48
    at /workspace/node_modules/@grpc/grpc-js/build/src/call-stream.js:145:78
        -> /workspace/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
    at processTicksAndRejections (internal/process/task_queues.js:79:11)

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (1 by maintainers)

github_iconTop GitHub Comments

1reaction
feywindcommented, Oct 6, 2021

I'm just going to close this and see if it comes back.

(Narrator) It did.

0reactions
feywindcommented, May 9, 2022

This should be fixed at this point.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Problem when schema registry is failed - Apache Kafka
When a schema registry has failed, consumer or producer cannot read schema anymore. This means that the records stored in Kafka are no ......
Read more >
Handling Incompatible Schema Changes with Avro
Apache Avro has the notion of schema compatibility that allows us to determine whether or not a schema is compatible with one or...
Read more >
Using Apache Kafka with Schema Registry and Avro
This guide shows how your Quarkus application can use Apache Kafka, Avro serialized records, and connect to a schema registry (such as the...
Read more >
Error registering Avro schema / io.confluent.kafka. ...
By default, the kafka-avro-console-producer will assume that the schema registry is on port 8081, and happily connect to it.
Read more >
A Detailed Introduction to the Avro Data Format
and can work with map/dictionary-like objects to represent records; does not need to have strongly typed classes generated from schemas ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found