Amy!
Amy!
according to the new implementation notes in the PR description, I have solved the issue of multiple claims. There are still some optimizations that still need to be done tho...
I can abunch of warnings about dangling tasks being put in to the queue each time i 1. run `polykey identities discover` 2. run `polykey identities list` to see that...
# THIS IS NOT A PROBLEM, DISREGARD THIS! THE ROOT CAUSE HAS BEEN IDENTIFIED IN THE PROCEEDING COMMENT for discovery resumption there needs to be changes in the code path....
The main problem right now, is that I've found discovering a Node vertex will make a Polykey agent request and iterate through the pages of claims on an identity in...
@tegefaulkes roger wanted to let you know that the PR can be handed off to you. The last part is just fixing #723 and then it should be ready to...
> Alright, I've fixed the main problem that was left. The main solution was to add a flag to `scheduleDiscoveryForVertex` called `ignoreActive` to ignore any active tasks when scheduling a...
It was found that the RPCServer was never using the `replacer` passed in from the constructor parameter. So no error stacks were ever being redacted. Furthermore, I think the `filterSensitive`...
i think it turns out to be something to do with importing from `@jest/globals` working improperly with `@swc/jest` https://github.com/swc-project/jest/issues/120. Simply patching out the imports with `const {...} = global;` seems...
Alternate idea: #### Using Multiple Sigchains (sigchain/network) Otherwise, we can maintain multiple certchains on a single node, one for each network that we want to connect to. The certchain would...
an example of a CSR over the wire protocol: https://en.wikipedia.org/wiki/Automatic_Certificate_Management_Environment going to take this into consideration