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.

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

Errors in Analysis Results #1483

Open
sww326 opened this issue Jul 29, 2024 · 5 comments
Open

Errors in Analysis Results #1483

sww326 opened this issue Jul 29, 2024 · 5 comments
Labels
bug server Things that likely require server access for deployment

Comments

@sww326
Copy link

sww326 commented Jul 29, 2024

I reviewed the "Analyze" data for my flight log today and found two errors. First, under "Journey records,"my past flight between CLE-PBI is calculated at "0 miles, 00:30" and thus became my shortest flight.

Also, the Airport Records section is blank.

Screenshot 2024-07-29 132805

@reedy
Copy link
Collaborator

reedy commented Aug 19, 2024

The airport records is possibly from 2decb1d or 7d10661

The shortest being 0 miles... Mine actually is a zero mile flight, so shows correctly...

If you edit the flight, is the distance correct? Can you remove the src/dst and re-add them to force it to recalculate?

@reedy reedy added the bug label Aug 19, 2024
@reedy
Copy link
Collaborator

reedy commented Aug 20, 2024

Hmm. The airport analyse part works fine locally on my dev install...

@reedy
Copy link
Collaborator

reedy commented Aug 20, 2024

image

@reedy reedy added the server Things that likely require server access for deployment label Aug 20, 2024
@sww326
Copy link
Author

sww326 commented Aug 20, 2024

If you edit the flight, is the distance correct? Can you remove the src/dst and re-add them to force it to recalculate?

That worked. Doesn't explain how the error occurred in the first place (I haven't edited that effected segment since I first entered it years ago), but it resolved the issue for me.

@reedy
Copy link
Collaborator

reedy commented Aug 20, 2024

Hard to say exactly.

Depending on how long ago, could've been some calculation bug at point of insert. Or some corruption since.

If it's not replicable, or seemingly widespread, not much can easily be done to try and find out.

Glad that part is fixed at least!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug server Things that likely require server access for deployment
Projects
None yet
Development

No branches or pull requests

2 participants