-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load connections didcomm protocols #1468
base: main
Are you sure you want to change the base?
Load connections didcomm protocols #1468
Conversation
Signed-off-by: jamshale <[email protected]>
@dbluhm Was this the intended behavior? To either have the OOB connection manager or the v1 connection manager and not both? |
Looks like it's not an issue with the binding. Possibly overlapping classes of something. Trying to figure it out. Currently did exchange doesn't work with the plugin. |
Signed-off-by: jamshale <[email protected]>
Signed-off-by: jamshale <[email protected]>
I think this fixes it. Looks for an oob invitation and serializes it with the OOBInvitation class. Added some development stuff. Going to see if the tests pass now in OATH. |
All the OATH tests pass with this branch so I think it's good to go... I admit I don't fully understand the data flow. |
@@ -9,7 +9,7 @@ python = "^3.12" | |||
|
|||
# Define ACA-Py as an optional/extra dependency so it can be | |||
# explicitly installed with the plugin if desired. | |||
acapy-agent = { version = "~1.2.1", optional = true } | |||
acapy-agent = { git = "https://github.com/openwallet-foundation/acapy.git", branch = "main", optional = true } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to keep this change? I assume we would want the version vs. main.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The version 1.2.1 doesn't have the v1 connections protocol removed. This would be updated when the next release happens.
@@ -24,7 +24,7 @@ pytest-ruff = "^0.4.1" | |||
black = "~24.4.2" | |||
|
|||
[tool.poetry.group.integration.dependencies] | |||
aries-askar = { version = "~0.3.2" } | |||
aries-askar = { version = "~0.4.2" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update to 0.4.3 already, or hold that to update them all together?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'll update it to 0.4.3 after acapy main gets the change, because it's pointing to main. The rest can wait until the next acapy release.
I'm not entirely sure why this is here though. This was done a long time ago. If the plugin doesn't explicitly use askar independently I don't think this should be needed. I'll try and look into removing this integration group for all plugins.
A couple of questions. |
I'm working on parsing this... Loading the protocol is needed but I thought the presence of the definition.py file would trigger that. I want to understand what's going on with the retrieve_invitation call as well before I call this good. Do you have a link to a test run that failed before introducing that particular change? |
I'm running it again... Will post when it completes. |
Yes the plugin definition file should have loaded the didcomm message types. It does this in firebase_push_notifications. However, the config it uses is |
Big file. But you can see the inviter get this stack trace whenever it uses oob connection.
The above exception was the direct cause of the following exception:
|
Signed-off-by: jamshale <[email protected]>
Signed-off-by: jamshale <[email protected]>
The didcomm protocol message types weren't loaded during setup which caused them to be missing when installed remotely and loaded via plugin.
This appears to make the v1 OATH tests pass but the other tests fail because this plugin binds to the BaseConnectionManager causing the OutOfBandManager to fail.