You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried running the test-cases of which 4 are failing.
processBlockEvent
1) should return without error
✓ should throw an error if it has already been in process
✓ should raise new channel notification if genesis has not already been stored yet
2) should raise update channel notification if config block is processed
3) should be done without any errors when config block doesn't have any payload in last updated data
4) should be done without any errors when _lifecycle block is processed
Has anyone faced the same issue while running the testcases? Please help, in fixing these issues.
What did you expect to happen?
Expected all the test cases would pass.
How can we reproduce it (as minimally and precisely as possible)?
Need to run the test- cases as per the ReadMe.
Anything else we need to know?
No response
OS version
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
The text was updated successfully, but these errors were encountered:
Test cases are failing due to Buffer.from() function in syncServices.ts. Where Buffer.from() expects object types like String, Array, Buffer, arrayBuffer but it is getting an object of another type. Solution can be giving JSON.stringify() for the object in Buffer.from().
What happened?
I have tried running the test-cases of which 4 are failing.
processBlockEvent
1) should return without error
✓ should throw an error if it has already been in process
✓ should raise new channel notification if genesis has not already been stored yet
2) should raise update channel notification if config block is processed
3) should be done without any errors when config block doesn't have any payload in last updated data
4) should be done without any errors when _lifecycle block is processed
Has anyone faced the same issue while running the testcases? Please help, in fixing these issues.
What did you expect to happen?
Expected all the test cases would pass.
How can we reproduce it (as minimally and precisely as possible)?
Need to run the test- cases as per the ReadMe.
Anything else we need to know?
No response
OS version
The text was updated successfully, but these errors were encountered: