Tobias Wochinger

Exalate commented: wochinge commented: Thanks for writing this detailed overview! 💯 In my opinion we need both. I see conversation tests as integration tests. From that perspective it makes sense...

Exalate commented: wochinge commented: > So you'd have some sort of mock custom action instead - not actually sure how our customers handle this, though i'd imagine they just have...

Exalate commented: wochinge commented: > If I am not mistaken these dispatched utterances appear neither in training data nor in current test stories, or do they? No, they don't. Besides...

Exalate commented: wochinge commented: Enable has done a spike on conversation testing and then benched it for 3.0 after talking to a few customers as we've realized that it doesn't...

@kalkbrennerei Would you mind jumping in and fix the `poetry.ock` so we can get this in?

@neo-alex How is it going? Can I help with the required changes?

@tmbo I don't think it's crucial for 2.0 and everybody has enough on their plate already. Will add it to my todo list anyway to make sure this gets wrapped...

@alexmic I think there are two things here: Number 1 is that Duckling does not currently not actually use specified timezones (see https://duckling.wit.ai/ , Limitations) > Timezones are parsed, but...

@akshay2000 > However, it doesn't work for relative times. For example, "last 2 hours" will give wrong results if we replace the Duckling timezone with the user timezone. Yes, but...

> As the bot sits on the client device, it can send timezone along with sender id and message. That highly depends on the input channel, doesn't it?