GitHub提交文件报错 Commit failed - exit code 1 received

最新推荐文章于 2025-10-22 09:00:00 发布
原创 最新推荐文章于 2025-10-22 09:00:00 发布 · 6.3k 阅读 · 1 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
文章标签：

#git

本文介绍了一种在使用Git上传文件夹到仓库时遇到的常见错误及其解决方案。通过简单的步骤，如打开本地仓库，使用快捷键shift+command+。(适用于Mac系统)，然后删除隐藏的.git文件夹，可以有效解决这一问题。

使用Git将一个文件夹上传仓库时出现题述错误。

打开本地仓库，快捷键shift + commond + . ps:我是mac系统
打开隐藏文件夹，删除.git文件夹即可

这里写图片描述

本地项目托管到Github&Gitee且同时关联两个Git远程项目(实现拉/推/整合/代码解决冲突) 教程
杰孑的博客
12-18 3354
Git的使用-如何将本地项目托管到Github上面？(三种简单的方法详解)：https://www.cnblogs.com/du-hong/p/9921214.html Git的使用-如何将本地项目托管到码云Gitee上面? 简单图文详解教程：https://www.sohu.com/a/319744556_418879 ...
triton inference server入门1
stephen147的博客
08-12 786
肯定很多人想知道triton干啥的，学习这个有啥用？triton可以充当服务框架去部署你的深度学习模型，其他用户可以通过http或者grpc去请求，相当于你用flask搭了个服务供别人请求，当然相比flask的性能高很多了triton也可以摘出C-API充当多线程推理服务框架，去除http和grpc部分，适合本地部署多模型，比如你有很多模型要部署，然后分时段调用，或者有pipeline，有了triton就省去你处理显存、内存和线程的麻烦注意，还有一个同名的triton。
【Git】解决Commit failed - exit code 1 received
midnight_time的博客
01-02 2833
使用Github桌面版出现了：Commit failed - exit code 1 received 总的来说都是因为当前Github桌面版打开的目录不对。 大致有以下两种情况 当前目录下没有.git文件夹，.git在上层目录 不仅当前目录存在.git文件夹，而且下层目录也存在.git文件夹 如果是第一种，找准.git所在目录，重新打开即可。 如果是第二种，要自己选择删除一个.git，...
GitHub Desktop 提交代码时出现：Commit failed - exit code 1 received 的解决办法
Iversons.Tian的博客
04-27 1262
博主提交的是用React写的前端代码，解决办法中： 找到项目中的 package.json文件，删除其中这行代码： 再次重新提交即可。
Commit failed with error(一文搞懂原因并解决)
风也温柔☆的博客
10-22 330
本文分析了Git提交失败的两个常见错误及其解决方法。错误1是由于lint-staged配置中包含了git add命令，需要移除package.json中的git add配置。错误2是husky的pre-commit钩子检查失败，可通过添加--no-verify参数跳过检查。解决方法包括修改lint-staged配置、添加--no-verify参数提交命令，以及如何在SourceTree中跳过钩子检查。通过调整配置和添加参数，可以解决Git提交失败的问题。
Git Commit failed - exit code 1 received
Lesley_驰骋沙场
10-09 8370
使用Git将一个文件夹上传仓库时出现题述错误。原因是我曾在这个文件夹上建过仓库，网页上仓库删除却没有删除本地的配置文件。如图，将该文件夹下的隐藏文件可见view ->hidden item(我的是英文系统，中文请对应寻找)删除.git文件夹即可
Commit failed - exit code 1 received
Kp0fS的草稿纸
07-20 261
如何解決這個問題？ 先去submodel里边， $ cd themes/next $ git add . $ git commit -m "update" $ git push origin master 然后在 git push
已解决：Commit failed - exit code 1 received, with output: ‘＞ running pre-commit hook: npm run precommit
谨言不言☞博客
11-14 2448
Commit failed - exit code 1 received, with output: '> running pre-commit hook: npm run precommit ###￥ 解决方案： 直接把pre-commit文件删除，进入项目.git文件夹——hooks——删除，然后，再次提交代码就ok啦。 借鉴地址：https://blog.youkuaiyun.com/m18633778874/article/details/87448059?ops_request_misc=%257B%2
curl -o .git/hooks/commit-msg https://gerrit-ce.tp-link.com/tools/hooks/commit-msg % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated. geri@geri-virtual-machine:~/share/code/github/NVMP/nvmp$ chmod +x .git/hooks/commit-msg chmod: 无法访问'.git/hooks/commit-msg': 没有那个文件或目录
10-12
- 因此 `.git/hooks/commit-msg` 文件并不存在，导致 `chmod` 报错 --- ### 问题原因分析 #### ❌ `curl` 失败的可能原因： 1. **网络策略限制**：你的环境（如虚拟机、公司内网）可能拦截了 HTTPS 请求。 2. **...
gapinyc@DESKTOP-9QS7RL5:~/superset-prod$ export DOCKER_BUILDKIT=1 docker build \ -f Dockerfile.superset \ --build-arg SUPERSET_VERSION=5.0.0 \ -t my-superset:5.0.0 \ . [+] Building 704.8s (11/17) docker:default => [internal] load build definition from Dockerfile.superset 0.0s => => transferring dockerfile: 2.62kB 0.0s => [internal] load metadata for docker.io/apache/superset:5.0.0 0.2s => [internal] load metadata for docker.io/library/node:18-bullseye-slim 1.1s => [internal] load .dockerignore 0.0s => => transferring context: 2B 0.0s => [source-downloader 1/5] FROM docker.io/library/node:18-bullseye-slim@sha256:d69fb189fa7765636655db043a6a9e6be5ddf94bd1a8dc33fd0bcf4664606a9e 21.1s => => resolve docker.io/library/node:18-bullseye-slim@sha256:d69fb189fa7765636655db043a6a9e6be5ddf94bd1a8dc33fd0bcf4664606a9e 0.0s => => sha256:42f42eafefa50f1f31a15009c5f7c860e50d64699a39e925032b52bf183b6ecd 446B / 446B 0.1s => => sha256:8a49ca04d9f25692385798d2f44622aa58023f3d74b4824e5b4838c95ae44fec 1.74MB / 1.74MB 0.6s => => sha256:3e45f78336892645521624a2eb06cffe415248440cb1154db9467017f359995c 38.27MB / 38.27MB 17.6s => => sha256:56e571f2ee22b5620bc735735848b8efe0c5f4feacae2584d6ab711789e7fe0c 4.07kB / 4.07kB 0.2s => => sha256:e1f16b66c2e86ad38458eba597e4ec79e4750398a28dbbc2d7819d829c4c9023 30.26MB / 30.26MB 19.4s => => extracting sha256:e1f16b66c2e86ad38458eba597e4ec79e4750398a28dbbc2d7819d829c4c9023 0.7s => => extracting sha256:56e571f2ee22b5620bc735735848b8efe0c5f4feacae2584d6ab711789e7fe0c 0.0s => => extracting sha256:3e45f78336892645521624a2eb06cffe415248440cb1154db9467017f359995c 0.7s => => extracting sha256:8a49ca04d9f25692385798d2f44622aa58023f3d74b4824e5b4838c95ae44fec 0.0s => => extracting sha256:42f42eafefa50f1f31a15009c5f7c860e50d64699a39e925032b52bf183b6ecd 0.0s => CACHED [stage-2 1/3] FROM docker.io/apache/superset:5.0.0@sha256:09735adaae3945c5a8fabbeca31a7954c8c74de195702ba61622aee8604d5c55 0.1s => => resolve docker.io/apache/superset:5.0.0@sha256:09735adaae3945c5a8fabbeca31a7954c8c74de195702ba61622aee8604d5c55 0.0s => [source-downloader 2/5] RUN apt-get update && apt-get install -y git curl && rm -rf /var/lib/apt/lists/* 201.4s => [frontend-builder 2/6] RUN npm config set registry https://registry.npmmirror.com && npm config set cache /tmp/npm-cache && mkdir -p /tmp/npm-cache 2.0s => [frontend-builder 3/6] WORKDIR /app/superset-frontend 0.0s => [source-downloader 3/5] WORKDIR /tmp/superset-src 0.0s => ERROR [source-downloader 4/5] RUN git clone https://github.com/apache/superset.git . && git checkout "rel/5.0.0" 481.1s ------ > [source-downloader 4/5] RUN git clone https://github.com/apache/superset.git . && git checkout "rel/5.0.0": 0.200 Cloning into '.'... 481.1 error: RPC failed; curl 56 GnuTLS recv error (-9): Error decoding the received TLS packet. 481.1 error: 754 bytes of body are still expected 481.1 fetch-pack: unexpected disconnect while reading sideband packet 481.1 fatal: early EOF 481.1 fatal: index-pack failed ------ Dockerfile.superset:21 -------------------- 20 | # 克隆 Apache Superset 源码并切换到指定版本 21 | >>> RUN git clone ${GITHUB_MIRROR}/apache/superset.git . && \ 22 | >>> git checkout "rel/${SUPERSET_VERSION}" 23 | -------------------- ERROR: failed to build: failed to solve: process "/bin/sh -c git clone ${GITHUB_MIRROR}/apache/superset.git . && git checkout \"rel/${SUPERSET_VERSION}\"" did not complete successfully: exit code: 128 gapinyc@DESKTOP-9QS7RL5:~/superset-prod$
10-23
exit 1; \ fi; \ echo " Resolved latest version: $REAL_VERSION"; \ else \ REAL_VERSION=${SUPERSET_VERSION}; \ fi; \ \ # 构造下载 URL（优先使用国内镜像） DOWNLOAD_URL="${GITHUB_ARCHIVE_MIRROR}/...
我用docker-compose启动firecrawl的时候出现报错： Attaching to api-1, nuq-postgres-1, playwright-service-1, redis-1 redis-1 | Starting Redis Server redis-1 | 1:C 15 Dec 2025 11:00:54.582 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. redis-1 | 1:C 15 Dec 2025 11:00:54.583 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis-1 | 1:C 15 Dec 2025 11:00:54.583 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=1, just started redis-1 | 1:C 15 Dec 2025 11:00:54.583 * Configuration loaded redis-1 | 1:M 15 Dec 2025 11:00:54.585 * monotonic clock: POSIX clock_gettime redis-1 | 1:M 15 Dec 2025 11:00:54.591 * Running mode=standalone, port=6379. redis-1 | 1:M 15 Dec 2025 11:00:54.594 * <bf> RedisBloom version 8.4.0 (Git=unknown) redis-1 | 1:M 15 Dec 2025 11:00:54.594 * <bf> Registering configuration options: [ redis-1 | 1:M 15 Dec 2025 11:00:54.594 * <bf> { bf-error-rate : 0.01 } redis-1 | 1:M 15 Dec 2025 11:00:54.594 * <bf> { bf-initial-size : 100 } redis-1 | 1:M 15 Dec 2025 11:00:54.594 * <bf> { bf-expansion-factor : 2 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> { cf-bucket-size : 2 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> { cf-initial-size : 1024 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> { cf-max-iterations : 20 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> { cf-expansion-factor : 1 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> { cf-max-expansions : 32 } redis-1 | 1:M 15 Dec 2025 11:00:54.595 * <bf> ] redis-1 | 1:M 15 Dec 2025 11:00:54.596 * Module 'bf' loaded from /usr/local/lib/redis/modules//redisbloom.so redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> Redis version found by RedisSearch : 8.4.0 - oss redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> RediSearch version 8.4.2 (Git=9e2b676) redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> Low level api version 1 initialized successfully redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> gc: ON, prefix min length: 2, min word length to stem: 4, prefix max expansions: 200, query timeout (ms): 500, timeout policy: return, oom policy: return, cursor read size: 1000, cursor max idle (ms): 300000, max doctable size: 1000000, max number of search results: 1000000, default scorer: BM25STD, redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> Initialized thread pools! redis-1 | 1:M 15 Dec 2025 11:00:54.614 * <search> Disabled workers threadpool of size 0 redis-1 | 1:M 15 Dec 2025 11:00:54.615 * <search> Subscribe to config changes redis-1 | 1:M 15 Dec 2025 11:00:54.615 * <search> Subscribe to cluster slot migration events redis-1 | 1:M 15 Dec 2025 11:00:54.615 * <search> Enabled role change notification redis-1 | 1:M 15 Dec 2025 11:00:54.616 * <search> Cluster configuration: AUTO partitions, type: 0, coordinator timeout: 0ms redis-1 | 1:M 15 Dec 2025 11:00:54.617 * <search> Register write commands redis-1 | 1:M 15 Dec 2025 11:00:54.618 * Module 'search' loaded from /usr/local/lib/redis/modules//redisearch.so redis-1 | 1:M 15 Dec 2025 11:00:54.619 * <timeseries> RedisTimeSeries version 80400, git_sha=3520a1568ad69076d60885c70711fbdc9b448749 redis-1 | 1:M 15 Dec 2025 11:00:54.620 * <timeseries> Redis version found by RedisTimeSeries : 8.4.0 - oss redis-1 | 1:M 15 Dec 2025 11:00:54.620 * <timeseries> Registering configuration options: [ redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-compaction-policy : } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-num-threads : 3 } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-retention-policy : 0 } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-duplicate-policy : block } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-chunk-size-bytes : 4096 } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-encoding : compressed } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-ignore-max-time-diff: 0 } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> { ts-ignore-max-val-diff : 0.000000 } redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> ] redis-1 | 1:M 15 Dec 2025 11:00:54.621 * <timeseries> Detected redis oss redis-1 | 1:M 15 Dec 2025 11:00:54.623 * <timeseries> Subscribe to ASM events redis-1 | 1:M 15 Dec 2025 11:00:54.623 * <timeseries> Enabled diskless replication redis-1 | 1:M 15 Dec 2025 11:00:54.623 * Module 'timeseries' loaded from /usr/local/lib/redis/modules//redistimeseries.so redis-1 | 1:M 15 Dec 2025 11:00:54.628 * <ReJSON> Created new data type 'ReJSON-RL' redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> version: 80400 git sha: unknown branch: unknown redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V1 API redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V2 API redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V3 API redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V4 API redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V5 API nuq-postgres-1 | The files belonging to this database system will be owned by user "postgres". redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Exported RedisJSON_V6 API nuq-postgres-1 | This user must also own the server process. redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Enabled diskless replication nuq-postgres-1 | redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <ReJSON> Initialized shared string cache, thread safe: true. nuq-postgres-1 | The database cluster will be initialized with locale "en_US.utf8". redis-1 | 1:M 15 Dec 2025 11:00:54.629 * Module 'ReJSON' loaded from /usr/local/lib/redis/modules//rejson.so nuq-postgres-1 | The default database encoding has accordingly been set to "UTF8". redis-1 | 1:M 15 Dec 2025 11:00:54.629 * <search> Acquired RedisJSON_V6 API nuq-postgres-1 | The default text search configuration will be set to "english". redis-1 | 1:M 15 Dec 2025 11:00:54.631 * Server initialized nuq-postgres-1 | nuq-postgres-1 | Data page checksums are disabled. redis-1 | 1:M 15 Dec 2025 11:00:54.632 * Ready to accept connections tcp nuq-postgres-1 | fixing permissions on existing directory /var/lib/postgresql/data ... ok nuq-postgres-1 | creating subdirectories ... ok nuq-postgres-1 | selecting dynamic shared memory implementation ... posix nuq-postgres-1 | selecting default "max_connections" ... 100 nuq-postgres-1 | selecting default "shared_buffers" ... 128MB nuq-postgres-1 | selecting default time zone ... Etc/UTC nuq-postgres-1 | creating configuration files ... ok playwright-service-1 | playwright-service-1 | > playwright-scraper-api@1.0.0 start playwright-service-1 | > node dist/api.js playwright-service-1 | nuq-postgres-1 | running bootstrap script ... ok api-1 | api-1 | ── Setting up NUQ PostgreSQL connection for docker-compose ── api-1 | api-1 | ✓ NUQ PostgreSQL connection configured with encoded credentials api-1 | api-1 | ── Starting services ── api-1 | api-1 | > api node dist/src/index.js api-1 | > worker node dist/src/services/queue-worker.js api-1 | > extract-worker node dist/src/services/extract-worker.js api-1 | > nuq-worker-0 node dist/src/services/worker/nuq-worker.js api-1 | > nuq-worker-1 node dist/src/services/worker/nuq-worker.js api-1 | > nuq-worker-2 node dist/src/services/worker/nuq-worker.js api-1 | > nuq-worker-3 node dist/src/services/worker/nuq-worker.js api-1 | > nuq-worker-4 node dist/src/services/worker/nuq-worker.js api-1 | ℹ Waiting for API on localhost:3002 nuq-postgres-1 | performing post-bootstrap initialization ... ok playwright-service-1 | Server is running on port 3000 nuq-postgres-1 | syncing data to disk ... ok nuq-postgres-1 | nuq-postgres-1 | nuq-postgres-1 | Success. You can now start the database server using: nuq-postgres-1 | nuq-postgres-1 | pg_ctl -D /var/lib/postgresql/data -l logfile start nuq-postgres-1 | nuq-postgres-1 | initdb: warning: enabling "trust" authentication for local connections nuq-postgres-1 | initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb. nuq-postgres-1 | waiting for server to start....2025-12-15 11:00:58.220 UTC [48] LOG: starting PostgreSQL 17.7 (Debian 17.7-3.pgdg13+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit nuq-postgres-1 | 2025-12-15 11:00:58.226 UTC [48] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" nuq-postgres-1 | 2025-12-15 11:00:58.264 UTC [51] LOG: database system was shut down at 2025-12-15 11:00:57 UTC nuq-postgres-1 | 2025-12-15 11:00:58.287 UTC [48] LOG: database system is ready to accept connections nuq-postgres-1 | 2025-12-15 11:00:58.305 UTC [54] LOG: pg_cron scheduler started nuq-postgres-1 | done nuq-postgres-1 | server started nuq-postgres-1 | CREATE DATABASE nuq-postgres-1 | nuq-postgres-1 | nuq-postgres-1 | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/010-nuq.sql nuq-postgres-1 | CREATE EXTENSION nuq-postgres-1 | psql:/docker-entrypoint-initdb.d/010-nuq.sql:2: ERROR: can only create extension in database postgres nuq-postgres-1 | DETAIL: Jobs must be scheduled from the database configured in cron.database_name, since the pg_cron background worker reads job descriptions from this database. nuq-postgres-1 | HINT: Add cron.database_name = 'firecrawl' in postgresql.conf to use the current database. nuq-postgres-1 | CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE nuq-postgres-1 | 2025-12-15 11:00:59.005 UTC [62] ERROR: can only create extension in database postgres nuq-postgres-1 | 2025-12-15 11:00:59.005 UTC [62] DETAIL: Jobs must be scheduled from the database configured in cron.database_name, since the pg_cron background worker reads job descriptions from this database. nuq-postgres-1 | 2025-12-15 11:00:59.005 UTC [62] HINT: Add cron.database_name = 'firecrawl' in postgresql.conf to use the current database. nuq-postgres-1 | 2025-12-15 11:00:59.005 UTC [62] CONTEXT: PL/pgSQL function inline_code_block line 4 at RAISE nuq-postgres-1 | 2025-12-15 11:00:59.005 UTC [62] STATEMENT: CREATE EXTENSION IF NOT EXISTS pg_cron; nuq-postgres-1 exited with code 3 api-1 | nuq-worker-0 2025-12-15 11:01:01 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | nuq-worker-2 2025-12-15 11:01:01 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | nuq-worker-3 2025-12-15 11:01:01 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | nuq-worker-1 2025-12-15 11:01:02 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | nuq-worker-4 2025-12-15 11:01:02 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | api 2025-12-15 11:01:02 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | api 2025-12-15 11:01:03 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | worker 2025-12-15 11:01:04 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | worker 2025-12-15 11:01:05 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-2 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | nuq-worker-0 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | nuq-worker-3 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | nuq-worker-1 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | nuq-worker-4 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | extract-worker 2025-12-15 11:01:06 warn [:]: Index supabase client will not be initialized. {} api-1 | worker 2025-12-15 11:01:07 warn [:]: Index supabase client will not be initialized. {} api-1 | api 2025-12-15 11:01:07 warn [:]: Index supabase client will not be initialized. {} api-1 | extract-worker 2025-12-15 11:01:09 warn [:]: Authentication is disabled. Supabase client will not be initialized. {} api-1 | nuq-worker-2 2025-12-15 11:01:09 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-1 2025-12-15 11:01:09 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-0 2025-12-15 11:01:09 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-4 2025-12-15 11:01:10 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | extract-worker 2025-12-15 11:01:10 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-3 2025-12-15 11:01:10 warn [:]: Authentication is disabled. Supabase ledger client will not be initialized. {} api-1 | nuq-worker-2 2025-12-15 11:01:10 info [:]: NuQ worker metrics server started api-1 | nuq-worker-2 2025-12-15 11:01:10 info [:]: Connected to Redis Session Rate Limit Store! api-1 | nuq-worker-1 2025-12-15 11:01:10 info [:]: NuQ worker metrics server started api-1 | nuq-worker-1 2025-12-15 11:01:10 info [:]: Connected to Redis Session Rate Limit Store! api-1 | nuq-worker-0 2025-12-15 11:01:10 info [:]: NuQ worker metrics server started api-1 | nuq-worker-0 2025-12-15 11:01:10 info [:]: Connected to Redis Session Rate Limit Store! api-1 | nuq-worker-3 2025-12-15 11:01:10 info [:]: NuQ worker metrics server started api-1 | nuq-worker-4 2025-12-15 11:01:10 info [:]: NuQ worker metrics server started api-1 | nuq-worker-3 2025-12-15 11:01:10 info [:]: Connected to Redis Session Rate Limit Store! api-1 | ● nuq-worker-2 15.0s api-1 | nuq-worker-4 2025-12-15 11:01:10 info [:]: Connected to Redis Session Rate Limit Store! api-1 | ● nuq-worker-1 15.2s api-1 | ● nuq-worker-0 15.2s api-1 | ● nuq-worker-4 15.2s api-1 | ● nuq-worker-3 15.2s api-1 | worker 2025-12-15 11:01:12 info [:]: Liveness endpoint is running on port 3005 api-1 | worker 2025-12-15 11:01:12 info [:]: Connected to Redis Session Rate Limit Store! api-1 | worker 2025-12-15 11:01:12 info [:]: Redis connected api-1 | worker /app/node_modules/.pnpm/pg-pool@3.10.1_pg@8.16.3_pg-native@3.5.2_/node_modules/pg-pool/index.js:45 api-1 | worker Error.captureStackTrace(err) api-1 | worker ^ api-1 | worker Error: getaddrinfo ENOTFOUND nuq-postgres api-1 | worker at /app/node_modules/.pnpm/pg-pool@3.10.1_pg@8.16.3_pg-native@3.5.2_/node_modules/pg-pool/index.js:45:11 api-1 | worker at process.processTicksAndRejections (node:internal/process/task_queues:105:5) api-1 | worker at async NuQ.getJobToProcess (/app/dist/src/services/worker/nuq.js:873:35) api-1 | worker at async crawlFinishWorker (/app/dist/src/services/queue-worker.js:304:21) api-1 | worker at async Promise.all (index 2) api-1 | worker at async /app/dist/src/services/queue-worker.js:400:5 { api-1 | worker errno: -3008, api-1 | worker code: 'ENOTFOUND', api-1 | worker syscall: 'getaddrinfo', api-1 | worker hostname: 'nuq-postgres' api-1 | worker } api-1 | worker Node.js v22.21.1 api-1 | extract-worker 2025-12-15 11:01:12 info [:]: Liveness endpoint is running on port 3004 api-1 | ✗ worker 16.5s (1) api-1 | ✗ Unhandled rejection api-1 | Error: worker failed with exit code 1 api-1 | at ChildProcess.<anonymous> (/app/dist/src/harness.js:261:24) api-1 | at ChildProcess.emit (node:events:519:28) api-1 | at maybeClose (node:internal/child_process:1101:16) api-1 | at ChildProcess._handle.onexit (node:internal/child_process:304:5) api-1 | api-1 | ── Shutting down ── api-1 | api-1 | extract-worker 2025-12-15 11:01:12 info [:]: Connected to Redis Session Rate Limit Store! api-1 | extract-worker 2025-12-15 11:01:12 info [:]: Redis connected api-1 | extract-worker 2025-12-15 11:01:12 debug [:]: Received SIGTERM. Shutting down gracefully... api-1 | extract-worker 2025-12-15 11:01:12 info [:]: No longer accepting new jobs. SIGINT api-1 | extract-worker 2025-12-15 11:01:12 info [:]: All workers exited. Waiting for all jobs to finish... api-1 | extract-worker 2025-12-15 11:01:12 info [:]: All jobs finished. Shutting down... api-1 | ✗ extract-worker 16.7s (null) api-1 | api 2025-12-15 11:01:13 info [:]: Number of CPUs: 2 available api-1 | api 2025-12-15 11:01:13 info [:]: Network info dump api-1 | api 2025-12-15 11:01:14 info [:]: Worker 15 started api-1 | api 2025-12-15 11:01:14 info [:]: Attaching WebSocket proxy to Express app api-1 | api 2025-12-15 11:01:14 info [:]: WebSocket proxy successfully attached to Express app api-1 | api 2025-12-15 11:01:14 info [:]: Worker 15 listening on port 3002 api-1 | ℹ All services running. Press Ctrl+C to stop api-1 | ✗ A service has terminated unexpectedly Error: worker failed with exit code 1 api-1 | at ChildProcess.<anonymous> (/app/dist/src/harness.js:261:24) api-1 | at ChildProcess.emit (node:events:519:28) api-1 | at maybeClose (node:internal/child_process:1101:16) api-1 | at ChildProcess._handle.onexit (node:internal/child_process:304:5) api-1 | ℹ Goodbye! api-1 exited with code 1
最新发布
12-16
1. Redis内存提交警告：可能是由于Redis配置的最大内存限制或系统内存不足导致。 2. PostgreSQL创建扩展错误：可能是由于权限不足或扩展包未安装。 3. Node.js连接PostgreSQL出现ENOTFOUND错误：可能是由于主机名...
解决git上传提交的时出现：Please tell me who you are.问题
热门推荐
Brave的博客
08-31 4万+
今天安装好git后，创建新项目，当git上传提交时出现了一个问题，如下： Commit failed - exit code 128 received, with output: '*** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's defaul
关于git提交代码时报错Committer identity unknown的解决方案
一个平平无奇的搬砖人
03-15 1989
今天安装好git后，创建新项目，当git上传提交时出现了一个问题，如下： 解释 Commit failed - exit code 128 received, with output: '*** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set your account's default ide
GitHub Desktop提交时报错误代码128
万物皆对象
09-29 1450
使用GitHub Desktop新建本地仓库提交后报错 Commit failed - exit code 128 received with output 临时的解决办法可以是打开本地仓库的路径，找到隐藏文件.git，加入你的name和email 在GitHub Desktop菜单栏点击Repository – show in Explorer进入本地仓库路径，然后找到.git文件夹双击进...
GitHub Desktop 提交错误及解决方法
王大阳的博客
08-12 5242
错误代码： Commit failed - exit code 128 received, with output: '*** Please tell me who you are. Run git config --global user.email "you@example.com" git config --global user.name "Your Name" to set...
gitlab-runner 出现 ERROR: Job failed: exit status 1
TypeXx的博客
11-11 1万+
gitlab-runner 出现 ERROR: Job failed: exit status 1grep命令 grep命令 如果gitlab-ci.yaml中包含 ... scrip: - grep root /etc/root ... 如果包含这样一句grep命令。 正常执行echo $? 是为0，你的gitlab-ci.yaml也是可以正常运行的 如果gitlab-ci.yaml中...
git Please tell me who you are...解决方法
jialong_chen的博客
07-06 735
git 的学习教程网站： 菜鸟教程 廖雪峰的网站 第一次运行时使用命令： git init git add * git commit -m “…” 运行之后提示**“Please tell me who you are…”**，这是因为创建信息不完整造成的，需要增加两条命令。 第二次： git init git config --global user.name “someone” git config --global user.email “someone@someplace.com” git
【web前端自动化工作环境配置】5. 解决git commit不成功，报错Please tell me who you are.的问题
返璞归真
07-11 1671
今天在学习git的时候，遇到了一个问题，就是git commit不成功，认真分析了一下报错原因，原来是git没有配置的原因。 找到git目录下的Git Bash运行，输入下面的两行代码运行即可： git config --global user.email "you@example.com" git config --global user.name "Your Name"
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
红包 添加红包
表情包 插入表情
表情包 代码片
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值