Elliott
04/11/2023, 7:33 AMColin - Krumware
04/11/2023, 2:34 PMStep 15/41 : RUN npx turbo prune --scope=@calcom/web --docker
---> Running in bd3e7e15b3f2
npm WARN exec The following package was not found and will be installed: turbo@1.8.8
Generating pruned monorepo for @calcom/web in /calcom/out
- Added @calcom/app-store
- Added @calcom/app-store-cli
- Added @calcom/config
- Added @calcom/core
- Added @calcom/dailyvideo
- Added @calcom/dayjs
- Added @calcom/embed-core
- Added @calcom/embed-react
- Added @calcom/embed-snippet
- Added @calcom/eslint-plugin-eslint
- Added @calcom/features
- Added @calcom/lib
- Added @calcom/office365video
- Added @calcom/prisma
- Added @calcom/trpc
- Added @calcom/tsconfig
- Added @calcom/types
- Added @calcom/ui
- Added @calcom/web
- Added @calcom/zoomvideo
ERROR Failed to encode pruned lockfile: Unable to find entry for tailwindcss@npm:3.3.1
Turbo error: Failed to encode pruned lockfile: Unable to find entry for tailwindcss@npm:3.3.1
Colin - Krumware
04/11/2023, 9:21 PMGenius Khalipha
04/12/2023, 9:55 PMGenius Khalipha
04/12/2023, 9:55 PMGenius Khalipha
04/12/2023, 9:55 PMzomars
04/13/2023, 6:54 PMSascha Foerster
04/15/2023, 11:37 PMBlaine J
04/16/2023, 3:16 AMkhatri Hitesh
04/25/2023, 6:17 PMreadmen.md
local deveContainer
for the development environment got setup without any apparent issues.
However, when I am trying to run yarn dx
.. it gives me following error.
Error: Database is uninitialized and superuser password is not specified.
You must specify POSTGRES_PASSWORD to a non-empty value for the
superuser. For example, "-e POSTGRES_PASSWORD=password" on "docker run".
You may also use "POSTGRES_HOST_AUTH_METHOD=trust" to allow all
connections without a password. This is *not* recommended.
See PostgreSQL documentation about "trust":
<https://www.postgresql.org/docs/current/auth-trust.html>
my docker is running and I can see that it has spun up postgres database docker image.. image is not running successfully!
has anyone faced with this issue? any help would be appreciated.
Posted in #generalkhatri Hitesh
04/25/2023, 6:17 PMSreehari S
05/01/2023, 5:01 PMAnand Christudas
05/02/2023, 1:36 PMColin - Krumware
05/03/2023, 3:04 PMAbtin Gramian
05/04/2023, 1:46 AMGitHub
05/04/2023, 6:38 AMElliott
05/04/2023, 1:00 PMColin - Krumware
05/04/2023, 1:23 PMImeth Gunawardena
05/17/2023, 8:26 AMBlaine J
05/21/2023, 2:03 PMBlaine J
05/24/2023, 10:34 AMAlex
05/27/2023, 3:12 PMWesley Matos
06/12/2023, 4:22 PMBlaine J
06/14/2023, 10:38 PMBlaine J
06/14/2023, 10:38 PMPeer
Colin - Krumware
06/28/2023, 9:11 PMSergei Reutov
06/30/2023, 8:40 AMDOCKER_BUILDKIT=0 docker compose build calcom
returns this error:
➤ YN0013: │ @aws-sdk/middleware-endpoint@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/middleware-host-header@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/is-array-buffer@npm:3.201.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/middleware-content-length@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/middleware-endpoint@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/middleware-host-header@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
➤ YN0013: │ @aws-sdk/middleware-logger@npm:3.272.0 can't be found in the cache and will be fetched from the remote registry
Usage Error: Couldn't find the node_modules state file - running an install might help (findPackageLocation)
$ yarn run [--inspect] [--inspect-brk] [-T,--top-level] [-B,--binaries-only] <scriptName> ...
The command '/bin/sh -c yarn config set httpTimeout 1200000 && npx turbo prune --scope=@calcom/web --docker && yarn install && yarn db-deploy && yarn --cwd packages/prisma seed-app-store' returned a non-zero code: 1
I’ve tried running yarn install
in the root folder and in the ./calcom
folder - same result.
I’m on Mac (Ventura 13.4.1), using Node v18.16.1, Docker v.4.19.0
Any idea how to fix it?Sergei Reutov
07/07/2023, 11:05 AMColin - Krumware
07/11/2023, 12:55 PM