[BUG] Scrolling up in Linux terminal mangles the lines
Open 💬 1 comment Opened Jun 14, 2026 by AndreiBarbuOz
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When I scroll up in Terminator on Linux the lines are mangled up
What Should Happen?
Lines should not be mangled up
Error Messages/Logs
Steps to Reproduce
- Use claude in Terminator on Linux
- prompt
- scroll up a few screens
Claude Model
Opus
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.177 (Claude Code)
Platform
Anthropic API
Operating System
Ubuntu/Debian Linux
Terminal/Shell
Other
Additional Information
● Health investigation complete, and the three skills now carry one-shot recipes for this. Here's the verdict.
Post-rollout health — PR #10230 (DEV/NST/ALP/AGOV)
No regression from the rollout. All bumped components green.
┌───────────────────────────────────────────────────┬───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│ Check │ Result │
├───────────────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Controller error-rate (markAsFailed + │ Flat across the 19:00 boundary — no step-up. alp ~2000/2h, nst ~700/2h are chronic baselines; top failures are the usual flip-floppers (RecoveryVault, ManagedRedisAccess, ServiceAccess, │
│ STATUS_CODE_ERROR) │ PostgreSQL, PrivateEndpoint…), nothing new │
├───────────────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ESO (external-secrets 2.6.0) │ ✅ 0 errors in logs, 0 warning events — green │
├───────────────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Flux Kustomizations │ ✅ 0 errors, reconciling normally │
├───────────────────────────────────────────────────┼───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Crossplane (2.3.2) │ ✅ 0 errors, 0 warnings │
159 +| extend ns = tostring(ResourceAttributes["k8s.namespace.name"]),
160 + cl = tostring(ResourceAttributes["k8s.cluster.name"])
161 +| where ns in ("external-secrets","flux-system","crossplane-system")
162 +| where SeverityText in ("ERROR","Error","error")
163 +| summarize c=count(), sample=take_any(Body) by cl, ns
164 +| order by c desc | take 20
165 +```
166 +
167 +### Ingestion gotcha (verified 2026-06-14)
168 +
169 +`alp` does **not** ship `external-secrets` / `flux-system` / `crossplane-system` logs to OTELLogs (zero `Total` for those namespaces), while `dev`/`nst`/`agov`/`local` do. For alp component health, fall back to the `kube-events`
+post-deploy sweep (KubeEvents covers alp). Flux is low-volume (~60 log lines/2h/cluster) — a low `Total` there is normal, not a gap.
170 +
171 ## Notes
172
173 - The `azuredataexplorerexporter` writes JSON values into the `dynamic` columns. Always wrap field access in `tostring(...)` when filtering or grouping by string keys, otherwise the implicit type is `dynamic` and equality won't m
atch.
● Health investigation complete, and the three skills now carry one-shot recipes for this. Here's the verdict.
<img width="2491" height="1122" alt="Image" src="https://github.com/user-attachments/assets/7bd582bb-502f-4482-9d75-94a6f17b5246" />
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗