Ticket Investigations

Root cause analyses produced by the Debug Agent Pipeline.

Investigations

TicketClientSeverityStatusRoot Cause
SLANUSZ-25NUSZP1Root Cause IdentifiedIP-based rate limiter + corporate NAT blocks all operators
FKITDEV-8521MKBMinorFix ReadyPhantom 3h waiting time — null cache + broad LIKE + stale cache race condition
FKITDEV-server-session-too-lowAllP2Triaged7 processes × 100 pool max = 700 connections, no idle/acquire/evict lifecycle
FKITDEV-8639NUSZP2TriagedExcel export missing Sum values + locale param bug + independent rounding
FKITDEV-8659InternalToolingCompleteCLI scripts for extracting and decrypting room attachments
CLI System CheckInternalP2TriagedWiring task — expose existing diagnostic data to CLI system-check command
Room 62243 ScreenshotNUSZP2CompleteBrowser never responds to videochat:screenshot:remote — 100% failure rate, 91 rooms, 31 days
ASSICASH-71InstaCashP2In ReviewPROD vuer_css portal.url UAT misconfig (fixed in FKITSYS-9486); WebServer.js CSP-violation logger amplifies any drift
FKITDEV-8787RaiffeisenP2-MediumTriagedMobile SDK Already authorized / Already has some kind of room — phantom-room family; SDK-local guards, OSS V2 silently resumes any non-closed room. Working hypothesis: in-app Restart leaves stale SDK session
FKITDEV-8252Internal (fleet)P2-ProactiveIn ProgressUBI10 migration ahead of RHEL 9 EOL; vuer_build Phase A on feature/FKITDEV-8252-ubi10 (15 commits ahead, 4 Dockerfiles uncommitted); decisions on per-key rpmkeys SHA1, OL9 instantclient on UBI10, vuer_cv 2h spike; probe-builds blocked on podman sandbox
FKITDEV-8533GeneraliP2Changes RequestedPR #7893 videoOrientExt tablet fix unreliable — modern iPadOS 13+ Safari reports a macOS UA, ua-parser-js v1 yields device.type === undefined; isTablet() is a logical subset of isMobile() (redundant). Correct fix = client-side navigator.maxTouchPoints detection
Face Comparison DB QueryPP3TriagedCustomer premise (“difference values not in DB”) false — faceComparisons stores euclideanDistance unconditionally; different_face is a read-time threshold verdict, not a stored status. Solved with one read-only SQL query, no release

How to Add

New investigations are created by running the debug agent pipeline on a YouTrack ticket. The pipeline:

  1. Decodes the complaint (Hungarian → technical signal)
  2. Triages with severity, affected components, debugging checklist
  3. Plans reproduction using room exports and dev environment
  4. Investigates root cause with 5-Whys evidence chain
  5. Documents findings here in Obsidian

See debug-agents for full pipeline documentation.

15 items under this folder.