3 ms·
> Process monitoring at 0.1-second intervals found zero git processes around reset times. I don’t think this is a valid way of checking for spawned processes.
by kccqzy 7mo ago
> Process monitoring at 0.1-second intervals found zero git processes around reset times.
I don’t think this is a valid way of checking for spawned processes. Git commands are fast. 0.1-second intervals are not enough. I would replace the git on the $PATH by a wrapper that logs all operations and then execs the real git.
- wswope 7mo agoSure looks to me like this whole case is Claude Code chasing its own tail, failing to debug, and offering to instead generate a bug report for the user when it can't figure out a better way forward. Maybe even submitting the bug report "agentically" without user input, if it's running on host without guardrails (pure speculation). E: It's a runaway bot lol https://github.com/anthropics/claude-code/issues/40701#issuecomment-4151187676 https://github.com/anthropics/claude-code/issues/40701#issue...
- bendews 7mo agoThis HN account is also by the same user as github, this submission may be AI created. I wonder if they've let **claw run loose over their whole online presence and this is the result.
- bruce_one 7mo agoeBPF is a great tool to use for debugging this kind of thing too, e.g. [bpftrace](https://bpftrace.org https://bpftrace.org) has an [execsnoop](https://github.com/bpftrace/bpftrace/blob/master/tools/execsnoop.bt https://github.com/bpftrace/bpftrace/blob/master/tools/execs...) script for looking at everything being exec'd on the system :-) (No need to use bpftrace, just an easy example :-) )