PoE-Overlay-Community / PoE-Overlay-Community-Fork

An Overlay for Path of Exile. Built with Angular.
MIT License
460 stars 85 forks source link

Node js errors when running on Linux x64 #343

Open HarrySpyrou opened 9 months ago

HarrySpyrou commented 9 months ago

🐞 bug report

Describe the bug Unfortunately I can't understand what the issue is exactly. However, from a user perspective, the overlay is not there. I can open the settings, log into my account and select Leagues etc, but the main Overlay doesn't work and also the shortcuts don't work. I was running it in the terminal so I can see these logs

08:36:59.781 › Error: Error: Cannot find latest-linux.yml in the latest release artifacts (https://github.com/PoE-Overlay-Community/PoE-Overlay-Community-Fork/releases/download/v0.8.27/latest-linux.yml): HttpError: 404 
"method: GET url: https://github.com/PoE-Overlay-Community/PoE-Overlay-Community-Fork/releases/download/v0.8.27/latest-linux.yml\n\nPlease double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n"
Headers: {
  "status": "404",
  "server": "GitHub.com",
  "date": "Sat, 02 Dec 2023 08:36:59 GMT",
  "content-type": "text/plain; charset=utf-8",
  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With",
  "cache-control": "no-cache",
  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",
  "x-frame-options": "deny",
  "x-content-type-options": "nosniff",
  "x-xss-protection": "0",
  "referrer-policy": "no-referrer-when-downgrade",
  "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",
  "content-encoding": "gzip",
  "content-length": "29",
  "x-github-request-id": "B910:FC10:39E4990D:3AAF553C:656AECAB"
}
    at createHttpError (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:84:10)
    at ElectronHttpExecutor.handleResponse (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:169:14)
    at ClientRequest.<anonymous> (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:134:16)
    at ClientRequest.emit (events.js:210:5)
    at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:2559:12)
    at SimpleURLLoaderWrapper.emit (events.js:210:5)
    at newError (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/index.js:212:17)
    at GitHubProvider.getLatestVersion (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/electron-updater/out/providers/GitHubProvider.js:135:50)
08:36:59.782 › (node:105348) UnhandledPromiseRejectionWarning: Error: Cannot find latest-linux.yml in the latest release artifacts (https://github.com/PoE-Overlay-Community/PoE-Overlay-Community-Fork/releases/download/v0.8.27/latest-linux.yml): HttpError: 404 
"method: GET url: https://github.com/PoE-Overlay-Community/PoE-Overlay-Community-Fork/releases/download/v0.8.27/latest-linux.yml\n\nPlease double check that your authentication token is correct. Due to security reasons actual status maybe not reported, but 404.\n"
Headers: {
  "status": "404",
  "server": "GitHub.com",
  "date": "Sat, 02 Dec 2023 08:36:59 GMT",
  "content-type": "text/plain; charset=utf-8",
  "vary": "X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With",
  "cache-control": "no-cache",
  "strict-transport-security": "max-age=31536000; includeSubdomains; preload",
  "x-frame-options": "deny",
  "x-content-type-options": "nosniff",
  "x-xss-protection": "0",
  "referrer-policy": "no-referrer-when-downgrade",
  "content-security-policy": "default-src 'none'; base-uri 'self'; connect-src 'self'; form-action 'self'; img-src 'self' data:; script-src 'self'; style-src 'unsafe-inline'",
  "content-encoding": "gzip",
  "content-length": "29",
  "x-github-request-id": "B910:FC10:39E4990D:3AAF553C:656AECAB"
}
    at createHttpError (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:84:10)
    at ElectronHttpExecutor.handleResponse (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:169:14)
    at ClientRequest.<anonymous> (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/httpExecutor.js:134:16)
    at ClientRequest.emit (events.js:210:5)
    at SimpleURLLoaderWrapper.<anonymous> (electron/js2c/browser_init.js:2559:12)
    at SimpleURLLoaderWrapper.emit (events.js:210:5)
    at newError (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/builder-util-runtime/out/index.js:212:17)
    at GitHubProvider.getLatestVersion (/tmp/.mount_poe-ovM3xoE1/resources/app.asar/node_modules/electron-updater/out/providers/GitHubProvider.js:135:50)
08:36:59.782 › (node:105348) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)

To Reproduce

Steps to reproduce the behavior:

  1. Use makefile:
    
    APPLICATION_NAME ?= poe-overlay

build: sudo docker build -o release --tag ${DOCKER_USERNAME}/${APPLICATION_NAME} .


2. after appimage is made, run in terminal. Observe nodejs errors
3. Open Path of Exile, set up PoE Overlay, observe that the overlay doesn't work, but the settings do
4. Check terminal, more node js errors as you start cliking around.
5. Try shortcut keys, observe they don't work.

**Expected behavior**
Show and be able to use the Overlay and the shortcuts.

## 🌍  Your Environment

- OS: [Nobara 38 Kde version](https://nobaraproject.org/download-nobara/) aka Fedora
- PoE: e.g. Steam 3.22.0 English
WhiteFang5 commented 9 months ago

This is probably happening because the latest release does not include a linux build. It's not included because of a number of issues related to linux builds that are still pending to be solved in a different PR.