Summary of bug
The Cosmos REST API returned a proposal with invalid voting_start_time and voting_end_time fields while the proposal was in voting stage. For this reason, the Cosmos Network Data Transformer crashed. The log can be seen below:
'As is' behaviour
Cosmos Network Data Transformer stops working when a malformed date/time value for the voting_start_time and voting_end_time fields is obtained from the Cosmos Network Monitor.
'To be' behaviour
Cosmos Network Data Transformer handles malformed date/time value for the voting_start_time and voting_end_time fields is obtained from the Cosmos Network Monitor. We also have to investigate what this entails for the alerter since these fields are used as a criteria for some alerts.
Steps to reproduce
Add a valid Cosmos-Hub node in PANIC and enable network monitoring.
Acceptance criteria
Given: PANIC started and a Cosmos-Hub node is added with network monitoring enabled
When: Obtained proposals
Then: Proposals are parsed correctly and alerts are raised as intended.
Summary of bug
The Cosmos REST API returned a proposal with invalid
voting_start_timeandvoting_end_timefields while the proposal was in voting stage. For this reason, the Cosmos Network Data Transformer crashed. The log can be seen below:'As is' behaviour
Cosmos Network Data Transformer stops working when a malformed date/time value for the
voting_start_timeandvoting_end_timefields is obtained from the Cosmos Network Monitor.'To be' behaviour
Cosmos Network Data Transformer handles malformed date/time value for the
voting_start_timeandvoting_end_timefields is obtained from the Cosmos Network Monitor. We also have to investigate what this entails for the alerter since these fields are used as a criteria for some alerts.Steps to reproduce
Add a valid Cosmos-Hub node in PANIC and enable network monitoring.
Acceptance criteria
Given: PANIC started and a Cosmos-Hub node is added with network monitoring enabled
When: Obtained proposals
Then: Proposals are parsed correctly and alerts are raised as intended.