fsprojects / fsprojects/Paket

install and restore ignore --silent option

Open
#3,650 0 comments 0 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

The --silent option is ignored with the install or restore command.
Paket version 5.219.0

Repro steps

Please provide the steps required to reproduce the problem

paket.exe install --silent
paket.exe install -s
paket.exe restore -s
paket.exe restore --silent

Expected behavior

From the description:
--silent, -s suppress console output

I would expect no console output at all (maybe a banner).

Actual behavior

.paket\paket.exe restore --silent -f
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxxx\xxxxxxxxxx.wixproj
Unable to parse project xxxxxxxxxxxx.wixproj:
unable to find Project node in file C:_\xxxxxx\xxxxxx\xxxxxx\xxxxxxxxxx.wixproj
.
.
.
Starting restore process.
Downloading Agilent.RapidControlFormatter 1.0.9.0
Downloading Agilent.LCDrivers.MergedBusinessObjects.1.0 1.18.0.0
Downloading Language_pt-BR 44.0.5
Downloading ELSDCoreDriver 1.1.1.0
Downloading Agilent.InstrumentControl.Framework 2.0.13
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.rapidcontrolformatter\1.0.9\agilent.rapidcontrolformatter.1.0.9.nupkg' already exists (maybe some other instance downloaded it as well)
Not moving as 'C:\Users\onlinden.nuget\packages\elsdcoredriver\1.1.1\elsdcoredriver.1.1.1.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.RapidControlFormatter 1.0.9.0 done in 542 milliseconds. (99 kbit/s, 0 MB)
Download of ELSDCoreDriver 1.1.1.0 done in 541 milliseconds. (759 kbit/s, 0 MB)
Downloading FluentCommandLineParser 1.4.3
Downloading Agilent.RCDrivers.AutomatedUI.Dependencies 1.0.0.0
Not moving as 'C:\Users\onlinden.nuget\packages\language_pt-br\44.0.5\language_pt-br.44.0.5.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Language_pt-BR 44.0.5 done in 809 milliseconds. (16169 kbit/s, 1 MB)
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.lcdrivers.mergedbusinessobjects.1.0\1.18.0\agilent.lcdrivers.mergedbusinessobjects.1.0.1.18.0.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.LCDrivers.MergedBusinessObjects.1.0 1.18.0.0 done in 911 milliseconds. (55791 kbit/s, 6 MB)
Not moving as 'C:\Users\onlinden.nuget\packages\fluentcommandlineparser\1.4.3\fluentcommandlineparser.1.4.3.nupkg' already exists (maybe some other instance downloaded it as well)
Download of FluentCommandLineParser 1.4.3 done in 359 milliseconds. (2511 kbit/s, 0 MB)
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.instrumentcontrol.framework\2.0.13\agilent.instrumentcontrol.framework.2.0.13.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.InstrumentControl.Framework 2.0.13 done in 1 second. (5983 kbit/s, 0 MB)
Downloading Help_Chs 2.0.25
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.rcdrivers.automatedui.dependencies\1.0.0\agilent.rcdrivers.automatedui.dependencies.1.0.0.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.RCDrivers.AutomatedUI.Dependencies 1.0.0.0 done in 436 milliseconds. (23358 kbit/s, 1 MB)
Downloading Agilent.InstrumentControl.Package_1100_1200 4.0.2
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.instrumentcontrol.package_1100_1200\4.0.2\agilent.instrumentcontrol.package_1100_1200.4.0.2.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.InstrumentControl.Package_1100_1200 4.0.2 done in 45 milliseconds. (3887 kbit/s, 0 MB)
Downloading Language_ru-RU 44.0.5
Downloading Agilent.InstrumentControl.Package_1120 4.0.2
Not moving as 'C:\Users\onlinden.nuget\packages\agilent.instrumentcontrol.package_1120\4.0.2\agilent.instrumentcontrol.package_1120.4.0.2.nupkg' already exists (maybe some other instance downloaded it as well)
Download of Agilent.InstrumentControl.Package_1120 4.0.2 done in 64 milliseconds. (3018 kbit/s, 0 MB)
Downloading Agilent.SampleContainerLocationFormatter 1.1.3.0

Known workarounds

None.

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

Reproduce the issue with the listed paket.exe install and restore commands, including both --silent and -s. Trace the install and restore command entry points and their console-output paths; done means these commands suppress output as described while still completing the operation.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
cli, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.