jamshale
jamshale
So, after understanding the problem with credo the approach for qualified `did:sov` will change. We will not support qualified `did:sov` at all. Currently with a patch release of credo it...
Yes. It will at least fail the `ruff` lint check that is done with the unit tests and force developers to keep the function descriptions up to date. I think...
@swcurran Did you used to get any warnings or errors when running `sphinx-build`? I fixed one set of warnings related to these changes but am getting other warnings for unrelated...
I'm slowly figuring out how to fix the sphinx errors and warnings. I'll include the changes in this PR once I resolve them all.
We can merge this the way it is. They warnings and errors only effect the individual docs. The rest will still be generated. I think I should be done soon...
This is updated and should be good to go now.
I do think the distributed lock is good in some ways. I still don't know if this got a ton of concurrent issuance requests if it's truly atomic or not....
I think we should go ahead with this solution for now and get a release out. From what I understand is askar transactions aren't atomic for multiple instances and connection...
ChatGPT sums this up really well. https://chatgpt.com/s/t_6852e134862081918dd705fd92b46205
Sounds good. I think it's more like this is a big improvement over basically what is a bug with it currently. However, the distributed lock is what is needed for...