Devdutt Shenoi

> While testing enhanced authentication with EMQX, I encountered issues passing authentication successfully. Can you elaborate on this? Would be helpful if we have code to debug this with. >...

@ting-ms as mentioned by @swanandx we are low on bandwidth and can't promise when the PRs will be reviewed. I will try my best to get in some time to...

Moving [layout/partials/navbar.html line52](https://github.com/tikv/website/blob/master/layouts/partials/navbar.html#L52) to a line before closing the < nav > will help solve the issue... Currently .navbar-end isn't included within .navbar-menu, causing this issue.

@ajayns @apollonian Sorry for not having given a heads-up. The requested changes were made, please review again.

It seems like it was pointed out in code by @abhikjain360 [here](https://github.com/mquictt/mquictt/blob/broadcast/mquictt-server/src/lib.rs#L142). I believe he'd been working on a log based rewrite of the broker, I'll try and fix this...

The publishes are only sent over the network [following a call to `flush()`](https://github.com/mquictt/mquictt/blob/broadcast/mquictt-client/src/lib.rs#L172) which is in a separate tokio task that is not awaited, so they need not happen before...

@abhikjain360 what are your thoughts about making `publish()` instantaneous, i.e. move code contents of `flush()` into publish.

@abhikjain360 did you remove the `broadcast` branch? 😅 I have reinstated the branch, we need to keep it for as long as `main` isn't working.

@abhikjain360, I think we must target doing this specifically on `Client`. i.e. only `Client.close()` must trigger connection closure. `Publisher`/`Subscriber.close()` methods must not trigger connection closure, they might instead be aimed...

We have stopped creating releases on GitHub, it seems like this was an unfortunate oversight from our side of creating a patch, we have deleted the same. Thanks for pointing...