Closed patriknw closed 1 year ago
similar silence for wrong stream_id in temperature_production.rs
Re-opening until verified by @patriknw. I've observed that an invalid stream id when consuming will cause the connection to drop and then be re-established. I view this as the correct behaviour as it may just be that the producer side does not yet know about a stream-id i.e. it is not a hard-failure.
Also, please note that DEBUG log level can be set to observe connections.
I have seen this again, but created a new issue https://github.com/lightbend/akka-edge-rs/issues/90 Closing this issue.
Change the stream_id registration_projection.rs to something that doesn't exist. Then the stream is supposed to fail with this exception https://github.com/akka/akka-projection/blob/5a540abc474c1b799d5a6a5e736d31eee551a865/akka-projection-grpc/src/main/scala/akka/projection/grpc/internal/EventProducerServiceImpl.scala#L105-L109
Nothing visible in iot-service-rs