-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
NoneType error when finding aircrafts #24
Comments
it shouldn't be crashing, it should just ignore the bad data. if you're
seeing it crash, can you send me the stack trace?
…On Wed, Feb 15, 2023 at 6:01 PM gncnpk ***@***.***> wrote:
It seems ADSBCOT crashes when a aircraft is missing any one piece of
information (id, lat, long, etc). My question is how should this be
handled? Should it be logged and the program continues or if the piece of
information isn't critical (lat, long I would consider the critical part),
should it just not provide that information? My current workaround is
having a try and except check in classes.py on line 255 and it just
ignores any aircraft missing a certain piece of information.
—
Reply to this email directly, view it on GitHub
<#24>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAWIXUAQKV64AS3ZFJYDD3WXWDBHANCNFSM6AAAAAAU5SD4GI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Greg Albrecht ***@***.***> W2GMD
EMT & ICT Specialist
Signal: +1-310-621-9598
https://ampledata.org/ <http://ampledata.org/>
https://github.com/ampledata
|
@ampledata Sure can do! Once I get off work, I'll remove my try and except catch, and get you the trace back :) |
|
What ADS-B source are you using? (mind sharing your config.ini?) |
Sure! I'm using
|
So I saw your message in Discord and I'll probably be switching over to the JSON feed instead, but I still would like to help fix this potential bug or if it's not a bug, help others find the solution :) |
Hey @gncnpk, if you're running locally, I recommend switching to the new |
It seems ADSBCOT crashes when a aircraft is missing any one piece of information (id, lat, long, etc). My question is how should this be handled? Should it be logged and the program continues or if the piece of information isn't critical (lat, long I would consider the critical part), should it just not provide that information? My current workaround is having a
try
andexcept
check inclasses.py
on line255
and it just ignores any aircraft missing a certain piece of information.The text was updated successfully, but these errors were encountered: