-
Hi, I wanted to play with pubsub a bit, with a very basic scenario:
- 3 peers all subscribe to the same topic "random"
- peer 1 is connected to 2 and peer 2 is connected to 3
- peer 1 publishes som…
-
-
## Description
The BuiltInType in the FieldMetaData is not set correctly.
This can be observed when using the example _tutorial_pubsub_publish_.
The DataSetField is the _ServerCurrentTime_ w…
-
**Describe the issue**
I am not able to get this to work, but I did also notice there is no "topic" field specified in the document. I am adding the topic, but I am getting this error:
error cr…
-
## Describe the feature
Currently redis stream pubsub use "0" as the last delivered entry ID in the stream, here is the related [code](https://github.com/dapr/components-contrib/blob/79adc565…
-
-
There is on-going work to make IPNS over PubSub have a faster initial resolution time by adding persistence to PubSub (e.g. libp2p/go-libp2p-pubsub#171). Additionally there is work on the libp2p testl…
-
OMEMO Encrypted messages to myself do not work (same device/client: Psi or Psi+).
It must be true: "options.ui.contactlist.show.self-contact"
Screenshot: https://i.ibb.co/3yV0ZCy/psi-myself-test…
-
## Expected Behavior
When calling the `client.pubsub.publish` function for a class, Dapr should send a CloudEvent with the `data` field filled with the value passed to the function. A type conversi…
-
fetchDeviceIdsForJID error:
From Micke to Everyone: (09:35 AM)
2018-01-17 16:30:53:244 Zom[487:117126] failedToFetchDeviceIdsFor tiffrobo@home.zom.im
17:442 Zom[487:117126] SEND:
siacs.c…