Skip to content

chore(lint): enforce eslint/no-empty-pattern

MacroscopeApp / Macroscope - Effect Service Conventions completed Oct 26, 2026 in 38s

Effect Service Conventions: duplicate tracing spans

apps/desktop/src/wsl/DesktopWslEnvironment.ts: Newly named Effect wrappers duplicate existing explicit spans. An inline fix was posted.

Details

Warning

  • Invalid effort level "max" in front matter. Fell back to "low". Valid values are: low, medium, high.

Note

Your check run agent prompt is: .macroscope/check-run-agents/effect-service-conventions.md
More information about how Check Run Agents work can be found in our Help Center.

Reviewed all 206 changed files (no prior completed review)


πŸ” Agent activity β€” 7 tool calls

πŸ’­ Inspecting runtime issues I need to look into potential concrete issues, specifically with the runtime runPromise in the ServerBrowser service and the credentialStore adapter. It seems like there are new named spans being duplicated explicitly in Wsl preWarm, which could be a problem. Also, there's a significant bug in the GitHubPullRequestApi where the set viewed mutation is misplaced inside flatMap. I should inspect all of these to pinpoint the issues.

1. browse_code β€” packages/source-control-github/src/server/GitHubPullRequestApi.ts

2. browse_code β€” apps/server/src/preview/ServerBrowser.ts

3. browse_code β€” packages/provider-cursor/src/server/credentialStore.ts

4. browse_code β€” apps/server/src/orchestration-v2/http.ts

πŸ’­ Evaluating duplicate spans I'm trying to focus on avoiding duplicate spans, especially with explicit names like DesktopWsl and preWarm. I wonder if I should group findings from several locations for better clarity. It's possible that having unnamed inline DesktopWebLinks could work, but the named Wsl wraps might cause confusion with explicit spans. I need to ensure that the instrumentation is meaningful and not duplicated. I should also look into how source-control functions may cause internal span duplication.

5. browse_code β€” apps/desktop/src/wsl/DesktopWslEnvironment.ts

πŸ’­ Evaluating callback patterns I'm considering the generic pattern for using Effect.fn in a callback context. It seems that Effect.fn is meant to return an Effect result, but I'm wondering about how to handle a logger callback. Could a logger be returning an effect instead? I'll need to check and clarify this to ensure everything functions correctly. It's important to sort through this to avoid potential confusion later on!

6. browse_code β€” apps/server/scripts/record-codex-app-server-replay-fixture.ts

πŸ’­ Evaluating code efficiency I need to report on possible duplicate spans in WSL and other explicit withSpans across different areas. One comment mentions that the WSL representative covers a block. It’s a potential issue, but I notice that laziness has changed in functions, like the VcsAction execute function using yield. That can cause delayed evaluation, though it seems fine. Meanwhile, replacing the existing runPromise with context improves performance while keeping the same boundaries to avoid complications.

7. modify_pr β€” Submitted review with 1 inline comment


Agent Credits: 40 credits

Token usage: 15 uncached input Β· 434,637 cache-read input Β· 110,094 cache-write input Β· 945 output
Agent Credits may also include non-token charges from external tools such as web research.