14-07-2018, 06:20 PM
Colin
I don't like there being faulty code out there so I need to find the reason. I have used an earlier version for well over an hour at a time without any fall-over so maybe it somehow relates to the new view option. How, I am not sure as it doesn't use a list that way except when sorting the reports.
Thanks for the direct email with the files attached. I have looked at them with a text editor and they are all relatively normal. Creating and working with pure text files makes that error check quite easy !!
Another thought does cross my mind though and that is the low number of reports of your transmissions (like one ) when it keeled over. Maybe it is not the upper 300 limit that is reached but rather it is seeing just one and treating it as zero - or having a nominal zero and thinking it is -1 - and that last state is a definite List out of bounds error. Have seen that one a few times during its early development.
My reception report counts are towards the 300 upper limit as I am often beaming Europe long path or short path to USA on 20m, plus getting many South-East Asia & Japanese hits coming back via PSKRepView. Obviously I need to try it with minimal reports to emulate yours.
I might wait a bit for any other bug reports before I push out another version as they will (hopefully) reveal whether the problem appears at either the low or high reports count numbers.
My weekend is shot doing fencing for my daughter so won't be back on FT8 until during the week, so no opportunity to test it here until at least then.
Doug
I don't like there being faulty code out there so I need to find the reason. I have used an earlier version for well over an hour at a time without any fall-over so maybe it somehow relates to the new view option. How, I am not sure as it doesn't use a list that way except when sorting the reports.
Thanks for the direct email with the files attached. I have looked at them with a text editor and they are all relatively normal. Creating and working with pure text files makes that error check quite easy !!
Another thought does cross my mind though and that is the low number of reports of your transmissions (like one ) when it keeled over. Maybe it is not the upper 300 limit that is reached but rather it is seeing just one and treating it as zero - or having a nominal zero and thinking it is -1 - and that last state is a definite List out of bounds error. Have seen that one a few times during its early development.
My reception report counts are towards the 300 upper limit as I am often beaming Europe long path or short path to USA on 20m, plus getting many South-East Asia & Japanese hits coming back via PSKRepView. Obviously I need to try it with minimal reports to emulate yours.
I might wait a bit for any other bug reports before I push out another version as they will (hopefully) reveal whether the problem appears at either the low or high reports count numbers.
My weekend is shot doing fencing for my daughter so won't be back on FT8 until during the week, so no opportunity to test it here until at least then.
Doug
Doug VK4ADC @ QG62LG51
http://www.vk4adc.com
This Forum is only going to be as interesting as the posts it contains.
If you have a comment or question, post it as it may trigger or answer the query in someone else's mind.
http://www.vk4adc.com
This Forum is only going to be as interesting as the posts it contains.
If you have a comment or question, post it as it may trigger or answer the query in someone else's mind.