Simon Lin

@abtink Per my experience, it happens quite often recently. e.g. https://github.com/openthread/openthread/pull/5910/checks?check_run_id=1515464577 It's interesting that this fail can only be resolved after a fresh rebuild.

This should be an RA processing bug at the systemd-networkd side since `otbr-agent` works well with `dhcpcd`. There have been similar bug reports (e.g. https://github.com/coreos/bugs/issues/1478#issuecomment-234772765)

Seems systemd-networkd failed to handle RIO in the RA advertised by otbr-agent, because kernel refused to add the route with a local gateway address. systemd-networkd should ignore RIO sent by...

I doubt if there is an issue that needs to be fixed by https://github.com/openthread/openthread/pull/7996. What is the re-registration delay in BBR dataset. This could be caused by improper reregistration delay,...

> This PR mainly fixes some issues on current tests of OTBR-REST, and makes some preparations for #532 . > > * set timeout for rest-test in case it takes...

Labelled as P2 since #532 depends on this.

> The too many logs issue is due to a bug of otbr with latest openthread, see the fail https://github.com/openthread/ot-br-posix/pull/594/checks?check_run_id=1290402004 in @simonlingoogle 's new PR. Yes. It's not an issue...

Not being an expert on `cmake`, what happens when we build with `-DOTBR_VERSION=1.0` and then without specifying `-DOTBR_VERSION`? @suveshpratapa

> * After my change, it re-evaluates the version the proper way that it would if one didn't provide a version (so includes git information etc.) IIUC, that's true only...

> > > * After my change, it re-evaluates the version the proper way that it would if one didn't provide a version (so includes git information etc.) > >...