jamshale
jamshale
I've been thinking about this problem and the lock does make sense for single instance deployments. It could probably be a bit more efficient. However, the problem is with multi-instance...
I think this is a good solution and basically what I was thinking. The only thing I wasn't sure about is if we could really assure atomicity for reads by...
It is just postgres and sqlite. I'm not sure what to do about sqlite. Maybe we can just make it a condition that it can only be used for single...
@bryce-mcmath Were you able to test this? I was wondering if this could still get merged into the patch as it is the last thing allowing this scenario to work...
OK, great. Thank you.
@ff137 Is this working for you to test changes to the aries-askar library? I've been trying to do the same thing, with a fork of aries-askar, committing the `libaries_askar.*` files...
> @jamshale I managed to get integration tests passing - using an aries_askar TestPyPI package 👀 [90cd53c](https://github.com/hyperledger/aries-cloudagent-python/commit/90cd53cc3f736ffc85128975ffca4f8484950b75) > > Last couple commits here show how I uploaded to TestPyPI: [ff137/aries-askar#1](https://github.com/ff137/aries-askar/pull/1)...
You shouldn't set a did:web to the public did. It is very indy specific right now. This should be prevented. There is ongoing work to allow the public did to...
- Yes, The count/start endpoints should be renamed limit/offset. - `GET /credentials/w3c` should have limit and offset capabilities. Could be done as a separate task. I guess this would be...
I believe this is improper use of the public did configuration. Although it's not your fault. This configuration has become extremely confusing. I have created a ticket to try and...