Closed sandreim closed 3 days ago
cc @alindima
Also seen on Kusama: https://grafana.teleport.parity.io/goto/URufflmHR?orgId=1
This happens under normal operation.
Suppose an allowed_ancestry_len of 2, so we allow up to two ancestors from an active leaf. Prospective parachains maintains fragment chains for the inactive leaves also if they're within the implicit view (if the relay parent is within the allowed_ancestry_len of an active leaf). So when you get a new candidate built of the latest active leaf, when you try to introduce it to the fragment chains of the ancestors, you'll get this log. Notice it's only a debug log. No error here.
I should revisit some of these logs and set them as trace level. I was probably too eager with the debug logs and set too many :D
Closing this issue. Opened an issue for tracking the revisiting of the logs: https://github.com/paritytech/polkadot-sdk/issues/6172
On Paseo we observe that some candidates are reject because the relay parent (0xec3fa2c08635ff24f23a905e66af5b434141f29a629bb52b71db5c266da9022f) is not in scope, but the relay parent is actually in scope (notice the block import)
https://grafana.teleport.parity.io/goto/n7OvB_mHg?orgId=1