Tutorial Form Error: Could not parse timestamp

I am following

(my input) $ docker run -p 8000:8000 rasa/duckling no port specified, defaulting to port 8000 Listening on http://0.0.0.0:8000

(my input in another terminal) rasa run actions& 2019-07-12 14:13:55 INFO rasa_sdk.endpoint - Action endpoint is up and running. on (‘0.0.0.0’, 5055)

(my input in another terminal I type) rasa shell -m models --endpoints endpoints.yml 2019-07-12 14:16:41 INFO root - Starting Rasa Core server on http://localhost:5005 Bot loaded. Type a message and press enter (use ‘/stop’ to exit): Your input ->

(This is where I hit a snag) (my input) hello WARNING root - Could not parse timestamp c1a3c1b0ba984394b3e46cab5cfc10ef…

Any further inputs result in sorry, I didn’t understand you, please try input something else

Questions: What am I doing wrong?

Hey @DexterDSilva, I’ve just started running into this too — as far as I know, this is a bug in duckling we have to look into. However, as this bot doesn’t parse dates, it shouldn’t be causing the fallback stuff, just annoying warnings that don’t apply here.

I think what’s causing the fallback is that you didn’t give it any input here:

14:16:41 INFO root - Starting Rasa Core server on http://localhost:5005 Bot loaded. Type a message and press enter (use ‘/stop’ to exit): Your input ->

Here’s an example I had with this bot today:

Your input ->  hi
2019-07-13 14:24:13 WARNING  root  - Could not parse timestamp f8a32f568ceb43f1b15d2536798684e6. Instead current UTC time will be passed to duckling. Error: invalid literal for int() with base 10: 'f8a32f568ceb43f1b15d2536798684e6'
Hello! I am restaurant search assistant! How can I help?
Your input ->  i want to book a restaurant
2019-07-13 14:24:27 WARNING  root  - Could not parse timestamp 50d4e8aa274e49a788dd3186db7708e4. Instead current UTC time will be passed to duckling. Error: invalid literal for int() with base 10: '50d4e8aa274e49a788dd3186db7708e4'
what cuisine?
Your input ->  chinese
2019-07-13 14:24:30 WARNING  root  - Could not parse timestamp 0cea23002975466f9ecb36e0971242d2. Instead current UTC time will be passed to duckling. Error: invalid literal for int() with base 10: '0cea23002975466f9ecb36e0971242d2'
how many people?
Your input ->  3

@erohmensing thank you for your reply.

What was throwing me was the ‘could not parse timestamp message…’ and I thought I was doing something wrong. Hence, I did not bother with the rest.

Now I shall go back and run it with a smile :slight_smile:

No worries. I’ve created an issue to hopefully figure out what’s going on there :slight_smile: you can safely ignore it for now!

1 Like

I am seeing the same warning ’ Could not parse timestamp '. Please let us know when it’s fixed on either the duck ling or Rasa side :slight_smile:

2 Likes

Hi Guys - Is there any update on this issue? I still see this issue. Please share if there is a work around. Thanks. Vijay

Hi @erohmensing , any update on this ? Thanks

As far as I know, the warning still shows, but the bot parses the information correctly. You can test this with rasa shell nlu

hi, i have issue of timeout. because of this error i am not getting output from custom action

Hi @Sharada201, this is not the reason for not getting output. We are aware of that issue and a fix is building right now :slight_smile:

Any update?

1 Like

receiving that as well

rasa input: “tomorrow at 9 pm”

Server logs Could not parse timestamp 12f5fc0c021e452694ae290479c75888. Instead current UTC time will

rasa x output

  • null{“time”:“2020-02-07T21:00:00.000+02:00”}

configuration: language: en pipeline:

  • name: DucklingHTTPExtractor url: ‘http://0.0.0.0:8000’ dimensions: time timezone: Asia/Jerusalem locale: he_IL
  • name: EntitySynonymMapper
  • name: ResponseSelector retrieval_intent: out_of_scope policies:
  • name: EmbeddingPolicy max_history: 10 epochs: 20 batch_size:
    • 32
    • 64
  • max_history: 6 name: AugmentedMemoizationPolicy
  • core_threshold: 0.3 name: TwoStageFallbackPolicy nlu_threshold: 0.8
  • name: FormPolicy
  • name: MappingPolicy