Babe block producing hacks

[akru]

Question

Is it possible to fix or escape this kind of error?

0-05-01 15:08:40 Timeout fired waiting for transaction pool to be ready. Proceeding to block production anyway.
2020-05-01 15:08:40 🎁 Prepared block for proposing at 119981 [hash: 0x093fdea4e64a146cdcda1b621d7650471190a34ad6a0a186698bf8bfb9b246d0; parent_hash: 0x49df…b546; extrinsics (2): [0x5e40…0f50, 0xf5fd…bb3c]]
2020-05-01 15:08:40 🔖 Pre-sealed block for proposal at 119981. Hash now 0x03f7d0d9e3e67fa58216e68a3fb168c27c8a5fc9f7d14e7ea2fbd85ccc44ef84, previously 0x093fdea4e64a146cdcda1b621d7650471190a34ad6a0a186698bf8bfb9b246d0.
2020-05-01 15:08:40 Error with block built on 0x49df8a4a688bfbc635eb3a69baa75344c8ae39bb5869e83a5bdb460059fbb546: ClientImport("Expected epoch change to happen at 0x03f7d0d9e3e67fa58216e68a3fb168c27c8a5fc9f7d14e7ea2fbd85ccc44ef84, s158833492")

What is the best practice to fix it?

[bkchr]

There is no hack for this at the moment. Sorry. I assume this is on a dev chain?

[akru]

Sure, but I catch it sometimes and better to known how to work with it.

Do you have some workaround recommendation?

[bkchr]

Sadly there is currently not solution for dev chains. You change the session length to make sure that you don't run into this (Babe requires that one block per session is build). Otherwise, there is no solution.