pulsar icon indicating copy to clipboard operation
pulsar copied to clipboard

Updater and Package Manager broken

Open Shinrai opened this issue 1 year ago • 6 comments

Thanks in advance for your bug report!

  • [X] Have you reproduced issue in safe mode?
  • [X] Have you used the debugging guide to try to resolve the issue?
  • [X] Have you checked our FAQs to make sure your question isn't answered there?
  • [X] Have you checked to make sure your issue does not already exist?
  • [X] Have you checked you are on the latest release of Pulsar?

What happened?

`Fetching local packages failed.Hide output… P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\agent.js:114 class SocksProxyAgent extends agent_base_1.Agent { ^

TypeError: Class extends value undefined is not a constructor or null at Object. (P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\agent.js:114:44) at Module._compile (node:internal/modules/cjs/loader:1108:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10) at Module.load (node:internal/modules/cjs/loader:988:32) at Function.Module._load (node:internal/modules/cjs/loader:828:14) at Module.require (node:internal/modules/cjs/loader:1012:19) at require (node:internal/modules/cjs/helpers:93:18) at Object. (P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\index.js:5:33) at Module._compile (node:internal/modules/cjs/loader:1108:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)`

`Fetching outdated packages and themes failed.Hide output… P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\agent.js:114 class SocksProxyAgent extends agent_base_1.Agent { ^

TypeError: Class extends value undefined is not a constructor or null at Object. (P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\agent.js:114:44) at Module._compile (node:internal/modules/cjs/loader:1108:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10) at Module.load (node:internal/modules/cjs/loader:988:32) at Function.Module._load (node:internal/modules/cjs/loader:828:14) at Module.require (node:internal/modules/cjs/loader:1012:19) at require (node:internal/modules/cjs/helpers:93:18) at Object. (P:\Utilities\Pulsar Editor\resources\app\ppm\node_modules\socks-proxy-agent\dist\index.js:5:33) at Module._compile (node:internal/modules/cjs/loader:1108:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1137:10)`

Pulsar version

1.112.1

Which OS does this happen on?

🪟 Windows

OS details

11

Which CPU architecture are you running this on?

x86_64/AMD64

What steps are needed to reproduce this?

Update to 1.112.1 Launch Pulsar

Additional Information:

No response

Shinrai avatar Jan 06 '24 19:01 Shinrai

Not sure what the issue was but I started installing older versions. At one point decided to remove the old files and start a fresh install as the problem was constantly happening. After doing so v1.112.1 worked fine. So leaving the older version's files in place was the cause for this issue.

Shinrai avatar Jan 06 '24 19:01 Shinrai

I think we'll probably keep this issue open because, at very least, the logging should be more helpful here. Hopefully the stack trace is enough for us to piece together roughly what went wrong. Thanks for the report!

savetheclocktower avatar Jan 06 '24 20:01 savetheclocktower

I think we'll probably keep this issue open because, at very least, the logging should be more helpful here. Hopefully the stack trace is enough for us to piece together roughly what went wrong. Thanks for the report!

Yea that's why I didn't close the issue when reporting the fix.

Shinrai avatar Jan 06 '24 21:01 Shinrai

@Shinrai I'm curious about which older files you removed. Was it anything in your .pulsar folder? Or where there other files you kept around, I'm wondering if this was some proxy config that was attempting to be used that was either invalid, or otherwise something is broken in PPM's current proxy setup

confused-Techie avatar Jan 07 '24 23:01 confused-Techie

@Shinrai I'm curious about which older files you removed. Was it anything in your .pulsar folder? Or where there other files you kept around, I'm wondering if this was some proxy config that was attempting to be used that was either invalid, or otherwise something is broken in PPM's current proxy setup

I only removed the files inside the install directory. All my app data was left alone.

Shinrai avatar Jan 14 '24 08:01 Shinrai

So looking further into this issue, I was able to find the same error being reported on one of the dependencies used in ppm here.

Which this was only used in PPM after 1.112.0 when PPM switched from request to superagent. So I'm assuming this popped up due to some old files within PPM, possibly not having the right dependencies or something, it's hard to say.

confused-Techie avatar Feb 12 '24 22:02 confused-Techie