Re: [SPAM] Re: 2024.1.6 rc2
Rhys Ackerman <[email protected]> Sat, 13 Jun 2026 18:32:11 +0100
| Newsgroups | gmane.games.flightgear.devel |
|---|---|
| Message-ID | <CAH1fkitMsfhxuygWRUnjG+tRd4w9coF8M8kGLbUb8iR1o3zo8A@mail.gmail.com> |
TLDR: More stuff is logged using a new method. Running the Sentry SDK in Debug mode shows this happening live in your console, but because not as much was logged before and was done so in a different way, you just never saw it. I have checked on Sentry with your UUID that you sent me, and indeed, it seems that yours has been running as a Dev build for quite some time. 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. There will have to be some sort of change with 2024.1.7 as we are struggling to handle the amount of logging right now, but exactly how much we will log or discard is yet to be worked out. There's some very valuable stuff coming to us from both a development/debug point of view, and also analytical, and once we iron out the teething troubles, I will be looking into ways we can present some of this data to users in an easy to read way. If you enable debug level logging in FG, you will actually see those same lines logged in your fgfs.log by FG. But by default they are not shown as they are too low of a priority message to show with the default logging level of Info. Hopefully that helps clear it up a little for you On Sat, 13 Jun 2026, 15:33 Josh Davidson, <[email protected]> wrote: > Why was this never a problem before now though? > > It looks like for some reason it was always building as a dev build but I > never got sentry spamming the log > > -- > Josh Davidson > ------------------------------ > > _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel