Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[gui error report] SyntaxError: Unexpected end of JSON input: Error: open C:\Users\mengs\Do #2353

Closed
ShuyueMeng opened this issue Dec 2, 2022 · 4 comments
Labels
area/windows Windows exp/intermediate Prior experience is likely helpful kind/bug A bug in existing code (including security flaws) kind/stale need/author-input Needs input from the original author topic/windows Windows specific

Comments

@ShuyueMeng
Copy link

👉️ Please describe what you were doing when this error happened.

Specifications

  • OS: win32 6.2.9200
  • IPFS Desktop Version: 0.24.1
  • Electron Version: 19.0.9
  • Chrome Version: 102.0.5005.167

Error

SyntaxError: Unexpected end of JSON input: Error: open C:\Users\mengs\Downloads\kubo_v0.17.0_windows-amd64\kubo\ipfs.exe\config: The system cannot find the path specified.
    at JSON.parse (<anonymous>)
    at Daemon._getConfig (D:\IPFS\IPFS Desktop\resources\app.asar\node_modules\ipfsd-ctl\src\ipfsd-daemon.js:368:21)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Daemon.init (D:\IPFS\IPFS Desktop\resources\app.asar\node_modules\ipfsd-ctl\src\ipfsd-daemon.js:158:9)
    at async getIpfsd (D:\IPFS\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:63:7)
    at async startDaemon (D:\IPFS\IPFS Desktop\resources\app.asar\src\daemon\daemon.js:210:17)
    at async startIpfs (D:\IPFS\IPFS Desktop\resources\app.asar\src\daemon\index.js:48:17)
    at async setupDaemon (D:\IPFS\IPFS Desktop\resources\app.asar\src\daemon\index.js:116:3)
    at async run (D:\IPFS\IPFS Desktop\resources\app.asar\src\index.js:85:5)
@ShuyueMeng ShuyueMeng added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Dec 2, 2022
@welcome
Copy link

welcome bot commented Dec 2, 2022

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@SgtPooki SgtPooki moved this to Needs Grooming in IPFS-GUI (PL EngRes) Dec 2, 2022
@whizzzkid
Copy link
Contributor

@ShuyueMeng This error indicates that you don't have an ipfs config file at C:\Users\mengs\Downloads\kubo_v0.17.0_windows-amd64\kubo\ipfs.exe\config. Can you please respond with the following information so we can investigate further?

  1. The path looks wrong (.exe files are not directories) have you successfully used IPFS desktop previously? (i.e. is this an issue with ipfs config not being created correctly? see https://github.com/ipfs/ipfs-desktop#how-does-ipfs-desktop-select-the-ipfs-repo-location)
  2. Can you attach your error.log, combined.log, and ipfs config files? https://github.com/ipfs/ipfs-desktop#where-are-my-ipfs-configuration-and-log-files
  3. Can you share more details about what you were doing when this error happened?

Thanks!

@whizzzkid whizzzkid added exp/intermediate Prior experience is likely helpful area/windows Windows need/author-input Needs input from the original author topic/windows Windows specific and removed need/triage Needs initial labeling and prioritization labels Dec 5, 2022
@github-actions
Copy link
Contributor

Oops, seems like we needed more information for this issue, please comment with more details or this issue will be closed in 7 days.

@github-actions
Copy link
Contributor

This issue was closed because it is missing author input.

Repository owner moved this from Needs Grooming to Done in IPFS-GUI (PL EngRes) Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/windows Windows exp/intermediate Prior experience is likely helpful kind/bug A bug in existing code (including security flaws) kind/stale need/author-input Needs input from the original author topic/windows Windows specific
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants