madelson

@mjaow I think you are correct. Setting the metadata would just be "best effort" to support debugging and shouldn't be relied on as a synchronization mechanism. Arguably callers could just...

@mjaow youll just have to test it unfortunately I don’t have personal experience with such a configuration

Hi @DaleyKD thanks for your interest in the library. The implementation tries to clean up after itself, so currently we don’t support creating containers on the fly. I also wanted...

> The main reason is that I don't want to ask my customers to go in and manually create a container. I'd hope asking them to create the storage account...

@alexandrepepin-boxoffice the redis lock has a default expiry of 30s (with regular renewal so long as the lock is held). See [these docs](https://github.com/madelson/DistributedLock/blob/master/docs/DistributedLock.Redis.md#options). So I would expect that if you...

I'm going to consider this resolved for the time being. It would be great if we had a way to ensure that the lock renewal system was not affected by...

Is this not just broken as-is?

@mgravell I had someone report that the scripts weren't working in their setup because it references all keys through ARGV instead of KEYS (see https://github.com/madelson/DistributedLock/issues/254). I think I've seen the...

@teesofttech go for it. See https://github.com/madelson/DistributedLock/blob/master/docs/Developing%20DistributedLock.md for local setup steps. Depending on what you're doing you don't necessarily need all the setup but the more tests you can run locally...

@thangnguyen-69 I'd be happy to have you contribute this! As a starting point I would focus on providing an implementation of IDistributedLock. https://github.com/madelson/DistributedLock/pull/51/files gives a good sense of what adding...