Kevin Burke

(This work was sponsored by [Segment](https://segment.com))

The 2.7.1 issue should be fixed now.

Bytes that can’t be represented directly in a Go string are replaced by “\x01” or equivalent, which is four bytes. Since the byte representation of a tarball or a photo...

You should be able to use either the `--no-metadata` flag or the `--modtime=X` flag where X is some constant timestamp. See for example https://github.com/kevinburke/go-bindata/blob/master/testdata/Makefile#L15 (I set up the tests to...

Ah, got it, you want to avoid regenerating the output if the input hashes are the same. I already compute the hashes, it shouldn't be too crazy to support that...

I'm working on a fix, but just remembered the way I avoid this usually is by using the mtimes in a Makefile to avoid invoking go-bindata altogether, for example https://github.com/kevinburke/logrole/blob/master/Makefile#L64

I just merged a patch to kevinburke/go-bindata master, it looks good locally, though I might give it a few days before putting it in a tagged release.

(note just for myself, since I have to look this up every time; this isn't broken on my fork because I never added a `-fs` mode; the debug tests work...

Good idea, just fixed this here. https://github.com/kevinburke/go-bindata/commit/c938b041d272dc5b5ad53b4884cbe59083cc0359 (The red "X" is because tests on Go 1.12 now generate a different file than Go 1.13; fixed in a later commit.)

I doubt this is a go-bindata issue, but in any case you are going to need to be more specific about what you are trying to do, what you expect...