question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

No runtime version available when ejecting bot runtime

See original GitHub issue

Describe the bug

When trying to eject the bot runtime, no runtime version is available to select. The runtime versions field is empty. Since the selection is not available, the runtime cannot be ejected, which blocks (amongst others) creating custom actions.

Version

image

The issue is producing in a nightly build version.

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. Make a new bot based on the sample Echobot.
  2. Navigate to the Settings page and select Runtime Config.
  3. Toggle Use custom runtime in the Bot runtime settings field and select Get a new copy of the runtime code.
  4. The dialog box which appears has no runtime versions listed.

Expected behavior

There should be the option in the dialog box to select C# and click OK, after which the ejected runtime directory should show in the Runtime code location field.

Screenshots

image

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
VanyLawcommented, Jun 22, 2020

Hi @tonyanziano, It seems like the electron load plugins folder error. I tested in local and found the plugins our nightly-build version loaded was previously. FYI. For example, the azure function plugin name was changed to @bfc/plugin-azure-functions-publish. image

I try to build electron locally by yarn dist:full, but it fail to load plugins folder either. I try to run yarn start:electron locally and find the pluginsDir is [Composer folder]\Composer\packages\electron-server, but the path need to be [Composer folder]\Composer\packages\electron-server\dist\win-unpacked\resources\app.asar.unpacked.

I am not sure how to debug in electron, could you help to take a look? Thanks!

Read more comments on GitHub >

github_iconTop Results From Across the Web

Robot Licensing Failed. There are no available runtime ...
Hi everyone, When I run any process by Schedule or manually, status is pending all the time. In the process information, you can...
Read more >
The extension APIs in Bot Framework Composer
Runtime templates: extensions can provide a runtime template used when ejecting from Composer. Combining these endpoints, it's possible to ...
Read more >
Could not load file or assembly System.Runtime, Version=4.1 ...
I updated my company's build server to VS 15.5 when it was released and triggered a rebuild and deployment (through our on-prem TFS)...
Read more >
Upgrading Mule Runtime Engine(Versions 3.x to 3.n)
If there are no relevant changes between the Mule Runtime version in which ... to work properly (these would be found in the...
Read more >
WALL-E - Wikipedia
WALL-E is a 2008 American computer-animated science fiction film produced by Pixar Animation Studios and released by Walt Disney Pictures. ... He is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found