James Hillyerd
James Hillyerd
It seems `tee` can be used as a workaround for now: ```sh cargo chef cook --recipe-path recipe.json | tee /tmp/cook.txt ```
I think that assuming the presence of a TTY means it is always an interactive session is a mistake, the build shouldn't break because of it.
In my case, I'm using (testing really) Hashicorp Waypoint, which starts up a build runner as a docker container within a Nomad cluster. That runner apparently uses kaniko to build...
If it helps, I have `gofmt = 'gopls'` in my setup call.
Interesting, I am on 0.7.0. Perhaps there is something wrong with my distro's package. I poke around a bit when I have more time.
Currently enmime trusts the Content-Type when it comes to text/plain vs text/html, so this is working as expected. I'm not necessarily opposed to trying to detect and fix the content...
This sounds good to me.
Bit of fuzzing added in #242, but it is unlikely to exercise much of the MIME parsing codebase.
Yeah, this would be a good use of options, blocked by #90
Apologies for slow response. I agree, using detectTextHeader to not treat it at multipart, and adding a new error to error.go would be a good approach.