George Payne

Here is an alternative workaround, if `innerHTML` doesn't suit your needs (assumes there is a single slot): ```ts // workaround for https://github.com/ionic-team/stencil/issues/2982 @Watch('active') updateActive(active?: string) { if (!active) return; const...

/assign @moadz

Hi Alice, > Is mutating these keys something you need to do for some reason? Passing a different key forces a recreation of an element, so you can start with...

Thanks for extensive reply, and the docs you linked were interesting. > I believe in practice Stencil users can avoid the problem of inappropriately-null refs by using static, consistent keys...

> * Virtual DOM patching algorithm based on Snabbdom Coludn't find an equivalent issue in `Snabbdom`, but: > * Production setAccessor() function based on Preact This seems to be the...

Hi Florian, This is due to it being missing on the server side, but the fix _should_ be in the upcoming 22.6, so it can be added to the client...

### `Error: 8 RESOURCE_EXHAUSTED: Bandwidth exhausted` Related issue on `grpc-node` https://github.com/grpc/grpc-node/issues/1158 note: setting `grpc-node.max_session_memory` didn't appear to fix the issue. ### `Error: 13 INTERNAL: Received RST_STREAM with code 2 (Internal...

@Lougarou This appears to be fixed by #305 as it now correctly applies backpressure, preventing the bandwidth exhaustion. `yarn start wrfl --connection-string="esdb+discover://admin:changeit@uri:2113" --client_count=10 --request_count=30000 --stream_count=5000 --size=10 --worker_count=1` Using batch append:...

Hi @FeepingCreature, thanks for the issue. > I suspect there's a timing issue where the client tries to start up a batch connection for every event. Yep, that's exactly what...

Hi @matchish, I can't seem to reproduce this, beyond ~10_000 reads, we level off at (around) 13mb. `nodejs`: v16.13.0 `@eventstore/db-client`: v3.3.1 mem.js ``` js const { EventStoreDBClient, jsonEvent, START, FORWARDS,...