Skip to content

Dotnet may fail when trying to update tools just after it was updated from package manager #572

@thecatcore

Description

@thecatcore

Erroneous Behavior

Dotnet step tried to update a tool "-------------------------------------" which is the separator, just after updating it from package manager.
I don't have any tools installed so it simply should not have tried running.

Expected Behavior

Dotnet step doesn't run because I don't have any tools installed.

Steps to reproduce

Run topgrade when a dotnet update is available through the package manager.

Possible Cause (Optional)

When installing or updating dotnet through the package manager, it warns the user about a command running in the background to finish setuping it after the package manager is done running.
My guess is that in this case, the background command wasn't done when topgrade arrived to the dotnet step, and because of this there might have been more lines logged before the list of tools than usual (2, which are skipped in topgrade).

Problem persists without calling from topgrade

  • Yes
  • No

Did you run topgrade through Remote Execution

  • Yes
  • No

If yes, does the issue still occur when you run topgrade directlly in your
remote host

  • Yes
  • No

Configuration file (Optional)

Additional Details

  • Operation System/Version

Pop!_OS 22.04

  • Installation

cargo/crates.io

  • Topgrade version (topgrade -V)
    12.0.2

Verbose Output (topgrade -v)


Metadata

Metadata

Assignees

No one assigned

    Labels

    C-bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions