Miller complaining about malformed timezone

[spmundi]

I am running mlr-6.13.0-dev built on windows11

I have the same build running on three OSs: two windows11, one windows10.
On the box where I built the executable everything seems ok.
On the other two I get
"mlr: TZ environment variable appears malformed: "America/New_York"

(The TZ env variable is set the same on all three boxen)

I am at a loss to understand this behavior. It seems wrong, but regardless, why do I get different behavior from the same executable with the same TZ ?

Rob Stevens

[spmundi]

I have my own followup.
The go documentation (version 1.15) talks about adding this line:
import _ "time/tzdata"
to the go code which supposedly includes the timezone database into the code. I don't know where in the miller code that would go.

As far as I can see, the two boxes which display this error have the tzdata package (from cygwin) included, as does the third where I do not see this error. The third cygwin install, where I do not see the error, has many many more packages installed than the other two.

I have also found that mlr on macos 13.7.4 also displays this eror when the TZ env variable is explicitly set (it normally is not explicitly set in my environment)

My conclusion is that some package or other installs a comprehensive timezone database, but I don't know which cygwin package that would be.

Any thoughts?

[johnkerl]

@spmundi yeah, I guess Miller has always been implicitly getting the timezone data from the OS -- if it's present.

I like your:

import _ "time/tzdata"

-- I'll give this a try!