jamshale

In acapy we set the notification with the `indy::` prefix like `(thread_id or f"indy::{rev_reg_id}::{cred_rev_id}")`. We thought we shouldn't change the revocation notification format but maybe credo can't handle the prefix?...

I wonder if there's any difference between single-wallet/db and multi-wallet/db scenarios? I agree we should try and prevent unnecessary opening and closing of sessions. I don't think this was ever...

@ff137 Yes, I think that's the correct way forward for now. I've never understood why these post filters have to be applied the way they do but I think that's...

Thanks for taking this on. This is an important feature. My only concern about having it in the 1.0.0 release is that it keeps getting delayed. We really want to...

We don't have a date. We want to release ASAP. I think this problem is acceptable to have in the release. It would make a good release milestone once it's...

This is now configurable via helm chart and env variables and live in a dev env. We are currently using the postgres persistence without any data clean up of old...

Can we replicate this with the demo? If so what are the steps? I removed the `preserve-exchange-records` flag from the faber and alice demo and could still complete the proof...

Hmm. As far as I could tell the webhook response always contained the required presentation result in the demo at least. There's some code here https://github.com/hyperledger/aries-cloudagent-python/blob/main/aries_cloudagent/protocols/present_proof/v2_0/models/pres_exchange.py#L205 related to the generated...

Maybe the vc-authn controller is parsing out the presentation somehow? I'd check out the demo with debug logs and different configs and see if it's what you are expecting. Unless,...

So, what I was doing with the webhook payload was my fault. The dockerfile for the demo had a random env variable setting `debug-webhooks` to true that overrides the command...