fsprojects / fsprojects/Paket

Paket crash when --no-install is specified on update with generate_include_scripts

Open
#2,785 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

Original report: https://github.com/fsharp/FAKE/issues/1672
But this reproduces with paket standalone as well...

This issue only reproduces when a clear state is used (ie packages, paket-files and paket.lock as well as .paket/load deleted):

paket.dependencies

source https://api.nuget.org/v3/index.json
generate_load_scripts: true
nuget Fake.Core.Targets prerelease

group External
    source https://api.nuget.org/v3/index.json

    nuget Google.Protobuf.Tools prerelease

.paket/paket.exe update --no-install --group Main

Paket failed with
-> Folder C:\proj\testing\packages\runtime.ubuntu.16.04-x64.runtime.native.System.Security.Cryptography.OpenSsl doesn't exist. Did you restore groups Main?
Expected behavior

Paket executes a restore even when --no-install is specified.

Actual behavior

Paket doesn't execute a restore and obviously fails when trying to generate load scripts.

Known workarounds

do a restore after the error.

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 from a clean state using paket.dependencies and .paket/paket.exe update --no-install --group Main, with the listed Main and External groups. Trace the update path that generates load scripts and verify that the command restores the required packages before generation, while preserving the intended --no-install behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
fsharp
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.