Emulator is silent when encountering malformed/incorrect transcript files about botbuilder-tools HOT 19 CLOSED

@emadelwany ; @eanders-ms - can you please take a look?

from botbuilder-tools.

@vishwacsena - I can repro, will triage it for an upcoming release.

from botbuilder-tools.

Is this just with errors? I can't even get a transcript to open in the new emulator when I pull the samples directly from the chatdown repo. I just get a blank tab when I open the transcript file regardless.

I'm using the samples in the repo and the most recent alpha release of the emulator.

from botbuilder-tools.

@szul can you please share the transcript file you're trying to open or which specific sample you were using?

from botbuilder-tools.

@emadelwany My first attempt was with this transcript, and when that didn't work, I generated a transcript from the sample in this repo, but to no avail... and that's a pretty basic sample.

Are there any restrictions on file placement? I put mine in a folder called chats in the root of the app.

I should add that the emulator version/installer is: botframework-emulator-setup-4.0.14-alpha.exe

Windows 10 machine. Node.JS version 8.9.4

from botbuilder-tools.

Hey @szul, did you try changing the file extension to .transcript? I just downloaded your transcript and was able to view it in the Emulator (v4.0.14-alpha) after changing the extension to transcript.

When you generate the transcript using chatdown, try making the extension of the output file .transcript.

Ex:

chatdown sample.chat > sample.transcript

from botbuilder-tools.

@tonyanziano Yeah, they're all .transcript files. Maybe I'll try uninstalling and reinstalling the emulator. Out of curiosity, what's your OS version and Node.JS version?

from botbuilder-tools.

@szul

Node: v8.11.1

OS:
Windows 10, Version 1709, Build 16299.371

from botbuilder-tools.

Yeah, so I'm getting the following in the Developer Tools console when I load any transcript file--whether my own, or one generated from the sample greetings chat. Looks like the chatdown CLI is generating something invalid?

https://1drv.ms/u/s!AsXbi5E9HRsKs5loC0T3TPUw85nIgw

from botbuilder-tools.

What version of chatdown are you running? 1.0.1?

from botbuilder-tools.

@tonyanziano Yes.

from botbuilder-tools.

@szul Could you please share your .transcript file generated from Greetings.chat so I can compare it with my own?

from botbuilder-tools.

@tonyanziano

Gist:
https://gist.github.com/szul/d17f182c45ad09d18f04d67c06cef5ce

Chatdown file:
https://1drv.ms/u/s!AsXbi5E9HRsKs5lp0fe4Xe-7NUjIQg

Transcript file:
https://1drv.ms/u/s!AsXbi5E9HRsKs5lqBE0Cmh-Ig1cUSg

Error message from the Developer Tools looks kind of like bad encoding or something...

from botbuilder-tools.

This is almost certainly a file encoding issue. The emulator needs transcript files to be utf-8 encoded. It will fail on anything else. We need to fix this in the code, but in the meantime can you verify your transcript file is utf-8?

from botbuilder-tools.

Was just able to repro the error by downloading your transcript file, saving it as Unicode big endian encoded, and trying to open it in the emulator.

Seems like @eanders-ms's assumption was right.

from botbuilder-tools.

Is this a chatdown CLI output issue or is it from the way my VSCode is saving the initial *.chat file?

from botbuilder-tools.

We've seen this before, when running the CLI tool from within VSCode's command window. Is that your workflow? Ultimately, it's an emulator issue. It should be more robust about loading text files of different encodings. It shouldn't care about encoding.

from botbuilder-tools.

I’ve done it a couple different ways, but was mostly using the VSCode task workflow to process them. I did it from a Hyper terminal too. I’ll try a few different scenarios and report back the repo steps if that’s helpful.

from botbuilder-tools.

This should be fixed with the latest emulator and the latest CLI tools. We pushed an update across the board to support different file encodings.

from botbuilder-tools.