Closed pauc closed 3 years ago
An example project where this error is occurring: https://github.com/pauc/debug_mutant
@pauc I could reproduce the issue, and develop a workaround on what I consider to be a ruby bug in #1229. I pushed mutant-0.10.30 to rubygems with the workaround.
I've got independent reports that this still happens even on the latest release. I've got no reproduction at this point but will re-open the issue for now.
We can extend the workaround to reset the binmode flag before every write. In the hope it does not evaporate before the write happens.
See: https://github.com/mbj/mutant/pull/1235 which I may merge. asking for my reporters to test that version as we speak.
I've expanded the workaround into a more elaborate one with the release of v0.10.32
. Lets hope its stable now, there is not more to be done from ruby side short of changing to non binary data (moving to UTF-8 JSON as serialzation format).
I've yet to reduce the bug to report it upstream to MRI, but: Mutant needs to stay functioning for a large number of Ruby releases, so this workaround has to stay for the forseeable future.
Some weeks ago mutant stooped to work in my project. It's a Rails 6.1 application running on Ruby 2.6.6 in a Mac OSx machine.
I tried in a docker container and I also tried a new project with fewer dependencies (but both rails projects). Also tried in a linux machine.
Example of the output:
The content of the
Gemfile.lock
isAny clue what is happening?