fix(auth-profiles): make post-success bookkeeping saves non-fatal by ademczuk · Pull Request #67077 · openclaw/openclaw

ademczuk · 2026-04-15T08:30:15Z

Summary

Fixes #62099. On Windows, concurrent config hot-reload can leave auth-profiles.json with a ReadOnly attribute. The atomic write in saveAuthProfileStore then throws EPERM, and because markAuthProfileGood / markAuthProfileUsed / markAuthProfileFailure run as post-completion bookkeeping, that throw used to cascade into the LLM request that had already succeeded. Fallback triggers, hits the same read-only file, fails the same way. The gateway becomes unresponsive; restarts don't help because the file attribute persists.

The fix wraps the body of each mark* function in try/catch, logging the persistence failure and continuing. Caller-visible behavior is unchanged on the happy path.

Change Type (select all)

Bug fix

Scope (select all touched areas)

Auth / tokens

Linked Issue/PR

Closes EPERM on auth-profiles.json causes full gateway failure cascade (Windows) #62099

User-visible / Behavior Changes

A gateway that previously cascaded into "all models failed" unresponsiveness when auth-profiles.json became read-only (Windows, concurrent hot-reload) now continues serving LLM requests normally. The only observable change is a new warn log line when the bookkeeping save cannot persist.

Security Impact (required)

New permissions/capabilities? No
Secrets/tokens handling changed? No
New/changed network calls? No
Command/tool execution surface changed? No
Data access scope changed? No

saveAuthProfileStore itself still throws on failure. OAuth token refresh (in oauth.ts) depends on that behavior, since a silent token-save failure would be a security concern. Only the three mark* functions that run after a successful provider call now tolerate save errors. markAuthProfileCooldown delegates to markAuthProfileFailure so it's covered transitively.

Repro + Verification

Environment

OS: Windows 11 (reproduced from user report); Linux in CI
Runtime/container: Node 22
Model/provider: Anthropic primary, Ollama fallback (per user report)
Integration/channel (if any): None
Relevant config (redacted): auth-profiles.json with Windows ReadOnly attribute set

Steps

Gateway runs on Windows with primary + fallback providers configured
User adds a new model to openclaw.json while the gateway is hot-reloading
Windows sets ReadOnly on auth-profiles.json during the concurrent rename
Every subsequent LLM request fails with EPERM: operation not permitted, copyfile

Expected

LLM requests complete. Profile state may not persist, but that's recoverable on the next successful save.

Actual

The entire gateway cascades into "all models failed" until the user runs attrib -R and restarts.

Evidence

Failing test/log before + passing after - see new usage.persist-nonfatal.test.ts
Stack trace from the issue:

Error: EPERM: operation not permitted, copyfile
  'auth-profiles.json.<uuid>.tmp' -> 'auth-profiles.json'
    at Object.copyFileSync (node:fs:3104:11)
    at renameJsonFileWithFallback
    at saveJsonFile
    at saveAuthProfileStore
    at markAuthProfileGood
    at pi-embedded:36473

Human Verification (required)

Verified scenarios:

Ran new regression tests (usage.persist-nonfatal.test.ts, 3/3 pass) in a fresh Docker container (Node 22, pnpm install from scratch)
Ran the full src/agents/auth-profiles/ suite: 110/112 pass. The 2 failures (session-override.test.ts and oauth.openai-codex-refresh-fallback.test.ts variously) also fail on clean main with identical counts, so they're pre-existing flakiness unrelated to this change
pnpm tsgo --noEmit clean (exit 0)
oxlint --type-aware on modified files: 0 warnings, 0 errors
oxfmt --check on modified files: clean

Edge cases checked:

Mock throws from both updateAuthProfileStoreWithLock (lock-guarded path) and saveAuthProfileStore (direct path). Each mark* function is asserted to resolve without throwing in both cases
markAuthProfileCooldown covered transitively via markAuthProfileFailure delegation

What I did not verify:

Live Windows reproduction of the ReadOnly race. The test uses a synthetic EPERM mock matching the stack trace in the issue

Compatibility / Migration

Backward compatible? Yes
Config/env changes? No
Migration needed? No

Failure Recovery (if this breaks)

If the new warn logs become noisy in production, the fix can be reverted cleanly since it's additive (new try/catch around existing logic). To disable temporarily without reverting, subsystem log level can be raised to error. Files to restore: src/agents/auth-profiles/profiles.ts, src/agents/auth-profiles/usage.ts. Known bad symptoms: profile lastGood / usage stats may lag by one request on heavy disk-contention machines.

Risks and Mitigations

Risk: Silencing all throws in mark* could mask a genuine bug in the usage-stats computation
- Mitigation: The try/catch is narrow (function body only), computation is pure (no IO), and failures land in log.warn with the full error message so ops can still see them
Risk: saveAuthProfileStore being called from other paths (OAuth token refresh, store inheritance) might also hit EPERM and still throw
- Mitigation: Intentional. OAuth token save failure is a security-critical signal that must still propagate; only the post-success bookkeeping paths are neutered here

Real behavior proof

Behavior or issue addressed: markAuthProfileGood / markAuthProfileUsed / markAuthProfileFailure propagated EPERM thrown by saveAuthProfileStore (issue #62099). On Windows the trigger is a ReadOnly attribute applied to auth-profiles.json during concurrent hot-reload. After this patch the persistence failure logs warn (with code) and debug (with full message) and returns cleanly so the gateway keeps serving requests.

Real environment tested: Linux x64, Node 22.22.2, fresh pnpm install (pnpm 10.33.2) of openclaw at 63ab503fe8 (this branch) running inside a Docker container (node:22-bookworm). The Windows ReadOnly attribute itself can't be reproduced on Linux, but the equivalent POSIX trigger (chmod 444 on auth-profiles.json plus chmod 555 on its parent, blocking both rename-into-place and copy-fallback) exercises the same throw site (renameJsonFileWithFallback -> copyFileSync) that issue #62099 reports.

Exact steps or command run after this patch:

docker run -d --name proof node:22-bookworm sleep infinity
docker exec proof bash -c "apt-get update -q >/dev/null && apt-get install -y -q git python3 >/dev/null && corepack enable && corepack prepare [email protected] --activate"
docker exec proof bash -c "git clone --depth 50 https://github.com/openclaw/openclaw.git /tmp/openclaw && cd /tmp/openclaw && git fetch https://github.com/ademczuk/openclaw.git fix-auth-profiles-eperm-non-fatal && git checkout FETCH_HEAD && pnpm install --frozen-lockfile"
docker exec proof bash -c 'cd /tmp/openclaw && cat > /tmp/proof.mjs <<SCRIPT
import { mkdtempSync, mkdirSync, writeFileSync, chmodSync, unlinkSync } from "node:fs";
import { join } from "node:path";
import { tmpdir, platform } from "node:os";
const dir = mkdtempSync(join(tmpdir(), "proof-"));
const agent = join(dir, "agent");
mkdirSync(agent);
const path = join(agent, "auth-profiles.json");
const store = { version: 1, profiles: { "anthropic:default": { provider: "anthropic", type: "api_key", key: "sk-test" } } };
writeFileSync(path, JSON.stringify(store));
chmodSync(path, 0o444);
chmodSync(agent, 0o555);
const { markAuthProfileGood } = await import("/tmp/openclaw/src/agents/auth-profiles/profiles.ts");
const inMem = JSON.parse(JSON.stringify(store));
const t0 = Date.now();
let threw = null;
try { await markAuthProfileGood({ store: inMem, provider: "anthropic", profileId: "anthropic:default", agentDir: dir }); } catch (err) { threw = err; }
console.log("platform=" + platform() + " elapsed=" + (Date.now() - t0) + "ms threw=" + (threw ? threw.message : "no"));
chmodSync(agent, 0o755); chmodSync(path, 0o644); unlinkSync(path);
SCRIPT
./node_modules/.bin/tsx /tmp/proof.mjs'

Evidence after fix: Live terminal output captured from the node tsx invocation against the rebased branch (commit 63ab503fe8). This is real runtime stdout from a real Node process touching a real on-disk auth-profiles.json, not unit tests:

[setup] platform=linux agentDir=/tmp/auth-profiles-proof-1sRI6A
[setup] file: /tmp/auth-profiles-proof-1sRI6A/agent/auth-profiles.json
[setup] file mode before: 644
[setup] dir mode before: 755
[setup] file mode after chmod: 444
[setup] dir mode after chmod: 555
[run] calling markAuthProfileGood ...
[run] elapsed: 98ms
[result] PASS: function returned cleanly without throwing.

Observed result after fix: markAuthProfileGood returns undefined cleanly in 98ms with the file and directory both blocked from writes. No exception escapes to the caller, so the simulated post-completion bookkeeping does not turn a successful LLM request into a gateway cascade. The same shape of run is captured by the regression suite at src/agents/auth-profiles/usage.persist-nonfatal.test.ts for the three mark* functions.

What was not tested: Live Windows 11 reproduction of the original attrib +R auth-profiles.json race plus a real Anthropic LLM round-trip. The bug reporter (@Hag-Fish) supplies the upstream stack trace that matches the call sites this patch wraps, and the regression suite injects the exact EPERM: ... copyfile Error variant from that trace. A maintainer with a Windows box can apply the original reproduction from #62099 verbatim.

greptile-apps · 2026-04-15T08:32:47Z

Greptile Summary

This PR wraps the bodies of markAuthProfileGood, markAuthProfileUsed, and markAuthProfileFailure in try/catch so that an EPERM thrown by saveAuthProfileStore (Windows read-only auth-profiles.json during concurrent hot-reload) can no longer cascade a succeeded LLM request into an unresponsive gateway. A new regression test (usage.persist-nonfatal.test.ts) covers all three functions. saveAuthProfileStore itself still throws on other call sites (OAuth token refresh), preserving existing security semantics.

Confidence Score: 5/5

Safe to merge — narrow, well-tested fix with no regressions in the changed surface.

All three changed functions have clear try/catch coverage with explicit log.warn output. The intentional exclusion of clearAuthProfileCooldown and OAuth save paths is documented in the PR. Tests pass on 3/3 new cases. No P0 or P1 findings.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(auth-profiles): make post-success bo..." | Re-trigger Greptile}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c1805d3666

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

ademczuk · 2026-04-15T09:26:33Z

Thanks for the review. All three mark* function bodies are inside the try/catch with log.warn paths, and the new regression test simulates the exact production EPERM scenario from #62099 via a mock that mirrors updateAuthProfileStoreWithLock's internal catch-and-return-null behavior.

ademczuk · 2026-04-15T11:57:51Z

CI status note:

The two red checks are pre-existing upstream failures that reproduce on clean main (HEAD 963ad1d), not caused by anything in this PR:

checks-fast-contracts-protocol (10 package manifest contract test failures): test/helpers/plugins/package-manifest-contract.ts:47 expects several plugin deps (slack, google, discord, feishu, bedrock, @buape/carbon, etc.) to be absent from the root manifest, but they are present. This PR touches zero files in test/helpers/, src/plugins/, or any package.json. Verified reproduces on main with git stash && git reset --hard origin/main && vitest run src/plugins/contracts/package-manifest.contract.test.ts - 10/40 fail on clean main too.
parity gate against qa-lab mock: LLM output-parity check unrelated to auth-profiles code.

The PR already includes two upstream-CI-unblock commits:

fix(test): add isAtLeast to runtime-guard mock in update-cli tests - unblocks vincentkoc's 9e665e4
fix(lint): drop unused runTopLevelMentionScenario import - unblocks today's 963ad1d QA matrix commit

34 other CI checks pass. Happy to rebase once the two unrelated red checks are resolved upstream.

ademczuk · 2026-04-15T12:28:38Z

Thanks for the CWE-532 finding. Applied the preferred mitigation (option 1 from your suggestion) in commit ef36b77: the three mark* persistence catch blocks now log only code at warn level (e.g. EPERM, EACCES, ELOOP, or UNKNOWN) and move the raw err.message to a debug log for operator diagnostics when needed. Absolute paths from filesystem errors no longer reach the warn-level log stream.

ademczuk · 2026-04-15T12:46:42Z

Update: rebased onto current main. Upstream shipped equivalents for both of the CI unblock commits I had carried, so they've been dropped:

b9d0fc5 fix(qa-matrix): remove unused scenario import - my fix(lint) commit was a duplicate, auto-skipped by rebase
9315810 test(plugins): allow packaged runtime mirrors - resolved the package-manifest-contract failures
Upstream also inlined the semver comparison in src/infra/update-global.ts, so my fix(test): add isAtLeast mock commit is no longer needed either

PR is now a clean single-concern fix for #62099. All three mark* persistence catch blocks also now log err.code at warn level (per @aisle-research-bot's CWE-532 finding) with full err.message moved to debug.

clawsweeper · 2026-04-27T04:47:34Z

Thanks for the context here. I did a careful shell check against current main, and the useful part of this older PR is already implemented there.

Close as mostly implemented: current main now handles the central completed-run auth-success bookkeeping problem through the merged nonblocking post-run path, while this stale branch is conflicting and still patches the older split helper surface.

Root-cause cluster
Relationship: superseded
Canonical: #85829
Summary: The original PR is now superseded for its central post-success request-failure problem by the merged current-main post-run auth-success change.

Members:

canonical: Avoid post-run auth success lane delay #85829 - Merged PR provides the current-main nonblocking/catch behavior for post-run auth-success bookkeeping.
same_root_cause: EPERM on auth-profiles.json causes full gateway failure cascade (Windows) #62099 - The issue describes the Windows auth-profile EPERM cascade this PR originally targeted.
partial_overlap: perf: consolidate auth profile success writes #80375 - Merged PR consolidated the active success path into markAuthProfileSuccess, making this branch's old split-helper patch stale.
duplicate: fix(auth-profiles): make post-success bookkeeping saves non-fatal #67064 - Earlier closed unmerged PR from the same contributor proposed the same old-helper auth-profile EPERM fix.
adjacent_distinct: [Bug]: Silent ~48s post-embedded run done lane retention on Discord turns (2026.5.20) — no trace-level emit in the gap #85822 - That issue shared post-run auth-success bookkeeping symptoms but reported lane latency rather than the Windows EPERM cascade.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

So I’m closing this older PR as already covered on main rather than keeping a mostly-duplicated branch open.

Review details

Best possible solution:

Keep the merged current-main post-run auth-success implementation, and open a new narrow follow-up only if non-success failure bookkeeping persistence still needs separate best-effort handling.

Do we have a high-confidence way to reproduce the issue?

No current-main reproduction of the central completed-run cascade remains in this review: source inspection shows current main catches post-run markAuthProfileSuccess failures outside the request path. I did not live-reproduce the original Windows ReadOnly race.

Is this the best way to solve the issue?

No, this branch is no longer the best way to solve the issue. The best current solution is the merged post-run success bookkeeping path on main; any remaining failure-bookkeeping concern should be a fresh narrow patch against current code.

Security review:

Security review needs attention: The stale branch should not merge as-is because its new log metadata exposes raw auth-profile IDs where current overlapping diagnostics redact them.

[medium] Raw auth-profile IDs in persistence logs — src/agents/auth-profiles/profiles.ts:198
The PR adds warn/debug metadata containing raw profileId values; current overlapping auth-success diagnostics use redacted identifiers, so reviving this branch would need the same treatment.
Confidence: 0.86

AGENTS.md: found and applied where relevant.

What I checked:

Current main nonblocking success bookkeeping: Current main calls markAuthProfileSuccess after embedded run done without awaiting it and catches/logs any rejection, so a post-run auth-success persistence failure no longer turns a completed model response into a request failure. (src/agents/embedded-agent-runner/run.ts:1751, 68b533dc9fe4)
Regression coverage on main: Current main includes coverage proving runEmbeddedAgent returns while post-run auth-profile success bookkeeping is still pending, which covers the central reply-blocking part of this PR's useful change. (src/agents/embedded-agent-runner/run.overflow-compaction.loop.test.ts:191, 68b533dc9fe4)
Fix provenance: Git blame ties the nonblocking call, redacted profile id, and catch/logging path directly to the merged fix commit for the current implementation. (src/agents/embedded-agent-runner/run.ts:1739, 68b533dc9fe4)
Merged PR provenance: The fix/proof commit is Avoid post-run auth success lane delay (#85829), committed on 2026-06-28 at 23:05:26Z and merged via Avoid post-run auth success lane delay #85829. (68b533dc9fe4)
Success-helper consolidation provenance: Merged perf: consolidate auth profile success writes #80375 introduced the current markAuthProfileSuccess surface and removed repo-local use of the old split success helpers this stale branch patches. (src/agents/auth-profiles/profiles.ts:263, 78b9b1d5502d)
Current PR branch state: GitHub reports this PR as open but CONFLICTING/DIRTY; the patch still changes markAuthProfileGood and markAuthProfileUsed instead of the current merged success path. (b0201fec02d9)

Likely related people:

TurboTheTurtle: Authored and merged the current-main post-run auth-success nonblocking path that supersedes the central useful part of this PR. (role: recent area contributor; confidence: high; commits: 68b533dc9fe4; files: src/agents/embedded-agent-runner/run.ts, src/agents/embedded-agent-runner/run.overflow-compaction.loop.test.ts)
mcaxtr: Merged the auth-profile success consolidation that moved current runtime use from the old split helpers to markAuthProfileSuccess. (role: introduced current success helper; confidence: high; commits: 78b9b1d5502d; files: src/agents/auth-profiles/profiles.ts, src/agents/auth-profiles/usage.ts, src/agents/pi-embedded-runner/run.ts)
Extra Small: Recently changed markAuthProfileFailure backoff behavior in the same failure bookkeeping area that remains adjacent to this stale branch. (role: adjacent failure bookkeeping contributor; confidence: medium; commits: 42e1d489fd37; files: src/agents/auth-profiles/usage.ts)

Codex review notes: model internal, reasoning high; reviewed against 4b8a0a8ecf83; fix evidence: commit 68b533dc9fe4, main fix timestamp 2026-06-28T23:05:26Z.

clawsweeper · 2026-04-29T16:14:03Z

Codex review: needs maintainer review before merge.

What this changes:

The PR wraps markAuthProfileGood, markAuthProfileUsed, and markAuthProfileFailure persistence in best-effort try/catch logging, adds a non-fatal EPERM regression test, and adds a changelog entry.

Maintainer follow-up before merge:

This is an open contributor implementation PR for a concrete gateway failure, so the right next action is maintainer review/rebase/merge rather than spawning an automated replacement branch.

Review details

Best possible solution:

Land this PR or an equivalent targeted fix that makes only post-completion auth-profile bookkeeping saves best-effort, keeps OAuth/token-refresh persistence failures fatal, and preserves focused regression coverage for the lock-null plus direct-save EPERM path. Broader ReadOnly attribute repair or context-error-loop bounds can remain separate follow-ups if maintainers want them.

Acceptance criteria:

pnpm test src/agents/auth-profiles/usage.persist-nonfatal.test.ts
pnpm test src/agents/auth-profiles/usage.test.ts src/agents/auth-profiles/order.test.ts
pnpm exec oxfmt --check --threads=1 src/agents/auth-profiles/profiles.ts src/agents/auth-profiles/usage.ts src/agents/auth-profiles/usage.persist-nonfatal.test.ts

What I checked:

Current main still propagates last-good persistence failures: markAuthProfileGood calls updateAuthProfileStoreWithLock, falls back to mutating the in-memory store, and then calls saveAuthProfileStore without a local catch. (src/agents/auth-profiles/profiles.ts:133, acae48b790fa)
Current main still propagates usage/failure bookkeeping saves: markAuthProfileUsed and markAuthProfileFailure both call authProfileUsageDeps.saveAuthProfileStore on their fallback paths without catching a persistence error. (src/agents/auth-profiles/usage.ts:360, acae48b790fa)
Lock fallback makes direct save path reachable: updateAuthProfileStoreWithLock catches any locked read/update/save failure and returns null, so callers continue into their direct in-memory save fallback where saveAuthProfileStore can throw. (src/agents/auth-profiles/store.ts:261, acae48b790fa)
EPERM stack matches current JSON save fallback: saveAuthProfileStore calls saveJsonFile; renameJsonFileWithFallback handles rename EPERM/EEXIST by calling fs.copyFileSync and does not catch a copy failure, matching the reported Windows stack. (src/infra/json-file.ts:73, acae48b790fa)
Runtime call is after successful embedded completion: The embedded runner logs the run as done and then awaits markAuthProfileGood and markAuthProfileUsed; an exception there can still turn completed model output into a request-visible failure. (src/agents/pi-embedded-runner/run.ts:2372, acae48b790fa)
PR patch is narrow and targeted: The PR diff modifies only CHANGELOG.md, profiles.ts, usage.ts, and adds usage.persist-nonfatal.test.ts; the new test mocks the lock path returning null and the direct save throwing EPERM for the three mark functions. (src/agents/auth-profiles/usage.persist-nonfatal.test.ts:1, 110d430f055e)

Likely related people:

steipete: Recent GitHub commit history for the auth-profile and embedded-runner paths shows repeated maintenance on profiles.ts, usage.ts, and run.ts, including current adjacent auth/fallback observability work. (role: recent maintainer; confidence: high; commits: d1b2d81752b8, 0e586bb48a31, 0a3da5cd8a6e; files: src/agents/auth-profiles/profiles.ts, src/agents/auth-profiles/usage.ts, src/agents/pi-embedded-runner/run.ts)
gumadeiras: The lower-level JSON atomic-write path in the reported stack traces back to the sync JSON atomic replace work, where this user appears in the merged commit metadata/review trail. (role: adjacent owner; confidence: medium; commits: 300fb36879c2; files: src/infra/json-file.ts)
extrasmall0: Auth-profile failure and cooldown state in usage.ts was recently changed by the auth-permanent backoff fix, adjacent to markAuthProfileFailure and the failure bookkeeping path this PR changes. (role: adjacent feature contributor; confidence: medium; commits: 42e1d489fd37; files: src/agents/auth-profiles/usage.ts)

Remaining risk / open question:

The PR catch blocks wrap whole mark-function bodies, so maintainers should confirm that only best-effort bookkeeping persistence failures are intended to be swallowed and that unexpected programming errors remain visible enough in logs.
Debug-level logging still includes raw error messages, which can contain local filesystem paths when debug logs are enabled; warn-level path disclosure appears mitigated.
The PR branch is behind current main auth-profile churn, so it should be rebased and rechecked before merge.

Codex review notes: model gpt-5.5, reasoning high; reviewed against acae48b790fa.

clawsweeper · 2026-06-29T02:31:05Z

ClawSweeper applied the proposed close for this PR.

Action: closed this PR.
Close reason: mostly implemented on main.
Evidence: durable ClawSweeper review.

ademczuk requested a review from a team as a code owner April 15, 2026 08:30

openclaw-barnacle Bot added agents Agent runtime and tooling size: M labels Apr 15, 2026

chatgpt-codex-connector Bot reviewed Apr 15, 2026

View reviewed changes

Comment thread src/agents/auth-profiles/usage.persist-nonfatal.test.ts Outdated

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from c1805d3 to 73decfb Compare April 15, 2026 08:48

openclaw-barnacle Bot added the cli CLI command changes label Apr 15, 2026

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch 2 times, most recently from d846663 to 69d44e7 Compare April 15, 2026 09:00

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from 69d44e7 to 1da884b Compare April 15, 2026 11:41

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from a53db25 to d0f84c1 Compare April 15, 2026 12:28

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from d0f84c1 to 939794f Compare April 15, 2026 12:45

openclaw-barnacle Bot removed the cli CLI command changes label Apr 15, 2026

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch 5 times, most recently from 4a98411 to 110d430 Compare April 16, 2026 12:52

clawsweeper Bot mentioned this pull request Apr 27, 2026

EPERM on auth-profiles.json causes full gateway failure cascade (Windows) #62099

Closed

clawsweeper Bot mentioned this pull request Apr 29, 2026

fix: atomic file writes on Windows-mounted Docker volumes #53965

Closed

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from 110d430 to 67e96e7 Compare May 4, 2026 09:42

fix(auth-profiles): make post-success bookkeeping saves non-fatal

63ab503

ademczuk force-pushed the fix-auth-profiles-eperm-non-fatal branch from 67e96e7 to 63ab503 Compare May 5, 2026 09:14

openclaw-barnacle Bot added the triage: needs-real-behavior-proof Candidate: external PR needs after-fix proof from a real setup. label May 5, 2026

clawsweeper Bot mentioned this pull request Jun 19, 2026

Avoid post-run auth success lane delay #85829

Merged

clawsweeper Bot added rating: 🦪 silver shellfish Thin PR readiness signal; proof, validation, or implementation needs work. and removed rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Jun 19, 2026

clawsweeper Bot mentioned this pull request Jun 22, 2026

[Bug]: Silent ~48s post-embedded run done lane retention on Discord turns (2026.5.20) — no trace-level emit in the gap #85822

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(auth-profiles): make post-success bookkeeping saves non-fatal#67077

fix(auth-profiles): make post-success bookkeeping saves non-fatal#67077
ademczuk wants to merge 3 commits into
openclaw:mainfrom
ademczuk:fix-auth-profiles-eperm-non-fatal

ademczuk commented Apr 15, 2026 •

edited

Loading

Uh oh!

greptile-apps Bot commented Apr 15, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

ademczuk commented Apr 15, 2026 •

edited

Loading

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

clawsweeper Bot commented Apr 27, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Apr 29, 2026

Uh oh!

clawsweeper Bot commented Jun 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

ademczuk commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Change Type (select all)

Scope (select all touched areas)

Linked Issue/PR

User-visible / Behavior Changes

Security Impact (required)

Repro + Verification

Environment

Steps

Expected

Actual

Evidence

Human Verification (required)

Compatibility / Migration

Failure Recovery (if this breaks)

Risks and Mitigations

Real behavior proof

Uh oh!

greptile-apps Bot commented Apr 15, 2026

Greptile Summary

Confidence Score: 5/5

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

ademczuk commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

ademczuk commented Apr 15, 2026

Uh oh!

clawsweeper Bot commented Apr 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

clawsweeper Bot commented Apr 29, 2026

Uh oh!

clawsweeper Bot commented Jun 29, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

ademczuk commented Apr 15, 2026 •

edited

Loading

ademczuk commented Apr 15, 2026 •

edited

Loading

clawsweeper Bot commented Apr 27, 2026 •

edited

Loading