livepeer / livepeer/LivepeerDesktop

Does this work on Windows 10?

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

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
16
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Hi, I'm very intrigued by the concept of Livepeer (I was actually thinking of a combination between blockchain incentives in combination with a decentralized video platform, hence I started googling).

I wanted to try the desktop Client on Windows 10, but once I startup the application I get the following error. It does show a GUI, but it keeps hanging at "Starting Livepeer Node", with a few CPU hungy processes running in the background.

[Window Title]
Error

[Main Instruction]
A JavaScript error occurred in the main process

[Content]
Uncaught Exception:
Error: spawn C:\Users\<USERNAME>\LivepeerDesktop\node_modules/livepeer-static/bin\win32\x64\livepeer.exe ENOENT
    at exports._errnoException (util.js:1050:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
    at onErrorNT (internal/child_process.js:367:16)
    at _combinedTickCallback (internal/process/next_tick.js:80:11)
    at process._tickCallback (internal/process/next_tick.js:104:9)

[OK]

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

Reproduce the Windows 10 startup failure and inspect the desktop application's main process around the launch of node_modules/livepeer-static/bin/win32/x64/livepeer.exe. Verify whether the packaged executable exists at that path and confirm that a successful launch reaches the Livepeer node without the ENOENT error or hanging.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.