-
Notifications
You must be signed in to change notification settings - Fork 306
fix(satp-hermes): logs in oracle operations #4039
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
base: main
Are you sure you want to change the base?
Conversation
5bbb367 to
a1ede63
Compare
AndreAugusto11
left a comment
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.
@edsonCVN could you please add some very simple tests to make sure everything is working as expected?
|
@edsonCVN, also merge both commits into a single one, update the description of the commit (and the PR) mentioning the linked issue that will be closed once this is merged |
Thank you, I will do it |
Thank you, I will add the test |
424be58 to
82633c4
Compare
cfb9eb8 to
c621fdf
Compare
b0adf70 to
42835c4
Compare
12695e6 to
d3296f6
Compare
d3296f6 to
02768d5
Compare
| @@ -0,0 +1,276 @@ | |||
| import "jest-extended"; | |||
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 tests are insufficient. We need to assert that, running a gateway with an oracle component, logs are sent to the stdout. The current test uses mocks and therefore does not give us the confidence that the current functionality works
RafaelAPB
left a comment
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.
Please make sure to add robust tests
02768d5 to
98fa148
Compare
Introduce logging in the Oracle operations, similar to what we already
have in the SATP operations. Each operation include the following log
entries:
1. Log "init" before starting the operation.
2. Log "exec" immediately before executing the operation.
3. After the operation is executed:
- Log "done" if it was successful.
- Log "fail" if it failed.
Closes hyperledger-cacti#3946
Signed-off-by: Edson da Veiga <edson.da.veiga@tecnico.ulisboa.pt>
98fa148 to
9831a59
Compare
Signed-off-by: Edson da Veiga <edson.da.veiga@tecnico.ulisboa.pt>
Introduce logging in the Oracle operations, similar to what we already
have in the SATP operations. Each operation include the following log
entries: