duckling suddenly can’t parse local timestamp

This happens when ~you don’t pass a timezone to the~ duckling ~configuration and it~ tries to get your time using reference time.

I thought this was my new computer sending weird timestamps, but it’s happened on both old and new and was recently reported by a community member.

Warning:

2019-07-13 14:24:32 WARNING  root  - Could not parse timestamp fc976cc217934115b1f4b5d44b236d80. Instead current UTC time will be passed to duckling. Error: invalid literal for int() with base 10: 'fc976cc217934115b1f4b5d44b236d80'

[msamogh]

when you don’t pass a timezone to the duckling configuration

I did pass a timezone and still got the same error.

[fanlu]

Yes, I think there is no problem with timezone. this is my test case below.

curl -XPOST http://0.0.0.0:8000/parse --data 'dims=time&lang=en&l&tz=Asia/Shanghai&text=tomorrow morning&reftime=1573475247000'
[{"body":"tomorrow morning","start":0,"value":{"values":[{"to":{"value":"2019-11-12T12:00:00.000+08:00","grain":"hour"},"from":{"value":"2019-11-12T00:00:00.000+08:00","grain":"hour"},"type":"interva
l"}],"to":{"value":"2019-11-12T12:00:00.000+08:00","grain":"hour"},"from":{"value":"2019-11-12T00:00:00.000+08:00","grain":"hour"},"type":"interval"},"end":16,"dim":"time","latent":false}]
curl -XPOST http://0.0.0.0:8000/parse --data 'dims=time&lang=en&l&tz=Europe/Berlin&text=tomorrow morning&reftime=1573475247000'
[{"body":"tomorrow morning","start":0,"value":{"values":[{"to":{"value":"2019-11-12T12:00:00.000+01:00","grain":"hour"},"from":{"value":"2019-11-12T00:00:00.000+01:00","grain":"hour"},"type":"interval"}],"to":{"value":"2019-11-12T12:00:00.000+01:00","grain":"hour"},"from":{"value":"2019-11-12T00:00:00.000+01:00","grain":"hour"},"type":"interval"},"end":16,"dim":"time","latent":false}]