Describe the bug
The moment tracing is disabled all collected info is lost.
Looks like the call to system:trace() returns an empty sequence after system:enable-tracing(false()).
Then it is a bug in exist-db itself.
Expected behavior
The tracing view to keep the collected information when tracing is disabled.
To Reproduce
Integration Test
For UI and browser based testing we use cypress.js
describe ( 'profiling' , function ( ) {
it ( 'should load Query Profiling' , function ( ) {
cy . visit ( '/apps/monex/profiling.html' )
. url ( ) . should ( 'include' , '/monex/profiling.html' )
. wait ( 1000 )
. get ( '[href="?action=enable"]' ) . click ( )
. get ( '[href="?action=refresh"]' ) . click ( )
. get ( '[href="?action=disable"]' ) . click ( )
cy . contains ( '/db/apps/monex/controller.xql' )
. url ( ) . should ( 'include' , 'profiling.html?action=disable' )
} )
} )
Screenshots
query-profiling-issue-recording.mov
Context (please always complete the following information):
OS: n/a
eXist-db Version: exist-7.0.0-SNAPSHOT
Java Version: Java 21
App Version: 4.2.2
Additional context
How is eXist-db installed? built from source
Any custom changes in e.g. conf.xml? none
Describe the bug
The moment tracing is disabled all collected info is lost.
Looks like the call to
system:trace()returns an empty sequence aftersystem:enable-tracing(false()).Then it is a bug in exist-db itself.
Expected behavior
The tracing view to keep the collected information when tracing is disabled.
To Reproduce
Integration Test
For UI and browser based testing we use cypress.js
Screenshots
query-profiling-issue-recording.mov
Context (please always complete the following information):
Additional context
conf.xml? none