[GitHub] [pulsar-client-node] massakam commented on issue #129: Metadata properties incompatible with pulsar-dotnet

massakam commented on issue #129: URL: https://github.com/apache/pulsar-client-node/issues/129#issuecomment-705963659 Oh, I haven't joined `#dev-dotpulsar` yet. This is an automated message from the Apache Git Service. To re

[GitHub] [pulsar-client-node] sijie commented on issue #129: Metadata properties incompatible with pulsar-dotnet

sijie commented on issue #129: URL: https://github.com/apache/pulsar-client-node/issues/129#issuecomment-705960431 @massakam that was what I suspected and suggested in the slack channel. This is an automated message from th

[GitHub] [pulsar-client-node] massakam commented on issue #129: Metadata properties incompatible with pulsar-dotnet

massakam commented on issue #129: URL: https://github.com/apache/pulsar-client-node/issues/129#issuecomment-705960146 A description of "batching" in Pulsar is here: https://pulsar.apache.org/docs/en/2.6.1/concepts-messaging/#batching

[GitHub] [pulsar-client-node] massakam commented on issue #129: Metadata properties incompatible with pulsar-dotnet

massakam commented on issue #129: URL: https://github.com/apache/pulsar-client-node/issues/129#issuecomment-705958062 @dionjansen @sijie Apparently, no matter what language the producer is written in, pulsar-dotpulsar doesn't seem to be able to get the properties of the received messa

[GitHub] [pulsar-dotpulsar] gfoidl commented on pull request #59: Fixed potential torn reads in EventCounters

gfoidl commented on pull request #59: URL: https://github.com/apache/pulsar-dotpulsar/pull/59#issuecomment-705754069 Please wait with the merge until https://github.com/dotnet/docs/pull/20984 is approved. If there should be any change needed, then there are inconsistent usages for the p

[GitHub] [pulsar-manager] rattanjotsingh opened a new issue #343: Add Pagination feature at the front end of pulsar manager.

rattanjotsingh opened a new issue #343: URL: https://github.com/apache/pulsar-manager/issues/343 Able to see only 10 brokers at a time at the front end. Enable pagination feature to be able to see more than 10 brokers. This

[GitHub] [pulsar-dotpulsar] blankensteiner commented on pull request #59: Fixed potential torn reads in EventCounters

blankensteiner commented on pull request #59: URL: https://github.com/apache/pulsar-dotpulsar/pull/59#issuecomment-705569218 Hi @gfoidl If you rebase, then I can run the tests again :-) This is an automated message from th

[GitHub] [pulsar-dotpulsar] blankensteiner merged pull request #60: Fix CI

blankensteiner merged pull request #60: URL: https://github.com/apache/pulsar-dotpulsar/pull/60 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL abo

Slack digest for #dev - 2020-10-08

2020-10-07 16:26:26 UTC - Rich Adams: Does anyone know why pulsar-sql creates its ReadOnlyCursors with a default ManagedLedgerConfig rather than the configured ManagedLedgerConfig? I am running into issues where queries including a predicate with `__publish_time__` are failing with a `ManagedLe

[GitHub] [pulsar-dotpulsar] RobertIndie commented on pull request #59: Fixed potential torn reads in EventCounters

RobertIndie commented on pull request #59: URL: https://github.com/apache/pulsar-dotpulsar/pull/59#issuecomment-705430698 > CI failure is unrelated to this change, can someone re-run CI please? This seems to be a problem with some configuration of CI. I will try to fix it.

[GitHub] [pulsar-dotpulsar] gfoidl commented on pull request #59: Fixed potential torn reads in EventCounters

gfoidl commented on pull request #59: URL: https://github.com/apache/pulsar-dotpulsar/pull/59#issuecomment-705429278 CI failure is unrelated to this change, can someone re-run CI please? This is an automated message from the

[GitHub] [pulsar-dotpulsar] gfoidl opened a new pull request #59: Fixed potential torn reads in EventCounters

gfoidl opened a new pull request #59: URL: https://github.com/apache/pulsar-dotpulsar/pull/59 The backing fields for the counters are `long`, so there was potential torn read on 32-bit platforms. `Volatile.Read` ensures that the value is read in a atomic way, so no torn reads can occur.