Fix issue 3446
This PR adds a regression test for issue #3446. Please fork this branch to implement a fix for the issue.
Pull request automatically marked stale!
Is this still active? If so: Could you comment on why a fix should not be based on latest master? What other changes are injected when starting from your branch, as you suggest?
This branch, which is based on master, makes the CI fail by adding a regression test.
We cannot merge changes that cause the CI to fail. Is someone looking into implementing a fix for the underlying issue?
We cannot merge changes that cause the CI to fail. Is someone looking into implementing a fix for the underlying issue?
This raises actually an interesting question: How can we collect reproducers/regression tests for issues that we have on the back-burner? Maybe for now it would make most sense to change the title of this PR to "Add regression test for issue 3446" and convert it to Draft. Then, when someone starts to work on an actual solution, they could pull this PR/branch into their own work. In this way, we would at least make it openly visible that the regression test is already available.
This PR will stay available and is linked directly from the issue. There is no use having it as draft and continuously occupy our attention on the PR board. It's still an issue, hence we find it in the issues. I'll close this for now, please re-open when works are picked up again.