Boris Zbarsky

@RudyGOGOGO Sorry, I have no idea about the build system bits here, just who might know....

"contains" as currently implemented really only works for lists of integer values.

I can fix `contains` to work for structs, but it won't help here, because readEvent does not return a list....

In particular, we should probably do a path-specific status for whatever path it was that did not fit in the packet.

RESOURCE_EXHAUSTED seems like a good status to use here.

Proxies are out of scope for 1.0.

@rwells1703 which exact SHAs are you using for chip-tool and the lighting app? Please include this info in general in future issues; it makes log analysis much easier. #### Attempt...

> Is it likely that chip-tool is sending its trying to initiate the CASE handshake over this link-local IP Fwiw, no. Per logs it was using `2a00:23a8:89b:da01:45b2:6372:b224:91e5`. I don't know...

I suspect people will want to know more information about the network (e.g. which router is being used), by the way.

@HubertHugo In particular, it looks like commissioning discovery found the wrong thing for that second chip-tool pairing command, but since that command said "find me anything on the network at...