pulsar-edit / pulsar-edit/ppm

Package install issue on linux( MX linux )

Open
#129 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
40
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Thanks in advance for your bug report!
  • Have you reproduced issue in safe mode?
  • Have you used the debugging guide to try to resolve the issue?
  • Have you checked our FAQs to make sure your question isn't answered there?
  • Have you checked to make sure your issue does not already exist?
  • Have you checked you are on the latest release of Pulsar?
What happened?

Packages don't install after install a few basic packages

Pulsar version

1.116

Which OS does this happen on?

🐧 Debian based (Linux Mint, Ubuntu, etc.)

OS details

Mx Linux 23.2

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?
  1. Install a package ex: atom-ide-hyperclick
  2. Get the error of cb() is never called
Additional Information:

The log:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/opt/Pulsar/resources/app/ppm/bin/node',
1 verbose cli '/opt/Pulsar/resources/app/ppm/node_modules/npm/bin/npm-cli.js',
1 verbose cli '--globalconfig',
1 verbose cli '/home/Ayush/.pulsar/.apm/.apmrc',
1 verbose cli '--userconfig',
1 verbose cli '/home/Ayush/.pulsar/.apmrc',
1 verbose cli 'install',
1 verbose cli 'https://api.pulsar-edit.dev/api/packages/atom-ide-hyperclick/versions/1.0.11/tarball',
1 verbose cli '--target=12.2.3',
1 verbose cli '--disturl=https://artifacts.electronjs.org/headers/dist',
1 verbose cli '--arch=x64',
1 verbose cli '--force-process-config',
1 verbose cli '--global-style',
1 verbose cli '--production'
1 verbose cli ]
2 info using npm@6.14.19-pulsar1-1
3 info using node@v16.0.0
4 verbose npm-session c9b901d4ddacc70d
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 http fetch GET 200 https://codeload.github.com/atom-community/atom-ide-hyperclick/legacy.tar.gz/refs/tags/v1.0.11 2938ms
8 silly pacote remote manifest for undefined@https://api.pulsar-edit.dev/api/packages/atom-ide-hyperclick/versions/1.0.11/tarball fetched in 2971ms
9 timing stage:loadCurrentTree Completed in 3014ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 0ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 1ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule atom-ide-hyperclick@1.0.11 checking installable status
17 http fetch GET 200 https://registry.npmjs.org/atom-ide-base 124ms (from cache)
18 http fetch GET 200 https://registry.npmjs.org/rxjs 131ms (from cache)
19 http fetch GET 200 https://registry.npmjs.org/react 169ms (from cache)
20 silly pacote range manifest for atom-ide-base@^3.0.0 fetched in 323ms
21 silly resolveWithNewModule atom-ide-base@3.3.0 checking installable status
22 http fetch GET 200 https://registry.npmjs.org/react-dom 353ms (from cache)
23 silly pacote range manifest for react@^17.0.2 fetched in 497ms
24 silly resolveWithNewModule react@17.0.2 checking installable status
25 silly pacote range manifest for react-dom@^17.0.2 fetched in 500ms
26 silly resolveWithNewModule react-dom@17.0.2 checking installable status
27 http fetch GET 200 https://registry.npmjs.org/prop-types 778ms
28 http fetch GET 200 https://registry.npmjs.org/prop-types/-/prop-types-15.8.1.tgz 232ms
29 silly pacote range manifest for prop-types@^15.7.2 fetched in 1081ms
30 silly resolveWithNewModule prop-types@15.8.1 checking installable status
31 timing npm Completed in 4915ms
32 error cb() never called!
33 error This is an error with npm itself. Please report this error at:
34 error https://npm.community

Contributor guide

Open the contributing guide

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 installing atom-ide-hyperclick 1.0.11 on MX Linux 23.2 using the logged Pulsar package-manager command, then trace the ppm/npm install path around npm 6.14.19-pulsar1-1 and Node 16.0.0. Done means the package installs successfully instead of ending with “cb() never called”; the payload names no source files or tests, so identify the relevant entry point and regression coverage while investigating.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.