Closed KimEbert42 closed 11 months ago
It looks like things got started, but I’m only getting errors — 100% failure. DID/TAA/Schema/CredDef creation all seemed to work. .env
looks right. The connections are failing though.
Locust is showing in the Failures tab repeated versions of this (JSON prettify didn’t work):
{'error': 1, 'result': {'outboundMessageContext': {'message': {'@type': 'https://didcomm.org/connections/1.0/request', '@id': 'eff34c37-0763-4c7a-93f2-0f5ac7d7187b', 'label': 'RA9U9PgK3oWCXN', 'connection': {'DID': 'MyFbygZ1hZnZS18SrLbhnX', 'DIDDoc': {'@context': 'https://w3id.org/did/v1', 'publicKey': [{'id': 'MyFbygZ1hZnZS18SrLbhnX#1', 'controller': 'MyFbygZ1hZnZS18SrLbhnX', 'type': 'Ed25519VerificationKey2018', 'publicKeyBase58': 'CRu7kTqLYqRd2Mr4s8YwnZxnAk4wgBJmUXHDxBLn4QdG'}], 'service': [{'id': 'MyFbygZ1hZnZS18SrLbhnX#IndyAgentService-1', 'serviceEndpoint': 'didcomm:transport/queue', 'type': 'IndyAgent', 'priority': 0, 'recipientKeys': ['CRu7kTqLYqRd2Mr4s8YwnZxnAk4wgBJmUXHDxBLn4QdG'], 'routingKeys': []}], 'authentication': [{'publicKey': 'MyFbygZ1hZnZS18SrLbhnX#1', 'type': 'Ed25519SignatureAuthentication2018'}], 'id': 'MyFbygZ1hZnZS18SrLbhnX'}}, '~thread': {'thid': 'eff34c37-0763-4c7a-93f2-0f5ac7d7187b', 'pthid': 'a91fbdb3-7e61-4974-8ee0-191062c8cfdc'}, '~transport': {'return_route': 'all'}}, 'outOfBand': {'_tags': {'threadId': 'a91fbdb3-7e61-4974-8ee0-191062c8cfdc', 'state': 'initial', 'invitationId': 'a91fbdb3-7e61-4974-8ee0-191062c8cfdc', 'recipientKeyFingerprints': ['z6MkumxSrqat9hDEiW5feXMManoTR8Wy1RbLZC9B9skDwKXF'], 'role': 'receiver'}, 'metadata': {'_internal/legacyInvitation': {'legacyInvitationType': 'connections/1.x'}}, 'id': 'a26e5fd0-3450-45e5-bf70-646e68f59946', 'createdAt': '2023-12-08T05:29:42.670Z', 'outOfBandInvitation': {'@type': 'https://didcomm.org/out-of-band/1.1/invitation', '@id': 'a91fbdb3-7e61-4974-8ee0-191062c8cfdc', 'label': 'Mediator (Admin)', 'accept': ['didcomm/aip1', 'didcomm/aip2;env=rfc19'], 'handshake_protocols': ['https://didcomm.org/connections/1.0'], 'services': [{'id': '#inline', 'serviceEndpoint': 'http://host.docker.internal:3000', 'type': 'did-communication', 'recipientKeys': ['did:key:z6MkumxSrqat9hDEiW5feXMManoTR8Wy1RbLZC9B9skDwKXF']}]}, 'role': 'receiver', 'state': 'prepare-response', 'autoAcceptConnection': True, 'reusable': False, 'updatedAt': '2023-12-08T05:29:42.681Z'}, 'agentContext': {'contextCorrelationId': 'default'}, 'connection': {'_tags': {}, 'metadata': {}, 'connectionTypes': [], 'id': '63b85c69-425c-4c3c-bb2e-1c93b1a14aed', 'createdAt': '2023-12-08T05:29:42.700Z', 'did': 'did:peer:1zQmcumLER2L4MAw92FKQiH9yTaoNWvE8NTL1QzBYqk2694e', 'invitationDid': 'did:peer:2.SeyJzIjoiaHR0cDovL2hvc3QuZG9ja2VyLmludGVybmFsOjMwMDAiLCJ0IjoiZGlkLWNvbW11bmljYXRpb24iLCJwcmlvcml0eSI6MCwicmVjaXBpZW50S2V5cyI6WyJkaWQ6a2V5Ono2TWt1bXhTcnFhdDloREVpVzVmZVhNTWFub1RSOFd5MVJiTFpDOUI5c2tEd0tYRiN6Nk1rdW14U3JxYXQ5aERFaVc1ZmVYTU1hbm9UUjhXeTFSYkxaQzlCOXNrRHdLWEYiXX0', 'theirLabel': 'Mediator (Admin)', 'state': 'request-sent', 'role': 'requester', 'autoAcceptConnection': True, 'threadId': 'eff34c37-0763-4c7a-93f2-0f5ac7d7187b', 'protocol': 'https://didcomm.org/connections/1.0', 'outOfBandId': 'a26e5fd0-3450-45e5-bf70-646e68f59946', 'updatedAt': '2023-12-08T05:29:42.703Z'}}}}
Another thing I noted. When building the docker agent, it looks like there is an old, deprecated method for adding Node 18 to the docker container. I get this message and delay when building:
=> [load-agent base 4/13] RUN curl -fsSL https://deb.nodesource.com/setup_18.x | bash - 44.2s
=> => # SCRIPT DEPRECATION WARNING
=> => # ================================================================================
=> => # ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
=> => # ================================================================================
=> => # TO AVOID THIS WAIT MIGRATE THE SCRIPT
=> => # Continuing in 60 seconds (press Ctrl-C to abort) ...
I will add a ticket for the deprecated node installation.
To have the environment variables updated, shutting down the services is required for the environment variables to be applied.
Restart is insufficient? Also, just to confirm — stop the Mediator as well?
Yes, restart may not reload the .env file. It is okay to shutdown the mediator since we are using a volume for the database. I typically stop all the services.
I was able to successfully run everything for both (a) the ping test and (b) the issue credential test. I suggest adding the restart commands to the QUICKSTART
guide. Other than that, I think it looks great for a demo video! Thanks Kim!!
Add quick start guide for easier startup.