It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

@justinmc @TahaTesser It seems like that you have a bit more context to the target issue. Would you like to take a look at this PR?

@ayyoub-coder
Thanks for the contribution. Could you please provide more details in the description how this address the issue? It seems like you've linked a closed issue. The issue was fixed by @bleroux PR which reverted a change.

It seems like there are a lot of tests failures as well.

Thanks for your contribution 🙏

Closing this PR as the issue was fixed by the following revert: #169497.