The error is still expected to appear. What we fixed is that a bug that was triggered by this error handling. But, it's still interesting whether this error appears newly in 5.19.x. Did it appear on the earlier, 5.18.x kernels, too?