nushell / nushell/nupm

can't publish some packages

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Nushell
Stars
335
Forks
24
PR merge metrics
No merged PRs in 30d

Description

✔️ nu_plugin_explore@0.94.0

i was able to publish nu_plugin_explore@0.94.0 by running

nupm publish /path/to/nupm/registry/registry.nuon --save

after a git checkout 0.94.0 in the repo.

nu_plugin_clipboard@0.93.0

nu_plugin_clipboard@0.93.0 does not work because it's already published and targets 163bbb7, but it's not the correct revision...
it should be 1788d2c, is it possible to amend the registry? 🤔

not a huge deal because it's just a merge commit but still 😮

std-rfc

i wanted to try out to publish the standard library candidates and the std-rfc package but it gives an internal error

nupm publish /path/to/nupm/registry/registry.nuon
Error: nu::shell::access_beyond_end

  × Row number too large (empty content).
    ╭─[~/.local/share/nupm/modules/nupm/publish.nu:51:15]
 50 │         let res = search-package $pkg.name --registry $reg_path --exact-match
 51 │             | first # there will be only one result because we passed local path
    ·               ──┬──
    ·                 ╰── index too large (empty content)
 52 │             | get pkgs
    ╰────

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 by reproducing the three publishing cases with nupm publish and the referenced registry.nuon files. Read ~/.local/share/nupm/modules/nupm/publish.nu at line 51 and trace the search-package result for the std-rfc package. Done means the reported publish failures are handled clearly, including the already-published revision and the empty search result.

Written by the indexing model from the issue text.

Assessment

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