Converting unix timestamps in milliseconds occurs Assertion failed!

[WiVi71]

Edit

This bug was caused by too large a number. not strftime with "-R"

To Reproduce
ECHO {"published_at": 1461625253393} | jq ".published_at/1000 | strftime(\"%Y-%m-%d\")"
Converting unix timestamps in second works.
ECHO {"published_at": 1461625253393} | jq ".published_at | strftime(\"%Y-%m-%d\")"
But converting unix timestamps in milliseconds occurs unexpected type of error.

Expected behavior
jq should alart that the number is too big.

Environment (please complete the following information):

• Jq-1.6-Windows10

---

Wrong jq command with -R options and strftime occurs "Assertion failed!"

To Reproduce
echo {"updateTime":1589179644052} | jq -R "fromjson? | .updateTime | strftime(\"%B %d %Y\")"

Expected behavior
Jq should print "compile error" or "syntax error" or something else.

[itchyny]

What's the result of jq -n "1461625253393 | gmtime" ?

[WiVi71]

jq -n "1461625253393 | gmtime"
will print "jq: error (at ): errror converting number of seconds since epoch to datetime"

jq -n "1461625253393/1000 | gmtime"
will print

[
  2016,
  3,
  25,
  23,
  0,
  53.39299988746643,
  1,
  115
]

[itchyny]

Thank you.

[itchyny]

For a record, echo '{"updateTime":1589179644052000000}' | jq -R "fromjson? | .updateTime | strftime(\"%B %d %Y\")" is the reproducible command on macOS, and this command should print converting number of seconds since epoch to datetime. #2125 fixes the assertion failure but the command exits silently due to #1859.