changing debug setting purges the debugging logs

Description

change the debugging settings, purges the debugging logs

 

image-20240729-142906.png

Environment

None

Attachments

2
  • 26 Aug 2024, 02:32 pm
  • 29 Jul 2024, 02:29 pm

Activity

Show:

Michael Offner 26 August 2024 at 14:32

you can manually purge the logs already

 

Screenshot 2024-08-26 at 16.31.32.png

Zac Spitzer 30 July 2024 at 11:39

this is left over behaviour from when we had a debugging enabled flag, turning off debugging would clear the logs out of memory

if (!Caster.toBooleanValue(getString("debug", ""), false)) doPurgeDebugPool(); // purge the debug log pool when disabling debug to free up memory

https://github.com/lucee/Lucee/blob/6.2/core/src/main/java/lucee/runtime/tag/Admin.java#L1778

I guess this needs to be updated to either allow manually purging via the logs view in the admin, or keeping this behaviour and checking if any debugging is enabled.

I think in some ways, the manual purge is better, that way you can enable debugging briefly, grab some logs and then then turn off debugging to investigate them?

Fixed

Details

Assignee

Reporter

Priority

Fix versions

New Issue warning screen

Before you create a new Issue, please post to the mailing list first https://dev.lucee.org

Once the issue has been verified, one of the Lucee team will ask you to file an issue

Sprint

Created 29 July 2024 at 14:28
Updated 30 August 2024 at 06:51
Resolved 26 August 2024 at 14:35

Flag notifications