augonis

I'm working on a web app using [pwa-starter-kit](https://github.com/polymer/pwa-starter-kit) and serving it in development with polymer-cli, it doesn't transpile or bundle in develoment, just rewrites module imports from module specifiers to...

The ReceiveBuffer is much more than a `Queue`, it manages waiters and buffers messages for all specific channels under the same 'real channel', as well as runs the receive loop...

I added tests for the receive task handling, as basic receive is covered by existing tests. P.S. I've put a limit on how many messages per specific channel `receive Buffer`...

Doable, but semantically and implementation wise it would muddy the meaning of `capacity` (and friends `channel_capacity`, `get_capacity(channel)`). * Currently `capacity` is configured/enforced on the sending side, having it affect receiving...

Should I remove the limit to unblock this PR and open a separate issue?

Just read django/channels#134, sounds similar my problem, this PR might address it. django/channels#151 also may be related if that issue is only with specific channels.

I'd expect receive_buffers to be long lived and few in number. In fact for all existing applications there would be just one, as receiving on multiple `real_channels` previously was not...

The issue comes from the usage of `document.getElementById`, which fails to find the element if it's not in the document yet, or auto-complete is part of ShadowDOM of another element....

I've encountered the behavior described by @sterankin as well. I tracked the cause to `pluginTransformMiddleware` overwriting CORS headers set by @koa/cors with the ones from a previous cached response. If...

Hi, I have a similar requirement. I did some tests and found the register for setting the work mode (on a SUN-12K-SG04LP3) . It's address 142 and value is 0...