This is a follow up to #397. Check, whether the fix suggested inside PR is needed or some other solution needs to be there

—
Reply to this email directly or view it on GitHub.