Status buffer issues

[kareltucek]

Two issues:

1. sometimes, Agent splits the status buffer in halves, and shows only one of the halfs to the user.
2. some macro errors contain specification of binding site. Agent is removing these lines. This is confusing, because the logs look redundant.

I suspect that 1 is caused by an unexpected content of 2.

[ert78gb]

Is there a way to reproduce? It could help to fix easier

[kareltucek]

diagnose usb macro tends to do that with uhk60 and say this firmware :https://github.com/UltimateHackingKeyboard/firmware/actions/runs/30825488111

c2usb diag (t=8751 ms):
  power=L0-on configured=1 active=1
  last ok transfer: EP 83, 621 ms ago (76 total)
  ctrl stall: total=4 sinceOk=0, last: EP 00 err=0 7994 ms ago
  bus event: suspend x1, last 8746 ms ago
  bus event: resume x1, last 8166 ms ago
  bus event: reset x2, last 8079 ms ago
  bus event: set-config x1, last 7966 ms ago
hid state (t=8752 ms):
  sessions: kb=1 mouse=1 controls=1 cmd=1
  powerMode=0 usbUp=1 usbAwake=1
  key life (ms ago): scan(1)=1 queued=8752/forceQueued=8752/applied=1 action=1 delivered=7938
  inactive kb report: 
  semaphore (inFlight/retries/needsResend): kb=0/0/0 ctl=0/0/0 mouse=0/0/0 givenUp=0
  throttle: 1 ms ago blocked=0 reasons=0x0 until=in -8752 ms postponed=0x0
  isr (start/end ms ago): usb=622/622 pit=4294967295/4294967295 wdog=51/51 i2c=4294967295/4294967295 btn=8752/8752
  i2c watchdog: watch=87 recoveries=0
  stack: used=1584/4096 headroom=2512
Printing trace buffer because: Diagnostics reboot.
ID: 2, EV: 67109381, Tag: staging_260803_v2
Uptime: 8753 ms, Last main: 2 ms ago
Trace:
i6><i6><i6<U18>><i6><i6><F14><F1>(l9)<F10><i6><i6<U9>><i6><i6><F
14><F14><F10><i6><i6<U9>><i6><i6><F14><F1>(l9)<i6><i6<U9>><i6><i
6><F14><F10><F14><i6><i6<U9>><i6><i6><F14><F1>(l9)<F10><i6><i6<U
9>><i6><i6><F14>(l6u1u2v3w0w1x1x2x3x4w2w3w4w5w6ve3u7u8)(l6u1u2

and

v1

or

c2usb diag (t=77721 ms):
  power=L0-on configured=1 active=1
  last ok transfer: EP 83, 245 ms ago (631 total)
  ctrl stall: total=4 sinceOk=0, last: EP 00 err=0 77080 ms ago
  bus event: suspend x1, last 77716 ms ago
  bus event: resume x1, last 77255 ms ago
  bus event: reset x2, last 77156 ms ago
  bus event: set-config x1, last 77045 ms ago
hid state (t=77722 ms):
  sessions: kb=1 mouse=1 controls=1 cmd=1
  powerMode=0 usbUp=1 usbAwake=1
  key life (ms ago): scan(1)=1 queued=77722/forceQueued=77722/applied=1 action=1 delivered=77018
  inactive kb report: 
  semaphore (inFlight/retries/needsResend): kb=0/0/0 ctl=0/0/0 mouse=0/0/0 givenUp=0
  throttle: 1 ms ago blocked=0 reasons=0x0 until=in -77722 ms postponed=0x0
  isr (start/end ms ago): usb=246/246 pit=4294967295/4294967295 wdog=21/21 i2c=4294967295/4294967295 btn=77722/77722
  i2c watchdog: watch=777 recoveries=0
  stack: used=1364/4096 headroom=2732
Printing trace buffer because: Diagnostics reboot.
ID: 2, EV: 67109381, Tag: staging_260803_v2
Uptime: 77723 ms, Last main: 2 ms ago
Trace:
>(l9)<F14><F10><i6><i6<U9>><i6><i6><F14><F14><i6><i6<U9>><i6><i6
><F10><F1>(l9)<F14><i6><i6<U9>><i6><i6><F14><F10><i6><i6<U9>><i6
><i6><F14><F1>(l9)<F14><i6><i6<U9>><i6><i6><F10><F14><i6><i6<U9>
><i6><i6><F14>(l6u1u2v3w0w1x1x2x3x4w2w3w4w5w6v

and

e3u7u8l7)(l6u1u2v1

It is also possible that it is simply caused by that messy algorithm that we chose for reading of that buffer.

Let me know if you want to get a new clean API.