Adam Retter

Just to make it explicit. There are two tests in @Twilight-Shuxin's report. Only one of them fails, `t:test-db#0`, the other `t:test-mem#0` (which uses the in-memory DOM as opposed to the...

It was closed by mistake.

@amclark42 I think you said that you are using v6.2.0 of eXist-db. If that is the case, then the fix I made (https://github.com/eXist-db/exist/pull/4662) that @line-o suggested is already present in...

The jstack can tell us why a deadlock occurred, but unfortunately it is not enough to tell us where the deadlock occurred. The where is important to understand your specific...

I am afraid that there is nothing in the information that you provided that indicates why eXist-db crashed.

@line-o For an example take a look at `PackageTriggerTest`

Related to: https://github.com/eXist-db/exist/issues/3820 Related to: https://github.com/eXist-db/exist/issues/4517 Related to: https://github.com/eXist-db/exist/issues/4242

There are some things in the `conf.xml` that should not be visible apart to anyone apart from `dba` so we should probably consider the security implications of how that would...

That's very interesting! So this happens when trying to rewrite the query to replace a Location Step with a function which performs a Range Index comparison. So the only way...

> I have tried to reproduce this issue in eXist-db 6.2.0, however I am not seeing any NPE. @marmoure So the PR (https://github.com/eXist-db/exist/pull/3625) that @dizzzz sent and was merged (see...