Build failed in Jenkins: pulsar_release_nightly_snapshot #759

See Changes: [github] [PulsarAdmin] Clusters to async (#6568) [github] Make SchemaStorage accessible in Offloader (#6567) [github] [PulsarAdmin] Lookup to async (#6569) [github] [PulsarAdmin] Wo

[GitHub] [pulsar-client-node] eaba commented on issue #78: Error: Failed to send message: AlreadyClosed

eaba commented on issue #78: Error: Failed to send message: AlreadyClosed URL: https://github.com/apache/pulsar-client-node/issues/78#issuecomment-602017688 There are two sides to this, cause I experienced it! 1 - If your producer is actually being closed, have you tried Ping-ing the s

Slack digest for #dev - 2020-03-21

2020-03-20 19:07:45 UTC - Ivy Rogatko: @Ivy Rogatko has joined the channel 2020-03-20 19:11:45 UTC - Ivy Rogatko: Hi. I was wondering if there was any plan for when delayed/scheduled messages would be able to go to disk rather than purely being in memory? The persistent hash-wheel idea sound