kmKowdz / BBCI-Prototype

A prototype for my Blockchain-based Continuous Integration system.
Apache License 2.0
1 stars 0 forks source link

fix record action #8

Open kmKowdz opened 3 years ago

kmKowdz commented 3 years ago

when added with additional parameter for payload, i get these as a result:

image

kmKowdz commented 3 years ago

when added with additional parameter for payload, i get these as a result:

image image

next bug:

image

kmKowdz commented 3 years ago

when added with additional parameter for payload, i get these as a result: image image

next bug:

image

if removed: image

image

kmKowdz commented 3 years ago

however, when list action is performed, i retrieve the ff:

image

kmKowdz commented 3 years ago

however, when list action is performed, we retrieve:

image

image

kmKowdz commented 3 years ago

Hypothesis: Ibang handler yung nagpaprocess ng transaction

kmKowdz commented 3 years ago

Hypothesis: Ibang handler yung nagpaprocess ng transaction

Action Plans:

Solution 1 Result:

Test Folder: image

image

The test folder contains integration and smoke tests of which the state address from the GET request below is present in the integration_tools.py

image

kmKowdz commented 3 years ago

Hypothesis: Ibang handler yung nagpaprocess ng transaction

Action Plans:

  • [x] Find all XO-related files sa current working directory and find the line that causes the transaction to fail
  • [x] Create a new folder for BCI and change the xo python files with bci to make bci handler distinguishable from xo handler

Solution 1 Result:

Test Folder: image

image

The test folder contains integration and smoke tests of which the state address from the GET request below is present in the integration_tools.py

image

Add'l action: deleted the test folder and nose.cfg

Solution 2 result:

image image image

I get 'PENDING' as a status response from the validator which means that the validator is not processing the request.

kmKowdz commented 3 years ago

Hypothesis: Ibang handler yung nagpaprocess ng transaction

Action Plans:

  • [x] Find all XO-related files sa current working directory and find the line that causes the transaction to fail
  • [x] Create a new folder for BCI and change the xo python files with bci to make bci handler distinguishable from xo handler

Solution 1 Result: Test Folder: image image The test folder contains integration and smoke tests of which the state address from the GET request below is present in the integration_tools.py image

Add'l action: deleted the test folder and nose.cfg

Solution 2 result:

image image image

I get 'PENDING' as a status response from the validator which means that the validator is not processing the request.

image

Try the solution suggested here: https://stackoverflow.com/questions/59185556/hyperledger-sawtooth-block-always-pending