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
Summary:
Duplicate Transfer Response Header validation failing on QA Framework. Header FSPIOP-Source should match switch and not the responding FSP-Id.
Severity:
High
Priority:
Critical
Expected Behavior
Duplicate Transfer Response Header validation Header FSPIOP-Source should match switch.
lewisdaly
changed the title
Duplcate Transfer Response Header validation failing on QA Framework
Duplicate Transfer Response Header validation failing on QA Framework
Jul 24, 2019
It seems that the central-ledger isn't setting this uriParams field once again, and the id is undefined in the notification handler on ml-api-adapter, causing downstream requests to fail and the error we see above.
Summary:
Duplicate Transfer Response Header validation failing on QA Framework. Header FSPIOP-Source should match
switch
and not the responding FSP-Id.Severity:
High
Priority:
Critical
Expected Behavior
Duplicate Transfer Response Header validation Header FSPIOP-Source should match
switch
.Steps to Reproduce
duplicate_handling
.transfers
.original_transfer_at_committed
.Send Transfer
:duplicate_handling
.transfers
.original_transfer_at_committed
.Duplicate Transfer
:Specifications
Notes:
PR:
The text was updated successfully, but these errors were encountered: