Jakub Gmur

Is there any example/doc regarding how we may subscribe through GRAPH-QL-WS? I've managed to connect to graphql-ws for one of the subgraphs but I did not manage to subscribe for...

I'll close it as there's no activity.

I've tried following (can't see the difference). # GRAPH_LOG: error ETHEREUM_RPC_MAX_PARALLEL_REQUESTS: 256 ETHEREUM_BLOCK_BATCH_SIZE: 500 ETHEREUM_POLLING_INTERVAL: 100 ETHEREUM_TRACE_STREAM_STEP_SIZE: 500 GRAPH_ETHEREUM_TARGET_TRIGGERS_PER_BLOCK_RANGE: 1000 GRAPH_ETHEREUM_MAX_BLOCK_RANGE_SIZE: 8000 GRAPH_ETHEREUM_MAX_EVENT_ONLY_RANGE: 5000 # Is there any article regarding...

I haven't found any other solution to speed up the process except for the way that consits of placing more erigon/geth nodes and making each geth-node point to each (e.g...

Yes I've seen several enhacements in release notes e.g in 0.27, e.g: - **Store writes are now carried out in parallel to the rest of the subgraph process** - **GRAPH_STORE_WRITE_QUEUE**...

Had the same problem and just re-added VSTest@2 entry in pipeline via GUI. Adding VsTest@2 via GUI add these filtering entries mentioned by @AngelJava78 and @nohwnd. Be careful with **vsVersion**...

>  > > I can do this in the [ws](https://www.npmjs.com/package/ws) package but not on this one, any idea why it's not supported? Thanks for posting this screenshot :)

we're getting same issue; after switching this AddAzureCosmosDb health check we did not observe memory leak anymore  we're using

It's not the bug within the library **but the way we're registered & passed the** `CosmosClient` and `Microsoft.Azure.Cosmos.Database`. The solution: - Register **CosmosClient** as singleton (some of the settings may...