Ashok Shettigar

I encountered this same error today when running ES v7.8.1 with 1.24.0 of free ROR ES plugin.

https://github.com/j-maly/CommandLineParser/issues/76 - related to this question.

> Can you please take look at my comments? Replied to all individual comments. Please check.

@VagyokC4 thanks. But my question is can 2 clients read the same collection and are they getting the same copy of data? From the example, when we use provider.RedisCollection() and...

@slorello89 thanks for the details. I think its important to provide feature to set expiry at collection level. Given that there is no default TTL and the collection items are...

But if we do it insert level, wouldn't it become expiry at individual record level? I was thinking something at the collection level. ``` var collection = provider.RedisCollection(TimeSpan.FromSeconds(15)); ``` and...

But purely in terms of data consistency, collection level expiry makes more sense. You are no longer dealing with individual records, when you are doing the processing of a data...

> That's not how redis works... the "collecion" that you see is "imaginary" in the sense that it only exists as long as records exists containing that namespace. Soon as...

This is duplicate of #7862, but definitely not duplicate of #7913. Client credential always needs password/secret field. PKCE does not always need password field. #7913 talks about providing option to...

Thanks for the quick response. Unfortunately, our company blocks unauthorized plugins from being installed on Chrome due to security issues. If not, I would have tried that as the first...