[Bug 32057] New: Add optional stack trace to action logs
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Bug ID: 32057 Summary: Add optional stack trace to action logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs@lists.koha-community.org Reporter: kyle@bywatersolutions.com QA Contact: testopia@bugs.koha-community.org It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|koha-bugs@lists.koha-commun |kyle@bywatersolutions.com |ity.org | -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #1 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 142855 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142855&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #142855|0 |1 is obsolete| | --- Comment #2 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 142857 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=142857&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Small patch -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@davidnind.com Status|Needs Signoff |Patch doesn't apply --- Comment #3 from David Nind <david@davidnind.com> --- The patch no longer applies 8-(... Applying: Bug 32057: Add optional stack trace to action logs Using index info to reconstruct a base tree... M installer/data/mysql/kohastructure.sql M installer/data/mysql/mandatory/sysprefs.sql Falling back to patching base and 3-way merge... Auto-merging installer/data/mysql/mandatory/sysprefs.sql Auto-merging installer/data/mysql/kohastructure.sql CONFLICT (content): Merge conflict in installer/data/mysql/kohastructure.sql error: Failed to merge in the changes. Patch failed at 0001 Bug 32057: Add optional stack trace to action logs -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #142857|0 |1 is obsolete| | --- Comment #4 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144734 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144734&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144734|0 |1 is obsolete| | --- Comment #5 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144735 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144735&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #6 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144736 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144736&action=edit Bug 32057: Use replace insert query with use of Koha::ActionLogs -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144736|0 |1 is obsolete| | --- Comment #7 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144737 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144737&action=edit Bug 32057: Replace insert query with use of Koha::ActionLogs -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144737|0 |1 is obsolete| | --- Comment #8 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144738 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144738&action=edit Bug 32057: Replace insert query with use of Koha::ActionLogs -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Failed QA --- Comment #9 from David Nind <david@davidnind.com> --- After applying the patch, updating the database, and adding a value to ActionLogsTraceDepth, I am now unable to change system preferences. I tried with UseCaseRegisters and under Logs - enabling logging for an item that was currently disabled (such as IssueLog). I get an "Internal Server Error, please reload the page" in the staff interface. In the plack-error.log this is the start of the message: 291 DBIx::Class::Row::store_column(): No such column 'trace' on Koha::Schema::Result::ActionLog at /kohadevbox/koha/Koha/Object.pm line 79 292 at /usr/share/perl5/DBIx/Class/Exception.pm line 77 293 DBIx::Class::Exception::throw('DBIx::Class::Exception', 'No such column \'trace\' on Koha::Schema::Result::ActionLog') called at /usr/share/perl5/DBIx/Class/ResultSourc e.pm line 2380 294 DBIx::Class::ResultSource::throw_exception('DBIx::Class::ResultSource::Table=HASH(0x55a3fd102ef8)', 'No such column \'trace\' on Koha::Schema::Result::ActionLog') calle d at /usr/share/perl5/DBIx/Class/Row.pm line 1569 295 DBIx::Class::Row::throw_exception('Koha::Schema::Result::ActionLog=HASH(0x55a400de53c8)', 'No such column \'trace\' on Koha::Schema::Result::ActionLog') called at /usr/ share/perl5/DBIx/Class/Row.pm line 1215 296 DBIx::Class::Row::store_column('Koha::Schema::Result::ActionLog=HASH(0x55a400de53c8)', 'trace', '[^J {^J "package" : "Koha::Config::SysPref",^J "line" : 77, ^J "subroutine" : "C4::Log::logaction",^J "filename" : "/kohadevbox/koha/Koha/Config/SysPref.pm"^J },^J {^J "filename" : "/kohadevbox/koha/C4/Context.pm" ,^J "line" : 431,^J "subroutine" : "Koha::Config::SysPref::store",^J "package" : "C4::Context"^J },^J {^J "subroutine" : "C4::Context::set_preferenc e",^J "line" : 103,^J "package" : "CGI::Compile::ROOT::kohadevbox_koha_svc_config_systempreferences",^J "filename" : "/kohadevbox/koha/svc/config/systemprefe rences"^J }^J]^J') called at /usr/share/perl5/DBIx/Class/Row.pm line 270 -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Kyle M Hall <kyle@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #10 from Kyle M Hall <kyle@bywatersolutions.com> --- Created attachment 144769 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144769&action=edit Bug 32057: Update ActionLog schema file [DO NOT PUSH] -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144735|0 |1 is obsolete| | --- Comment #11 from David Nind <david@davidnind.com> --- Created attachment 144786 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144786&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144738|0 |1 is obsolete| | --- Comment #12 from David Nind <david@davidnind.com> --- Created attachment 144787 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144787&action=edit Bug 32057: Replace insert query with use of Koha::ActionLogs Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144769|0 |1 is obsolete| | --- Comment #13 from David Nind <david@davidnind.com> --- Created attachment 144788 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=144788&action=edit Bug 32057: Update ActionLog schema file [DO NOT PUSH] Signed-off-by: David Nind <david@davidnind.com> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the| |It can be useful to know release notes| |where in Koha a particular | |logged action was generated | |from, and how his | |enhancement adds stack | |traces to action logs. To | |use, add a number for the | |trace depth (such as 3) to | |the new system preference | |ActionLogsTraceDepth. The | |details for the stack trace | |are available by querying | |the database, for example: | |SELECT * FROM action_logs | |WHERE trace IS NOT NULL; --- Comment #14 from David Nind <david@davidnind.com> --- Thanks Kyle for fixing! I should have thought of running dbic! Now signed off. David -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 David Nind <david@davidnind.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the|It can be useful to know |It can be useful to know release notes|where in Koha a particular |where in Koha a logged |logged action was generated |action was generated from, |from, and how his |and how. This enhancement |enhancement adds stack |adds stack traces to action |traces to action logs. To |logs. To use, add a number |use, add a number for the |for the trace depth (such |trace depth (such as 3) to |as 3) to the new system |the new system preference |preference |ActionLogsTraceDepth. The |ActionLogsTraceDepth. The |details for the stack trace |details for the stack trace |are available by querying |are available by querying |the database, for example: |the database, for example: |SELECT * FROM action_logs |SELECT * FROM action_logs |WHERE trace IS NOT NULL; |WHERE trace IS NOT NULL; -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.de.rooy@rijksmuseum.nl --- Comment #15 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Did you think about using Devel::StackTrace / libdevel-stacktrace-perl ? -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- QA Contact|testopia@bugs.koha-communit |m.de.rooy@rijksmuseum.nl |y.org | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #16 from Kyle M Hall <kyle@bywatersolutions.com> --- (In reply to Marcel de Rooy from comment #15)
Did you think about using Devel::StackTrace / libdevel-stacktrace-perl ?
I did have a look at Devel::StackTrace when I started this bug. Simply put, using caller is the absolute fastest way to do what we need here. If there are other benefits to Devel::StackTrace I'm not aware of we could look into that on followup bugs! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144786|0 |1 is obsolete| | --- Comment #17 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 147152 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147152&action=edit Bug 32057: Add optional stack trace to action logs It can be useful to know where in Koha a particular logged action was generated from, and how. We should add the ability to attach a syspref controlled basic stack trace with the caller depth controlled via the syspref. We can the call caller() until the specified depth has been reached. Test Plan: 1) Apply this patch 2) Run updatedatabase.pl 4) Restart all the things! 5) Set the new syspref ActionLogsTraceDepth to a number ( e.g. 3 ) 6) Update a syspref or trigger another enabled log action 7) Query the database: SELECT * FROM action_logs WHERE trace IS NOT NULL 8) Note the stack trace was created! Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144787|0 |1 is obsolete| | --- Comment #18 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 147153 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147153&action=edit Bug 32057: Replace insert query with use of Koha::ActionLogs Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144788|0 |1 is obsolete| | --- Comment #19 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 147154 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147154&action=edit Bug 32057: Update ActionLog schema file [DO NOT PUSH] Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #20 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 147155 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147155&action=edit Bug 32057: (QA follow-up) Remove pretty flag Not needed for storage. You can always display pretty in the interface (on a follow-up report). Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #21 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 147156 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147156&action=edit Bug 32057: (QA follow-up) Add a simple test Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #22 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- A future report should add this field to the interface (log viewer). -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Pushed to master Version(s)| |23.05.00 released in| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #23 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Pushed to master for 23.05. Nice work everyone, thanks! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #24 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- Created attachment 148162 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=148162&action=edit Bug 32057: (follow-up) Add INSERT IGNORE in dbrev Preventing: ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Duplicate entry 'ActionLogsTraceDepth' for key 'PRIMARY' at /usr/share/koha/C4/Installer.pm line 739 Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl> -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |additional_work_needed -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 --- Comment #25 from Marcel de Rooy <m.de.rooy@rijksmuseum.nl> --- @RM: last trivial follow-up -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Marcel de Rooy <m.de.rooy@rijksmuseum.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomascohen@gmail.com -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Tomás Cohen Arazi <tomascohen@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|additional_work_needed | --- Comment #26 from Tomás Cohen Arazi <tomascohen@gmail.com> --- Thanks for the follow-up, Marcel. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Matt Blenkinsop <matt.blenkinsop@ptfs-europe.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to master |Needs documenting CC| |matt.blenkinsop@ptfs-europe | |.com --- Comment #27 from Matt Blenkinsop <matt.blenkinsop@ptfs-europe.com> --- Enhancement - not backporting to 22.11.x Nice work everyone! -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED CC| |caroline.cyr-la-rose@inlibr | |o.com Documentation| |https://gitlab.com/koha-com submission| |munity/koha-manual/-/merge_ | |requests/683 Documentation| |Caroline Cyr La Rose contact| | Status|Needs documenting |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32057 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Text to go in the|It can be useful to know |It can be useful to know release notes|where in Koha a logged |where in Koha a logged |action was generated from, |action was generated from, |and how. This enhancement |and how. This enhancement |adds stack traces to action |adds stack traces to action |logs. To use, add a number |logs. To use, add a number |for the trace depth (such |for the trace depth (such |as 3) to the new system |as 3) to the new system |preference |preference |ActionLogsTraceDepth. The |`ActionLogsTraceDepth`. The |details for the stack trace |details for the stack trace |are available by querying |are available by querying |the database, for example: |the database, for example: |SELECT * FROM action_logs | |WHERE trace IS NOT NULL; |`SELECT * FROM action_logs | |WHERE trace IS NOT NULL;` Component|Architecture, internals, |Reports |and plumbing | -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org