I checked the upstream git repository and the dump_errors! method is
still the same compared to version that was reported this bug. So in
theory, the problem still persists. I also did not find any upstream bug
for this issue, did someone do that? If no, I'd kindly ask to the
affected people to do so.

This bug was filed more than a decade ago and it is still open which
makes me think that this is not so important and we could close it out.
For now, let's keep it open to see if it gets any traction.

-- 
Lucas Kanashiro

Reply via email to