Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Bug]: Fixed position values get cleared upon nodedb reset #3929

Closed
prokrypt opened this issue May 18, 2024 · 3 comments
Closed

[Bug]: Fixed position values get cleared upon nodedb reset #3929

prokrypt opened this issue May 18, 2024 · 3 comments
Labels
expected behavior This behavior is expected. wontfix This will not be worked on

Comments

@prokrypt
Copy link
Contributor

Category

Other

Hardware

Not Applicable

Firmware Version

2.3.x

Description

From meshtastic/Meshtastic-Android#1044

Relevant log output

No response
@prokrypt prokrypt added the bug Something isn't working label May 18, 2024
@prokrypt prokrypt changed the title [Bug]: Fixed position gets reset upon nodedb reset [Bug]: Fixed position gets cleared upon nodedb reset May 18, 2024
@prokrypt prokrypt changed the title [Bug]: Fixed position gets cleared upon nodedb reset [Bug]: Fixed position values gets cleared upon nodedb reset May 18, 2024
@prokrypt prokrypt changed the title [Bug]: Fixed position values gets cleared upon nodedb reset [Bug]: Fixed position values get cleared upon nodedb reset May 18, 2024
@caveman99 caveman99 added wontfix This will not be worked on expected behavior This behavior is expected. and removed bug Something isn't working labels May 18, 2024
@caveman99
Copy link
Member

This is not just intended behaviour but also intentional behaviour and will not be changed. If this is not documented, documentation needs to be added.

@caveman99 caveman99 closed this as not planned Won't fix, can't repro, duplicate, stale May 18, 2024
@caveman99
Copy link
Member

ref: #3451

@nicheath
Copy link

Is there an explanation why this is desired to be this way? I came here to report it because it was not what I was expecting at all. Discovered nodes (dynamic data) vs my node's configured position (configuration static data) seem like two different things.

@nicheath nicheath mentioned this issue Sep 11, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
expected behavior This behavior is expected. wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@caveman99 @nicheath @prokrypt