search

microsoft / botframework-sdk

Bot Framework provides the most comprehensive experience for building conversation applications.
MIT License
7.5k stars 2.44k forks source link

Debug Symbols in .dialog file #6229

Open SChandlee-ARIFleet opened 3 years ago

SChandlee-ARIFleet commented 3 years ago

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.

Version

What package version of the SDK are you using.

Describe the bug

I am using VScode and installed the Debug Dialog extension. I am able to start my bot through the debugger. I set a breakpoint within my main .dialog file. The breakpoint is not recognized "no symbols have been loaded for this document".

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Give a clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

Additional context

Add any other context about the problem here.

Tracking Status

Dotnet SDK [TODO]()

Javascript SDK [TODO]()

Python SDK [TODO]()

Java SDK [TODO]()

Samples [TODO]()

Docs [TODO]()

Tools [TODO]()

jwiley84 commented 3 years ago

Hi @SChandlee-ARIFleet Thank you for reporting this. I"m going to attempt a repro, see if I can figure out what's going on. Does this happen with any bot you try, or one specific type?

SChandlee-ARIFleet commented 3 years ago

Thanks Jessica! I only tried it with a Bot Composer/Scratch project.

From: Jessica Wailes @.> Sent: Thursday, March 11, 2021 2:01 PM To: microsoft/botframework-sdk @.> Cc: Chandlee, Scott @.>; Mention @.> Subject: Re: [microsoft/botframework-sdk] Debug Symbols in .dialog file (#6229)

EXTERNAL EMAIL

Hi @SChandlee-ARIFleethttps://github.com/SChandlee-ARIFleet Thank you for reporting this. I"m going to attempt a repro, see if I can figure out what's going on. Does this happen with any bot you try, or one specific type?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/microsoft/botframework-sdk/issues/6229#issuecomment-796969048, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM3S2YHFXEBU2AIY6QYM5MTTDEAPHANCNFSM4Y4UHD7Q.

SChandlee-ARIFleet commented 3 years ago

Hi @jwiley84 , checking in to see if you were able to make any progress.

Thanks, Scott

jwiley84 commented 3 years ago

Apologies, I've been out.

I'm going to need to get repro steps from you to properly reproduce your error.

SChandlee-ARIFleet commented 3 years ago

VSCODE Version: 1.54.3 (user setup) Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8 Date: 2021-03-15T10:55:45.459Z Electron: 11.3.0 Chrome: 87.0.4280.141 Node.js: 12.18.3 V8: 8.7.220.31-electron.0 OS: Windows_NT x64 10.0.18363

Bot Framework Dialog Debugger v1.0.3

C# ms-dotnettools.csharp v1.23.9

Launch.json { "configurations": [ { "type": "bot", "request": "launch", "name": "Debug Bot (.NET Core)", "command": "dotnet", "args": [ "run", "--no-build", "--", "--debugport", "0" ] } ] }

BOT Framework Composer v1.3.1 'Use custom runtime'

VSCode Open folder where runtime was built Set breakpoint in [botprojectname].dialog Start Debugger breakpoint will be an open circle instead of closed circle image

Connect emulator to the debug port breakpoints set in .net files will work

**If there is a way to set this up without the "custom runtime" step, I am open to any recommendations

@jwiley84 I hope this is enough information. If not, let me know

carlosscastro commented 3 years ago

Update: @jwiley84 is working on this right now.

jwiley84 commented 3 years ago

Using a simple EchoBot, I am able to repro this. I'm going to try to make a LUIS bot, and see if this is limited to echo, or if it's across the board. Thank you for your patience.

carlosscastro commented 3 years ago

Thanks @jwiley84 . This means that we have a bug in the debugging library or somewhere in the adaptive / declarative library. Adding to R14 backlog for the dev team to be aware, investigate and fix. Note that our next release to happen in late April is already feature complete so this would be released afterwards unfortunately. If in the process of investigating we find a workaround or have a fix in a nightly build, we';ll update this bug with that information.