fsprojects / fsprojects/Paket

Paket prints too many restore information with `--no-restore` in `dotnet build --no-restore`

Open
#3,449 7 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
F#
Stars
2.1k
Forks
528
Avg merge
1d 12m
Merged PRs (30d)
54

Description

Description

Paket prints too many restore information with --no-restore in dotnet build --no-restore
This is the case with the latest 5.193.0
The older 5.163.2 works as expected/desired.

Repro steps

Use attached project with latest Paket.5.193.0

Invoke commands:

.paket\paket.exe restore
dotnet restore
dotnet build --no-restore
Expected behavior

Output of the last command dotnet build --no-restore should be:

Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Test1 -> C:\Users\rjq\Desktop\_181206_105136_pk\Paket.5.193.0\bin\Debug\netstandard2.0\Test1.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)
Actual behavior

Output of the last command dotnet build --no-restore contains too many information about restoring:

Microsoft (R) Build Engine version 15.9.20+g88f5fadfbe for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Paket version 5.193.0
  The last restore is still up to date. Nothing left to do.
  Performance:
   - Runtime: 128 milliseconds
  Test1 -> C:\Users\rjq\Desktop\_181206_105136_pk\Paket.5.193.0\bin\Debug\netstandard2.0\Test1.dll

Build succeeded.
    0 Warning(s)
    0 Error(s)

The picture is even worse if we build a solution with many projects (30+ in our case).
For every project we get 1 useful log line about DLL and 4 noise lines about restoring.

Known workarounds

I do not know any workarounds. For the moment I prefer to stay with older
Paket.5.163.2 which works as expected. The project is attached, too.


Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the attached Paket.5.193.0 project and reproduce the issue using .paket\paket.exe restore, dotnet restore, and dotnet build --no-restore. Trace the Paket output produced during the final build and compare it with Paket.5.163.2. Done means dotnet build --no-restore retains the build result while omitting the restore-status and performance lines.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
build-system, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.