Michael Ilyin

@Mallets @OlivierHecart @DariusIMP noticed, that there is a problem with this issue. Before the fix the `reply_id` was set to random, which was definitely wrong: https://github.com/eclipse-zenoh/zenoh/pull/1138/files#diff-f0aac9d83f0d53d0be9a6ee02269c26605c3920dbd6782f744e59c21aec235d5L2311 But it seems that...

@OlivierHecart also mentioned, that it's probably better to use `EntityGlobalId` here instead of `ZenohId`


@stepkun thank you for your thoughts After discussion with @OlivierHecart and @Mallets it was decided to put this option under "unstable" until final solution. Anyway there is no coherent way...

New requirement added: allow to use unbounded channel in `PublicationCache` **lomac — Yesterday at 8:57 AM** Hello, I am getting some deadlock on publication. Is this an expected behavior? Here...

Mostly duplication of https://github.com/eclipse-zenoh/zenoh/issues/732, fixed in https://github.com/eclipse-zenoh/zenoh/pull/729

Just to keep the history of the issue: Previous attempt to fix is in https://github.com/eclipse-zenoh/zenoh/pull/625 The comments about procedure to find leaks and some tool tooling is in https://github.com/milyin/arc-trace

To be resumed after Tokio merging #566

This could be implemented this way: ```Rust let s = zenoh::open().wait()?; ... let c = Config::from_file(file)?; let s = zenoh::open().config(c).wait()?; ``` I.e. make open function without parameters and add `.config()`...

Done in dev/1.0.0 branch by reexporting all API through lib.rs