Re: [SPAM] Re: 2024.1.6 rc2

James Turner <[email protected]> Mon, 15 Jun 2026 22:52:54 +0100
Newsgroups gmane.games.flightgear.devel
Message-ID <[email protected]>

> On 13 Jun 2026, at 18:32, Rhys Ackerman <[email protected]> wrote:
> 
> 2024.1.6 brought some changes to what is logged and how. Unfortunately, there was a slight oversight which is resulting in everything you see in your fgfs.log, plus more, being logged, and you are seeing that happen live because Sentry is in Debug mode and therefore repeating what it is logging essentially. For a bit of context for those interested, in the last 14 days we have received 679 million logs. 75% of these are categorised as debug, which for the most part are just noise such as `Took 0ms to update layer WXR` or `setting listener #611 in C:/Users/*****/FlightGear/Downloads/fgdata_2024_1/Nasal/canvas/tooltip.nas:109`, but still count towards our quota. And these numbers have been reached with only approximately 50% of users who have Sentry enabled and are using 2024.1.6 (or nightlies), which is the first version to use the new logging system.

To explain a bit more, we previously manually collect logs and recorded them *when an error occurred*, and I *intended* to replicate the same, but using the Sentry system designed for exactly that purpose. Unfortunately it seems to actually just log *all* the time, which is not what we really want, for a lot of reasons. So we will do a 2024.1.7 ‘soon’ that does a revert, and then going forward we will figure out how to use the logging API, but at a more sane granularity.

(The dedicated logging API is much better, eg you can search log messages, but again we only want to record high severity messages, and the messages immediately preceding an exception / error / crash)

Kind regards,
James

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel