jamshale
jamshale
I'm actually not sure if we have the agent configured properly for the postgres pickup add-on. Might be causing some of the issues I am seeing...
Ugh. I think it will do it for rc releases. We should be able to put a simple if and exit statement for the tag name.
I tried to address this with https://github.com/openwallet-foundation/acapy/pull/3796. I haven't tested it out yet. Need to adjust all the publish workflows for my fork.
Ok this PR to fix it is tested now. Wasn't actually hard to do.
Could you give examples of your payloads for `POST /issue-credential-2.0/create-offer` and `POST /out-of-band/create-invitation` endpoints please? Usually a connection is established first, and then that connection is used to issue the...
I believe self issuance and adding a credential offer as an attachment should work and this is an issue. However, If the use case allows creating the connection with itself...
The security alerts are nothing. http used in the scenario tests. Not sure how to ignore it yet.
It's the same way as a did:sov. You use the /did/indy/create and then post it to /wallet/did/public. There's no way to start up a fresh agent with a seed and...
> Given the 5 errors found (examples with an “http” protocol instead of “https” — would it be easiest to just add an “s” in the indicated places, even though...
I think the sonarcloud should just be safe to ignore. It's annoying, because we should be able to mark things a safe in sonarcloud but it requires an admin configuring...