Fix Gorse recommendation engine pods crashing with "user: unknown userid 65532" error. Use when: (1) Gorse master/server/worker pods show CrashLoopBackOff or Error status, (2) Logs show "failed to get user directory" with unknown userid, (3) Running gorse containers with runAsNonRoot security context and custom UID. The gorse images call os.UserHomeDir() at startup which requires the UID to exist in /etc/passwd.
中文简介正在准备中。当前显示原文说明。
安装前可以查看交给 AI 代理的指令内容。
Gorse recommendation engine containers (master, server, worker) crash immediately on
startup when running with Kubernetes runAsNonRoot: true and a custom UID like 65532.
CrashLoopBackOff or Error status{"level":"fatal","ts":...,"caller":"model/built_in.go:95","msg":"failed to get user directory","error":"user: unknown userid 65532"}
securityContext.runAsNonRoot: true and runAsUser: 65532zhenghaoz/gorse-master, zhenghaoz/gorse-server, zhenghaoz/gorse-worker)The gorse codebase calls Go's os.UserHomeDir() during initialization in model/built_in.go.
This function requires the running UID to have an entry in /etc/passwd. When running as
a non-root user that doesn't exist in the container's passwd file, the lookup fails.
Remove the runAsNonRoot and runAsUser constraints from the pod security context:
# Before (broken)
spec:
template:
spec:
securityContext:
runAsNonRoot: true
runAsUser: 65532
fsGroup: 65532
# After (working)
spec:
template:
spec:
securityContext:
fsGroup: 1000
Apply to all gorse deployments:
deployment-master.yamldeployment-server.yamldeployment-worker.yamlinit-db-job.yaml (if using init job)After updating the security context:
kubectl delete pods -l app.kubernetes.io/name=gorse -n gorsekubectl logs -l app=gorse-master -n gorse/etc/passwd entries for the desired UIDos.UserHomeDir()还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Fix ArgoCD ExternalSecret deployment failing with "namespace X is not permitted in project Y". Use when: (1) ExternalSecret shows OutOfSync in ArgoCD but won't sync, (2) ArgoCD application status shows "namespace X is not permitted in project 'infrastructure'", (3) ExternalSecret targets a namespace managed by a different ArgoCD project, (4) Using apps-of-apps pattern with separate infrastructure and application projects.
中文简介正在准备中。当前显示原文说明。
Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.
中文简介正在准备中。当前显示原文说明。
Fix "Null check operator used on a null value" errors when an object is set to null during an async await. Use when: (1) Object reference is nullified while awaiting, (2) Code accesses object with ! after await returns, (3) Cancel/dispose operations run concurrently with async operations on same object. Solution: capture local reference before await.
中文简介正在准备中。当前显示原文说明。
Add custom metadata headers (x-amz-meta-*) to AWS v4 signed requests for GCS S3-compatible API. Use when: (1) Adding custom metadata to GCS uploads via S3 API, (2) Getting signature mismatch errors after adding new headers, (3) x-amz-meta-* headers being ignored or causing 403 errors. Custom headers MUST be included in canonical headers and signed headers list.
中文简介正在准备中。当前显示原文说明。
Fix password/secret authentication failures caused by trailing newlines when creating Google Cloud secrets (or similar) with bash here-strings. Use when: (1) Password authentication fails with correct password, (2) Secret created with `<<< "value"` syntax, (3) Error like "password authentication failed" or "invalid token" despite correct value. Bash here-strings (`<<<`) add a trailing newline that corrupts secrets.
中文简介正在准备中。当前显示原文说明。
Fix silent video/media processing failures caused by URL extraction code that filters on file extensions (.mp4, .webm, .webp). Use when: (1) Media moderation, transcoding, or analysis silently skips files from Blossom or content-addressed storage servers, (2) URL extraction from Nostr event tags (imeta, r tags) drops URLs without recognized extensions, (3) CDN fallback URLs append .mp4 but the actual server uses extensionless content-addressed paths like /{sha256}. Common in Nostr video events (kind 34236) where different clients use different URL formats.
中文简介正在准备中。当前显示原文说明。