Tsuyoshi Sugibuchi

The same problem here. * KeeAgent + Tabby Alpha 181 -> OK * KeeAgent + Tabby Alpha 182, 183 -> KO

@stevenengland Sorry for this delay. I use the following settings. ### KeePass * KeePass: 2.52 * KeeAgent: 0.13.2 KeePass -> Tools -> Options -> KeeAgent * Agent Mode: Agent *...

Solved in my environment. I just downgraded the version of KeeAgent to 0.12.1 then it started working again with the latest Tabby (185) 🤔

@roeap We tried to use MSI-based authentication in a AKS cluster enabling AAD Pod Identity. But it failed with 403 errors from IMDS token endpoint. This error looks caused by...

This problem comes from the handling of `target_path` in `_details(...)` method. https://github.com/fsspec/adlfs/blob/2023.1.0/adlfs/spec.py#L919-L933 ```python if target_path: if ( len(output) == 1 and output[0]["type"] == "file" and not self.version_aware ): # This...

@martindurant Sorry for this late response. We expect only the link is deleted, like "rm" command in bash. ```bash mkdir a touch a/b ln -s a l ls l >...

I have confirmed that the latest version of KeeAgant (0.13.3) works with Tabby 1.0.186.

This behaviour of the AAD workload identity is not well documented, but the AAD workload identity webhook injects the following env variables into pods. https://azure.github.io/azure-workload-identity/docs/quick-start.html#7-deploy-workload | Environment variable | Description...

@steveloughran I agree. The env ver resolution looks the best solution for this. @creste Thank you very much for this prompt update. About the descriptions of the four properties, I...