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

Bun install hangs on Resolving (Waiting for 20 tasks) #10698

Open
KtheVeg opened this issue Apr 30, 2024 · 4 comments
Open

Bun install hangs on Resolving (Waiting for 20 tasks) #10698

KtheVeg opened this issue Apr 30, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@KtheVeg
Copy link

KtheVeg commented Apr 30, 2024

What version of Bun is running?

1.1.6+e58d67b46

What platform is your computer?

Linux 6.5.0-28-generic x86_64 x86_64

What steps can reproduce the bug?

Installed Bun (downloaded the script then ran separately).

  1. Created a project with bun init
  2. Ran bun i cheerio

What is the expected behavior?

Expected Resolving step to last less than a minute.

What do you see instead?

When run with --verbose, the line Waiting for 20 tasks gets printed repeatedly.

Additional information

Attempted fixes:

  1. Rebooting
  2. Updating Bun (both to Canary and Stable)
  3. Disabling IPv6 (Modified NM config for my network to disable IPv6 for this network)
@KtheVeg KtheVeg added the bug Something isn't working label Apr 30, 2024
@gvilums
Copy link
Contributor

gvilums commented May 1, 2024

Hm, unfortunately I'm unable to reproduce this. Are there any additional details about your environment that you could share?

@mgurg
Copy link

mgurg commented May 2, 2024

I have similar problem (# [PackageManager] waiting for) using Docker, Bun 1.1.6

files:
compose.prod.yml:

services:
  quasar-staging:
    build:
      context: .
      dockerfile: Dockerfile
      target: "production-stage"
    container_name: escape-room-ccui-staging
    ports:
      - "8080:8080"
      - "9000:9000"
    volumes:
      - ".:/app"

Dockerfile:

# build stage
FROM oven/bun:1.1 as develop-stage

# create work direction
RUN mkdir -p /usr/src/web

WORKDIR /usr/src/web

COPY . .

# build stage
FROM develop-stage as build-stage
RUN bun install --verbose
RUN bun install --verbose -g @quasar/cli

RUN bun run quasar build

# production stage
FROM nginx:1.25-alpine-slim as production-stage

COPY --from=build-stage /usr/src/web/dist/spa /usr/share/nginx/html
COPY --from=build-stage /usr/src/web/nginx/conf.d/default.conf /etc/nginx/conf.d/default.conf

EXPOSE 80

# start
CMD ["nginx", "-g", "daemon off;"]

package.json

{
  "name": "frontend",
  "version": "0.0.1",
  "description": "EscapeRoomUI CC",
  "productName": "EscaperRomCC",
  "author": "mgur <mgur@pop-os.localdomain>",
  "type": "module",
  "private": true,
  "scripts": {
    "lint": "eslint --ext .js,.vue ./",
    "format": "prettier --write \"**/*.{js,vue,scss,html,md,json}\" --ignore-path .gitignore",
    "test": "echo \"No test specified\" && exit 0",
    "dev": "quasar dev",
    "build": "quasar build"
  },
  "dependencies": {
    "@chenfengyuan/vue-countdown": "^2.1.2",
    "@quasar/extras": "^1.16.9",
    "@sentry/tracing": "^7.106.0",
    "@sentry/vue": "^7.106.0",
    "@vueuse/core": "^10.5.0",
    "axios": "^1.6.1",
    "howler": "^2.2.4",
    "luxon": "^3.4.3",
    "pinia": "^2.1.7",
    "quasar": "^2.14.0",
    "uuid": "^9.0.1",
    "vue": "^3.4.0",
    "vue-i18n": "^9.10.0",
    "vue-router": "^4.2.0"
  },
  "devDependencies": {
    "@intlify/unplugin-vue-i18n": "^2.0.0",
    "@quasar/app-vite": "^2.0.0-beta.11",
    "@sentry/vite-plugin": "^2.14.3",
    "autoprefixer": "^10.4.2",
    "eslint": "^8.11.0",
    "eslint-config-prettier": "^9.0.0",
    "eslint-plugin-vue": "^9.0.0",
    "postcss": "^8.4.14",
    "prettier": "^3.0.3",
    "vite-plugin-checker": "^0.6.4"
  },
  "engines": {
    "node": "^24 || ^22 || ^20 || ^18",
    "npm": ">= 6.13.4",
    "yarn": ">= 1.21.1"
  }
}

Run command: docker compose -f compose.prod.yml build

image

@progranadegrinder
Copy link

I was having the same exact problem on my Ubuntu server machine. Disabling IPv6 fixed the issue.

@KtheVeg
Copy link
Author

KtheVeg commented May 15, 2024

I was having the same exact problem on my Ubuntu server machine. Disabling IPv6 fixed the issue.

Unfortunately, disabling IPv6 didn't help at all, as mentionned in the third point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants