Typo in PR 371

[Orv]

IS:

blocked - latency: the link latency is to high to reliably pass data.

SHOULD BE:

blocked - latency: the link latency is too high to reliably pass data.

[ab7pa]

I'm looking but just not seeing it... can you identify the line number? THX

• pending: LQM is collecting data and evaluating the link.
• active: the link is viable and can be used.
• idle: the link is usable and would be active but the node routing table does not yet have a route for sending traffic across the link.
• blocked: the link is unusable and is blocked from use.
• blocked - distance: the remote node is either too close or too distant, based on the LQM Min and Max Distance settings.
• blocked - signal: the SNR on the link is too low to reliably pass data, based on the LQM Min SNR setting.
• blocked - retries: the retransmission rate is too high to reliably pass data.
• blocked - latency: the link latency is too high to reliably pass data.
• blocked - dtd: LQM blocks the RF interface of any nodes to which a DtD link also exists.
• blocked - dup: LQM blocks a link in cases when your node has an RF link to other nodes which themselves connect to each other via DtD. This can occur when there are multiple radios at a site using the same channel. The best remote node is chosen as the RF link for your node but the other possible RF connections are blocked as duplicates.
• blocked - user: LQM blocks any node which you enter in the User Blocked Nodes field in the Advanced Configuration section.
• disconnected: the RF Neighbor is no longer online.

[Orv]

It's line 83, but in your example, there it's been fixed. This is what I'm seeing:

blocked - latency: the link latency is to high to reliably pass data.

[ab7pa]

Here is line 83 as I'm seeing it. I think in the future it would be easier to troubleshoot and fix things if you would consider making your comment directly on the PR rather than opening a separate issue. In the PR you can comment on the exact line of code where the problem occurs.

[Orv]

Roger Wilco