keria icon indicating copy to clipboard operation
keria copied to clipboard

KERI Agent in the cloud

Results 84 keria issues
Sort by recently updated
recently updated
newest added

This PR adds the following types of log message enhancements: - uses the `keria:` prefix for log messages instead of `keri:` - uses the asctime, levelname, and message log fields...

SignifyTS does not call `IpexGrantCollectionEnd.sendMultisigExn` for sending the `/multisig/exn` messages following sending out the `/ipex/grant` message for multisig and instead uses `ExchangeCollectionEnd.on_post` for this purpose. Why is this the case?...

I found `lmdb.DiskError` that seems to appear intermittently while I was working with multi-signature AIDs. I could not figure out a script to reproduce this error reliably. Here is the...

### Version Latest main on KERIA + Signify-TS [KERIA: 6ad36d5e171c599b078624c9ed4cd1c54e3c1b4a / Almost latest: 1e451d1c91e6f50edb57e2f4f41ca8b55755dac4 ] ### Environment M3, Python 3.12.2 ### Expected behavior KERIA should use the correct keys to...

bug

Steps to reproduce: 1. Agent 1: Boot agent 2. Agent 1: Create aid 3. Agent 1: Authorize agent end role 4. Agent 2: Boot agent and immediately after try to...

**Description:** I am performing some tests on rotating delegated multisig with GAR repo (plays as GARs) and Signifyts + Keria (play as QARs). In the process of rotation, GARs may...

**Description:** In the process of rotating a delegated multisig, cURLing to the multisig OOBI (agent) would return a 404 rather than its associated KEL. See below for a sample response....

# Steps to reproduce 1. Create wallet with identifier X and authorize the agent end role 2. Create wallet with identifier Y and authorize the agent end role 3. Resolve...

### Version Latest main ### Environment _No response_ ### Expected behavior I've removed 2 unnecessary `Accept: "application/json+cesr"` calls from Signify-TS in this PR: https://github.com/WebOfTrust/signify-ts/pull/313 There's still one endpoint which needs...

bug

### Feature request description/rationale Currently there is no distinction between logs per agent. Prefix the logs with the agent id.