-
Notifications
You must be signed in to change notification settings - Fork 2
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
test: enable tests #14
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
YoussefAWasfy
had a problem deploying
to
release
September 10, 2024 09:29
— with
GitHub Actions
Failure
YoussefAWasfy
had a problem deploying
to
release
September 10, 2024 09:43
— with
GitHub Actions
Failure
- bs58 - sha2 - serde-enum-str - uuid
SSL Network server added Config Management added Stats starting to be added
Basic structure of REST handling starting to be put in place
Inbound message handling started Refactoring of message handling - about to fork
Now need to create an enum of envelope types to simplify the unpacking process.
Likely going to regret removing lifetimes and add back later Trade-off on speed/performance of not copying data vs complexity of lifetimes
- Implemented Envelope enum so we know what type the message is All didcomm-rust tests are working in this version.
Refactor: SecretsResolver uses &[String] instead of &Vec<String>
Created MetaEnvelope so we can keep associated data together Refactored the way we handle DID resolution (still ugly) unpacking an inbound message now works, but does nothing
Added ability to update DID and Secrets Resolevrs inside the unpack
- added allow for clippy::single_component_path_imports for examples - gets rid of a compiler warning that is not a problem
to benchmarks to remove warnings
Fixed message_inbound so it works with updated didcomm crate Added file structure for protocols including ping protocol
Need to now implement ability to write to the database and for the client to poll looking for the response message. Currently it cheats and returns the response message in the body of the HTTP response.
Still need to implement database storage and retrieval of trust-ping messages.
…the ATM-SDK * pack_encrypted() - encrypted and optionally signed message * pack_signed() - plaintext and signed message * pack_plaintext() - plaintext! not encrypted, not signed * unpack() - unpacks any format DIDComm message * NOTE: You are responsible for sending this message to the mediator as a separate step. * HTTP(S) : Call atm.send.didcomm_message(&message, true|false) * WebSocket : Call atm.ws-send_didcomm_message(&message, &message_id)
- added did-peer as a dev-dependency in mediator
This allows for the same DIDCache to be utilised by the application outside of ATM and within ATM. If you don't specify an external cache, then a local internal cache wil be automatically created. 2. Added DID Resolevr Cache configuation to mediator Allows for tuning of the DID resolver cache in the mediator
YoussefAWasfy
force-pushed
the
add_tests
branch
from
September 10, 2024 10:07
088ba99
to
5d9441c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.