Skip to main content
update dfor the current state of things.
Source Link
Tbaut
  • 253
  • 1
  • 6

While Alex Bean's answer would be perfectly right if things were running normally, in this particular case, the question was asked because something went wrong, while using the latest node-template v9.30

The issue here is that the RuntimeEvent could not be decoded by the api, and hence the UI. Because of this the Error event could also not be decoded and the UI was therefore only showing the green notification that the extrinsic was in a block, but NOT followed by any subsequent red notification, that would mean that something went wrong at run time. This is something that will be dealt with inhas subsequently been fixed at the pjs api level, or whenanother fix would have been if the node-template usesused weight v2.

While Alex Bean's answer would be perfectly right if things were running normally, in this particular case, the question was asked because something went wrong, while using the latest node-template v9.30

The issue here is that the RuntimeEvent could not be decoded by the api, and hence the UI. Because of this the Error event could also not be decoded and the UI was therefore only showing the green notification that the extrinsic was in a block, but NOT followed by any subsequent red notification, that would mean that something went wrong at run time. This is something that will be dealt with in the pjs api level, or when node-template uses weight v2.

While Alex Bean's answer would be perfectly right if things were running normally, in this particular case, the question was asked because something went wrong, while using the latest node-template v9.30

The issue here is that the RuntimeEvent could not be decoded by the api, and hence the UI. Because of this the Error event could also not be decoded and the UI was therefore only showing the green notification that the extrinsic was in a block, but NOT followed by any subsequent red notification, that would mean that something went wrong at run time. This is something that has subsequently been fixed at the pjs api level, another fix would have been if the node-template used weight v2.

Source Link
Tbaut
  • 253
  • 1
  • 6

While Alex Bean's answer would be perfectly right if things were running normally, in this particular case, the question was asked because something went wrong, while using the latest node-template v9.30

The issue here is that the RuntimeEvent could not be decoded by the api, and hence the UI. Because of this the Error event could also not be decoded and the UI was therefore only showing the green notification that the extrinsic was in a block, but NOT followed by any subsequent red notification, that would mean that something went wrong at run time. This is something that will be dealt with in the pjs api level, or when node-template uses weight v2.