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.

Installing a package while a bot is running results in multi-project build errors

See original GitHub issue

Describe the bug

If you install a package while a bot is running the underlying process isn’t fully killed. As a result Composer gets into a bad state where the Restart bot button becomes Start bot but there’s already an process running.

Version

Version: 2.0.0-nightly.241057.db66154 Electron: 8.2.4 Chrome: 80.0.3987.165 NodeJS: 12.13.0 V8: 8.0.426.27-electron.0

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. Create or open a bot and start it
  2. Install a package (I did the Teams package)
  3. Note how the Restart bot button becomes Start bot after the package is installed
  4. Click the Start bot button

Expected behavior

The button should either be Start bot where the underlying process is actually killed, or it should be Restart bot assuming restart rebuilds with any delta in the packages

Screenshots

Additional context

Error occurred building the bot

Message: Command failed: dotnet build TeamsTest.csproj Command: dotnet build TeamsTest.csproj Stack Trace: Error: Command failed: dotnet build TeamsTest.csproj

at ChildProcess.exithandler (child_process.js:308:12)
at ChildProcess.emit (events.js:210:5)
at maybeClose (internal/child_process.js:1021:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)

Output: Microsoft ® Build Engine version 16.9.0+57a23d249 for .NET Copyright © Microsoft Corporation. All rights reserved.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
hatpickcommented, Apr 30, 2021

@mareekuh @emivers8 @sgellock I think it’s important to let the user know that installing a new package requires stopping their bot, if they agree, then composer stops their bot and continues with the installation, if not composer informs the user that they need to stop their running bot before any installation can happen.

0reactions
sgellockcommented, May 7, 2021

Shiproom - approved

Read more comments on GitHub >

github_iconTop Results From Across the Web

Errors in NPM install · Issue #7707 · microsoft/fluentui - GitHub
Environment Information Package version(s): latest clone from GitHub Browser and OS versions: Windows 10 Actual behavior: Errors during npm ...
Read more >
`pip install` Gives Error on Some Packages - Stack Overflow
Some packages give errors when I try to install them using pip install . This is the error when I try to install...
Read more >
Triggering downstream pipeline on the same project results in ...
Summary An attempt to create a downstream multi-project pipeline on the same project results in an error.
Read more >
Attended license update package, install failed - Robot
In the bot tray it shows my app, but when I update my app on this tray, it shows UIPath Robot Error Failed...
Read more >
Configuring Hardware and Communication Connections STEP 7
you when installing and commissioning the software. ... Displaying the Version of the CPU Operating System in the 'Hardware Catalog' window .......... 40....
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