-
Notifications
You must be signed in to change notification settings - Fork 204
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
refactor: require native shared components implementation #1349
refactor: require native shared components implementation #1349
Conversation
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1349 +/- ##
==========================================
+ Coverage 85.31% 85.32% +0.01%
==========================================
Files 787 788 +1
Lines 19404 19405 +1
Branches 3150 3150
==========================================
+ Hits 16555 16558 +3
+ Misses 2842 2840 -2
Partials 7 7
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Just a few typos in the IndyVdrModuleConfig comments.
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
…tee/aries-framework-javascript into shared-component-module
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
…tee/aries-framework-javascript into shared-component-module
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by Government of Ontario Signed-off-by: Victor Anene <[email protected]>
…tee/aries-framework-javascript into shared-component-module
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
work funded by the Government of Ontario Signed-off-by: Victor Anene <[email protected]>
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.
Some final comments
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Yeah it has to be something with this branch. All other PRs have no issues with CI We switched indy-vdr from v9 to v10 in this branch. Let's see if it resolves the issue if we downgrade. |
Signed-off-by: Timo Glastra <[email protected]>
D'oh haven't seen this and I upgraded again to v10 in #1373 😞. Anyway, there it worked fine at the first try. |
Yeah seems that downgrading didn't do the trick. So it's something else, which is weird!?!? Or maybe it's because we're now importing the node.js modules more often, which results in the memory issues? |
import '../src/index' | ||
|
||
require('@hyperledger/indy-vdr-nodejs') | ||
import '@hyperledger/indy-vdr-nodejs' |
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.
These imports in tests' setup.ts are not needed anymore, are they?
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.
They are! Some tests don't use the module (e.g. IndyVdrSovDidResolver.test.ts
), but do use the binary. It will result in the binary not being registered on the shared package if you run the test (mainly in isolation).
I first started importing the nodejs bindings in these specific files, but I thought why make it more complex than needs to be and just imported it in the setup
This is absolutely possible, as in the wrappers we only provide a method to load libraries but not free resources used by them (which is certainly a bug, unless the runtime is freeing them automatically... which is not usually the case from our recent experience). |
We should maybe add a check and see if it's already loaded, and if so, don't load it again. I wouldn't expect importing a package multiple times has implications. If you're working in Node.JS you could only work with the Node.JS package, and never add / import the shared package... |
Signed-off-by: Ariel Gentile <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
100th time's the charm 🤞 |
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Signed-off-by: Timo Glastra <[email protected]>
Never thought this day would come |
The only thing we had to do was to rename it! Let's keep this in mind for the next cursed PR. |
The PR provides the guide to set up indy-vdr optional peer dependencies
Work funded by the Government of Ontario