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] Error: write EPIPE #2902

Open
fxhart opened this issue Dec 8, 2024 · 1 comment
Open

[gui error report] Error: write EPIPE #2902

fxhart opened this issue Dec 8, 2024 · 1 comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization

Comments

@fxhart
Copy link

fxhart commented Dec 8, 2024

I wasn't doing anything. Laptop was next to me and the error popped up

  • Desktop: 0.40.0
  • OS: linux 6.11.0-061100-generic x64
  • Electron: 33.2.0
  • Chrome: 130.0.6723.118
Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:161:15)
    at writeGeneric (node:internal/stream_base_commons:152:3)
    at Socket._writeGeneric (node:net:954:11)
    at Socket._write (node:net:966:8)
    at writeOrBuffer (node:internal/streams/writable:570:12)
    at _write (node:internal/streams/writable:499:10)
    at Writable.write (node:internal/streams/writable:508:10)
    at Console.log (/tmp/.mount_ipfs_d7g08QH/resources/app.asar/node_modules/winston/lib/winston/transports/console.js:79:23)
    at Console._write (/tmp/.mount_ipfs_d7g08QH/resources/app.asar/node_modules/winston/node_modules/winston-transport/index.js:82:19)
    at doWrite (/tmp/.mount_ipfs_d7g08QH/resources/app.asar/node_modules/winston/node_modules/winston-transport/node_modules/readable-stream/lib/_stream_writable.js:409:139)
@fxhart fxhart added kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization labels Dec 8, 2024
Copy link

welcome bot commented Dec 8, 2024

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 are triaging issues on weekly basis and aim to give initial feedback within a few 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.tech if you just need general support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug A bug in existing code (including security flaws) need/triage Needs initial labeling and prioritization
Projects
None yet
Development

No branches or pull requests

1 participant