hyperledger-archives / aries-acapy-plugin-toolbox Goto Github PK

After installing the plugin toolbox according to the README and running this command:

aca-py start \                                                                                                                                                        (update)
              -it http localhost 3000 -it ws localhost 3001 \
              -ot http \
              -e http://localhost:3000 ws://localhost:3001 \
              --plugin acapy_plugin_toolbox \ 
              --no-ledger

I get the following error:

```2020-12-30 12:54:34,568 aries_cloudagent.core.plugin_registry ERROR Error loading plugin module: Unable to import module acapy_plugin_toolbox: No module named 'aries_cloudagent.core.profile'``

Is there anything I am missing or is there a way to fix this quickly?

See #155

It is time to deprecate and archive this project.

i'm trying to run the demo agents on Aries-toolbox but i keep getting the below error

Error: certificate has expired

how can i fix this?!

@TelegramSam and I briefly discussed tagging the plugin to show compatibility with ACA-Py versions. I propose we start versioning the plugin at 0.1.0 ASAP and then add tags that potentially point to the same commit of the format acapy-X.Y.Z-J where X.Y.Z is the ACA-Py version and J is an incrementing number for each new plugin release that targets the same version of ACA-Py. I think keeping the versioning independent but still providing the mapping of what plugin versions are compatible with what ACA-Py versions is clearer than having a SemVer nonconforming version or pseudo-lock-step release with ACA-Py.

when run the command "docker-compose -f ./docker-compose.alice-bob.yml -f ./docker-compose.mediator.yml up --build" , the error is occured，for help ：

With the intention of the Sovrin networks clarified and a new pricing model being applied to StagingNet (Endorsers have a fee), the Toolbox defaults should change from StagingNet to something else -- likely BuilderNet. This change is going into affect Real Soon Now, so this should be made quickly.

I'm not able to make the changes (long story...) but I think there is a documentation change and the references to the genesis files in the various dockerfiles.

FYI: @dbluhm

demo_agent_1 exits and I get the following: --: ./ngrok-wait.sh: /bin/bash^M: bad interpreter: No such file or directory.

I'm using Windows and noticed in the readme there are some limitations for Mac and Windows using ngrok. I thought it was a dos2unix issue, but I haven't been able to figure that process out. Any tips? Do I need to simply be on a Linux OS?

I'm trying to run the toolbox locally and when I run this command:

pip install git+https://github.com/hyperledger/aries-acapy-plugin-toolbox.git@master#egg=acapy-plugin-toolbox

I get this error:

no matches found: git+https://github.com/hyperledger/aries-acapy-plugin-toolbox.git@master#egg=acapy-plugin-toolbox

Is this URL out of date? Command is from the readme, here:

https://github.com/hyperledger/aries-acapy-plugin-toolbox#plugin-installation

Kindly update aries-cloudagent-python to current latest version 1.0.0
Thanks team

Trying to start agent demos using docker, with/without ngrok, agents go down due to options used in the startup.sh script.
There is an issue in the cloudagent repo talking about removed options being used here.

When creating a schema with an incorrect version identifier (e.g. 1 instead of 1.0) this will trigger a ledger transaction error in ACA-Py, shutting down the agent.

I think it would be good to catch such errors to at least prevent an agent shutdown.

Ledger errors via the Admin API do not trigger shutdown, but ledger errors via protocol messages (as is the case with creating a schema in aries-toolbox) does trigger the shutdown

Can you please help on this below startup issue?
Attaching to demo_tunnel_1, demo_agent_1
agent_1 | Waiting for tunnel...
agent_1 | Waiting for tunnel...
tunnel_1 | Tunnel to agent:3000 running; mangement available on 4040
tunnel_1 | Tunnel URL is: https://chatty-seals-accept-148-173-100-224.loca.lt
tunnel_1 | GET /status 200 126 - 3.085 ms
tunnel_1 | GET /start 200 61 - 0.477 ms
agent_1 | fetched end point [https://chatty-seals-accept-148-173-100-224.loca.lt]
agent_1 | Setting logging level of acapy_plugin_toolbox to 30
agent_1 | 2022-05-30 08:07:51,147 aries_cloudagent.commands.start ERROR Exception during startup:
agent_1 | Traceback (most recent call last):
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent_1 | self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger
agent_1 | open_pool_ledger.cb)
agent_1 | indy.error.PoolLedgerTimeout
agent_1 |
agent_1 | The above exception was the direct cause of the following exception:
agent_1 |
agent_1 | Traceback (most recent call last):
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/commands/start.py", line 72, in init
agent_1 | await startup
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/commands/start.py", line 28, in start_app
agent_1 | await conductor.setup()
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/core/conductor.py", line 176, in setup
agent_1 | self.root_profile, self.setup_public_did and self.setup_public_did.did
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/config/ledger.py", line 133, in ledger_config
agent_1 | async with ledger:
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 277, in aenter
agent_1 | await self.pool.context_open()
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 210, in context_open
agent_1 | await self.open()
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent_1 | self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/indy/sdk/error.py", line 27, in exit
agent_1 | ) from err_value
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent_1 | self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent_1 | File "/home/indy/.venv/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger
agent_1 | open_pool_ledger.cb)
agent_1 | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Pool timeout
agent_1 | Caused by: Pool timeout

I tried running the alice-bob demo docker-compose file and faced the following issue:

Looks like poetry is not installed properly or the binary is not found in the path after installation.
Any help is highly appreciated!!

When completing this Hyperledger Aries Workshop, I encountered a problem with starting up the agents for the demo. In the demo directory, I run docker-compose -f docker-compose.alice-bob.yml up --build and Alice and Bob both start up, but they both shut down after indy.error.CommonInvalidState. I believe that this Discord message cites the same problem. The stack trace is below.

I determined that the problem is with the Indicio TestNet Genesis URL in demo/configs/alice.yml and demo/configs/bob.yml. The URL currently is https://raw.githubusercontent.com/Indicio-tech/indicio-network/master/genesis_files/pool_transactions_testnet_genesis, but I believe that Indicio has switched their naming convention from "master" to "main." Changing the URL to https://raw.githubusercontent.com/Indicio-tech/indicio-network/main/genesis_files/pool_transactions_testnet_genesis fixes the issue.

I will also submit a PR with this fix, but given that this is my first PR for aries-acapy-plugin-toolbox, I wanted to submit an issue with more information to make sure I'm not missing anything.

agent-alice_1   | Traceback (most recent call last):
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent-alice_1   |     self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger
agent-alice_1   |     open_pool_ledger.cb)
agent-alice_1   | indy.error.CommonInvalidState
agent-alice_1   | 
agent-alice_1   | The above exception was the direct cause of the following exception:
agent-alice_1   | 
agent-alice_1   | Traceback (most recent call last):
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/commands/start.py", line 72, in init
agent-alice_1   |     await startup
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/commands/start.py", line 28, in start_app
agent-alice_1   |     await conductor.setup()
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/core/conductor.py", line 176, in setup
agent-alice_1   |     self.root_profile, self.setup_public_did and self.setup_public_did.did
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/config/ledger.py", line 133, in ledger_config
agent-alice_1   |     async with ledger:
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 277, in __aenter__
agent-alice_1   |     await self.pool.context_open()
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 210, in context_open
agent-alice_1   |     await self.open()
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent-alice_1   |     self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/indy/sdk/error.py", line 27, in __exit__
agent-alice_1   |     ) from err_value
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/aries_cloudagent/ledger/indy.py", line 175, in open
agent-alice_1   |     self.handle = await indy.pool.open_pool_ledger(self.name, pool_config)
agent-alice_1   |   File "/home/indy/.venv/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger
agent-alice_1   |     open_pool_ledger.cb)
agent-alice_1   | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Invalid library state
agent-alice_1   |   Caused by: Consistency proof verification failed
agent-alice_1   | 
agent-alice_1   | 
agent-alice_1   | Shutting down
demo_agent-bob_1 exited with code 0
demo_agent-alice_1 exited with code 0```

Based on direction from the Hyperledger TSC, each Hyperledger project is in the process of renaming default branches to main.

Github has released tools to make this transition process relatively painless. As such, the default branch of hyperledger/aries-acapy-plugin-toolbox will be changed to conform with the TSC's guidance.

This change will take place on:

• February 3, 7:00PM UTC

Impact to you as a developer:

• Updating a local clone after a branch name changes

Other resources:

• Renaming the default branch from master
• Renaming a branch

I think ACA-Py changed integer predicate validation to only allow numbers and it seems the toolbox sends a string. Not sure, but that's what I make up of the error

aries_cloudagent.messaging.models.base ERROR RequestPres message validation error:
animo-acme-acapy_1   | Traceback (most recent call last):
animo-acme-acapy_1   |   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/aries_cloudagent/messaging/models/base.py", line 133, in deserialize
animo-acme-acapy_1   |     return schema.loads(obj) if isinstance(obj, str) else schema.load(obj)
animo-acme-acapy_1   |   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/marshmallow/schema.py", line 723, in load
animo-acme-acapy_1   |     data, many=many, partial=partial, unknown=unknown, postprocess=True
animo-acme-acapy_1   |   File "/home/indy/.pyenv/versions/3.6.13/lib/python3.6/site-packages/marshmallow/schema.py", line 904, in _do_load
animo-acme-acapy_1   |     raise exc
animo-acme-acapy_1   | marshmallow.exceptions.ValidationError: {'proof_request': {'requested_predicates': defaultdict(<class 'dict'>, {'age': {'value': {'p_value': ['Not a valid integer.']}}})}}
animo-acme-acapy_1   | 2021-07-05 21:17:18,937 aries_cloudagent.core.dispatcher ERROR Message parsing failed: Error deserializing message: RequestPres schema validation failed, sending problem report