-
Notifications
You must be signed in to change notification settings - Fork 295
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
feat(plugin-persistence-fabric): add new fabric persistence plugin #2331
feat(plugin-persistence-fabric): add new fabric persistence plugin #2331
Conversation
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.
@barnapa Please re-organize the commits a little bit to make it easier to review (right now the diff is huge because of the parent PRs in the stack and the 4 commits you have in the PR all look like they belong to your PR itself (but then when I look at the diff I can tell that the parent PRs diff are also included because it has the cmd-gui-app package in too).
If you reorganize your commits so that:
- There's only one commit with the changes that belong to this PR and
- The other 2 commits come from the 2 parent PRs
then we can review just your specific commit by filtering the diff down to just that (but right now this is not possible).
If you need any help with making this happen (git mechanics or otherwise) then just let me know or join one of the daily pair programming calls that we have and we can screen share: https://wiki.hyperledger.org/display/cactus/Daily+Pair+Programming+Calls
fc06dff
to
2e3c7f1
Compare
ok it is re organized |
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.
ok it is re organized
@barnapa It is re-organized, but all you did from what I can tell is squash everything together instead of separating the parent PR commits from this PR. You have a single commit that has a 115 files in its diff and it has the GUI app code in it too. Please double check #2331 (review)
@barnapa |
2e3c7f1
to
22213f2
Compare
I removed gui for fabric from this pull it will be in another one |
22213f2
to
eda83ce
Compare
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 removed gui for fabric from this pull it will be in another one
@barnapa Thank you for that! Now please resolve the merge conflicts and then we can review the actual PR.
I don't know why the other maintainers were not added automatically (we have it configured so that they are but it seems buggy) but I added everyone manually just now as reviewers.
Will wait for the conflict resolution before a full review but I noticed something already that could be addressed at the same time as the conflict resolution:
The tsconfig.base.json and tsconfig.json files were re-formatted which makes it hard to see if there were any actual changes it to so I'll ask to revert the formatting and if you do want to have the tsconfig files in a different format, that can be submitted as another PR which does not change any functionality, only formatting.
This way we don't mix changes that have potentially far reaching consequences (project-wide compiler configuration that affects 40+ packages) and changes that aren't changing anything but are very prone to distracting reviewers from tiny but impactful changes as described above.
...ugin-persistence-fabric/src/test/typescript/integration/persistence-fabric-db-client.test.ts
Show resolved
Hide resolved
...ugin-persistence-fabric/src/test/typescript/integration/persistence-fabric-db-client.test.ts
Show resolved
Hide resolved
...ugin-persistence-fabric/src/test/typescript/integration/persistence-fabric-db-client.test.ts
Show resolved
Hide resolved
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.
@barnapa Please
- Update the cacti versions to the current latest (which just had a release yesterday)
- Check out my comment about the magic strings
.../cactus-plugin-ledger-connector-fabric/src/main/typescript/plugin-ledger-connector-fabric.ts
Outdated
Show resolved
Hide resolved
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've requested minor edits around terminology and formatting in my comments.
95ac687
to
2654f0f
Compare
2654f0f
to
86dc2a2
Compare
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.
LGTM
86dc2a2
to
57b2da2
Compare
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.
LGTM
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.
@barnapa LGTM
FYI: I've made a couple of changes to the
- getRuntimeErrorCause function so that it doesn't hide information about exceptions that are not
string
norError
typed - dependencies (removed unused ones, added missing declarations)
1. Add a new plugin for storing hyperledger fabric ledger data into a database 2. Add functional tests for plugin and data access layer operations. operating with fabric-all-in-one docker composition Tests assume any postgres database, but for final deployment postgres or supabase is assumed. Data fed by this plugin can later be visualized by a GUI application or analyzed directly. ( right now the GUI will have switch to operate either with Ethereum ledger or Fabric ledger ) Also upgrade ts-node in the rood package.json because it was causing crashes for the scripts in the ./tools/ directory (such as the webpack bundle name validator script) Depends on: hyperledger-cacti#2259 Depends on: hyperledger-cacti#2265 Co-authored-by: Peter Somogyvari <[email protected]> Signed-off-by: Barnaba Pawełczak <[email protected]> Signed-off-by: Peter Somogyvari <[email protected]>
57b2da2
to
2e922aa
Compare
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
…rledger ledger data stored in supabase by persistence plugins Depends on: hyperledger-cacti#2265 Depends on: hyperledger-cacti#2331 Signed-off-by: Barnaba Pawelczak [email protected]
Add a new plugin for storing hyperledger fabric ledger data into a database
Add functional tests for plugin and data access layer operations.
operating with fabric-all-in-one docker composition
Tests assume any postgres database, but for final deployment postgres or supabase is assumed.
Data fed by this plugin can later be visualized by a GUI application or analyzed directly. ( right now the GUI will have switch to operate either with Ethereum ledger or Fabric ledger )
Depends on: #2259
Depends on: #2265
Signed-off-by: Barnaba Pawelczak [email protected]