LivelyKernel / LivelyKernel/lively.next

Build failure on WSL Ubuntu but not on OS/X

Open
#1,762 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

:lady_beetle: bug
Dominant language
JavaScript
Stars
90
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
I've tried to freeze https://github.com/engageLively/galyleo-dashboard, and the freeze works on my Mac but repeatedly fails on WSL, with the error message:

TypeError: Could not load https://jspm.dev/immutable@4.0.0-rc.12: fetch failed
    at Object.fetch (node:internal/deps/undici/undici:11457:11)
    at async WebDAVResource.read (file:///home/rick/lively.next/lively.resources/src/http-resource.js:232:17)
    at async fetchFile (/home/rick/lively.next/lively.freezer/src/resolvers/node.cjs:150:14)
    at async Object.load (/home/rick/lively.next/lively.freezer/src/resolvers/node.cjs:165:11)
    at async LivelyRollup.load (file:///home/rick/lively.next/lively.freezer/src/bundler.js:581:13)
    at async file:///home/rick/lively.next/lively.next-node_modules/rollup/2.70.2/dist/es/shared/rollup.js:22093:83
    at async Queue.work (file:///home/rick/lively.next/lively.next-node_modules/rollup/2.70.2/dist/es/shared/rollup.js:21677:32) {
  cause: SocketError: other side closed
      at TLSSocket.onSocketEnd (node:internal/deps/undici/undici:9689:26)
      at TLSSocket.emit (node:events:525:35)
      at endReadableNT (node:internal/streams/readable:1359:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '172.19.148.218',
      localPort: 34326,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 190,
      bytesRead: 0
    }
  },
  code: 'PLUGIN_ERROR',
  plugin: 'commonjs--resolver',
  hook: 'resolveId',

It was working fine until yesterday, but something is wrong today. I tried rebooting just in case it was system load. Same version of Lively

To Reproduce

  1. Pull https://github.com/engageLively/galyleo-dashboard
  2. On WSL, in the root directory, run npm build

Screenshots
If applicable, add screenshots to help explain your problem.

Setup
Please delete non-applicable items!

  • Windows
  • Linux

Version: Please paste the lively.next commit on which the problem occurred here (use the copy button of the Version Checker in the bottom left corner).
c725a776b26bd744331765a4881ba4c0557d2fea

Contributor guide

Open the contributing guide

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

Start by reproducing npm build in the galyleo-dashboard root on WSL Ubuntu and compare it with the working macOS setup. Read lively.resources/src/http-resource.js, lively.freezer/src/resolvers/node.cjs, and lively.freezer/src/bundler.js around the reported stack frames. Done means the freeze completes successfully on WSL for the reported commit, with the failure cause identified and covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, linux, nodejs, rollup
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.