I don't know what kind of issue this is, so I do not open the "Bug" category -- please see and decide what it is.
I configured my "rooftop" repeater to send own adverts with two byte path hash.
After doing so and manually issuing a flood advert, the repeater's icon on the map has changed to show three byte ID.
When I tell the repeater to send a zero-hop advert, the map icon returns to 1 byte ID.
Regards!
I don't know what kind of issue this is, so I do not open the "Bug" category -- please see and decide what it is.
I configured my "rooftop" repeater to send own adverts with two byte path hash.
After doing so and manually issuing a flood advert, the repeater's icon on the map has changed to show three byte ID.
When I tell the repeater to send a zero-hop advert, the map icon returns to 1 byte ID.
Regards!
<!-- github-sync-id:4361387032 -->
Sure, this was a Bug, and therefor here my update!
Fixed (v0.9.12.1(
Map / advert path cache: receiving a zero-hop advert from a repeater no longer resets its map icon to a 1-byte ID. A zero-hop packet carries no hash-size information; the cached path_len (and therefore the hash badge) is now preserved whenever the existing entry already has hop info, in both the raw-RX and the decoded-advert update paths (#242).
Sure, this was a Bug, and therefor here my update!
### Fixed (v0.9.12.1(
- Map / advert path cache: receiving a zero-hop advert from a repeater no longer resets its map icon to a 1-byte ID. A zero-hop packet carries no hash-size information; the cached `path_len` (and therefore the hash badge) is now preserved whenever the existing entry already has hop info, in both the raw-RX and the decoded-advert update paths (#242).
<!-- github-comment-id:4406973077 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I don't know what kind of issue this is, so I do not open the "Bug" category -- please see and decide what it is.
I configured my "rooftop" repeater to send own adverts with two byte path hash.
After doing so and manually issuing a flood advert, the repeater's icon on the map has changed to show three byte ID.
When I tell the repeater to send a zero-hop advert, the map icon returns to 1 byte ID.
Regards!
Sure, this was a Bug, and therefor here my update!
Fixed (v0.9.12.1(
path_len(and therefore the hash badge) is now preserved whenever the existing entry already has hop info, in both the raw-RX and the decoded-advert update paths (#242).