First thing I'd do is try to run the code on different hardware.
Second thing I'd do is try to run the code where BaseX is installed against the OpenJDK, rather than Oracle.
Third thing -- assuming those first two give you the same results, and it's not an issue with your hardware or the somewhat aged Oracle Java -- is to boil your code+data down to a minimum example that replicates the error, and send that to the nice folks at BaseX.
On Thu, Jul 29, 2021 at 1:58 PM Jonathan Robie jonathan.robie@gmail.com wrote:
Any ideas what this might mean? What should I do?
Jonathan
How can we reproduce this?
On Thu, Jul 29, 2021 at 7:59 PM Jonathan Robie jonathan.robie@gmail.com wrote:
Any ideas what this might mean? What should I do?
Jonathan
The easiest way might be to make someone from BaseX a member of a private GitHub repo that has queries, .bxs files, and datasets.
The behavior seems to vary depending on the indexes that have been defined.
Jonathan
On Thu, Jul 29, 2021 at 2:12 PM Christian Grün christian.gruen@gmail.com wrote:
How can we reproduce this?
On Thu, Jul 29, 2021 at 7:59 PM Jonathan Robie jonathan.robie@gmail.com wrote:
Any ideas what this might mean? What should I do?
Jonathan
Maybe you could try to find out how the behavior can be triggered from scratch; I’ll then be happy to look at it.
On Thu, Jul 29, 2021 at 9:27 PM Jonathan Robie jonathan.robie@gmail.com wrote:
The easiest way might be to make someone from BaseX a member of a private GitHub repo that has queries, .bxs files, and datasets.
The behavior seems to vary depending on the indexes that have been defined.
Jonathan
On Thu, Jul 29, 2021 at 2:12 PM Christian Grün christian.gruen@gmail.com wrote:
How can we reproduce this?
On Thu, Jul 29, 2021 at 7:59 PM Jonathan Robie jonathan.robie@gmail.com wrote:
Any ideas what this might mean? What should I do?
Jonathan
I remember seeing similar stacktraces with an old BaseX version. Could even have been 9.1. I would inspect[1] the database and run against latest version /Andy
[1] .https://docs.basex.org/wiki/Commands#INSPECT
On Thu, 29 Jul 2021 at 20:54, Christian Grün christian.gruen@gmail.com wrote:
Maybe you could try to find out how the behavior can be triggered from scratch; I’ll then be happy to look at it.
On Thu, Jul 29, 2021 at 9:27 PM Jonathan Robie jonathan.robie@gmail.com wrote:
The easiest way might be to make someone from BaseX a member of a
private GitHub repo that has queries, .bxs files, and datasets.
The behavior seems to vary depending on the indexes that have been
defined.
Jonathan
On Thu, Jul 29, 2021 at 2:12 PM Christian Grün <
christian.gruen@gmail.com> wrote:
How can we reproduce this?
On Thu, Jul 29, 2021 at 7:59 PM Jonathan Robie <
jonathan.robie@gmail.com> wrote:
Any ideas what this might mean? What should I do?
Jonathan
Let me try to just program around it ... I think there are better ways to do what this query does. And I don't know that I can reproduce this without a rather large dataset that I am using.
Jonathan
On Thu, Jul 29, 2021 at 3:53 PM Christian Grün christian.gruen@gmail.com wrote:
Maybe you could try to find out how the behavior can be triggered from scratch; I’ll then be happy to look at it.
On Thu, Jul 29, 2021 at 9:27 PM Jonathan Robie jonathan.robie@gmail.com wrote:
The easiest way might be to make someone from BaseX a member of a
private GitHub repo that has queries, .bxs files, and datasets.
The behavior seems to vary depending on the indexes that have been
defined.
Jonathan
On Thu, Jul 29, 2021 at 2:12 PM Christian Grün <
christian.gruen@gmail.com> wrote:
How can we reproduce this?
On Thu, Jul 29, 2021 at 7:59 PM Jonathan Robie <
jonathan.robie@gmail.com> wrote:
Any ideas what this might mean? What should I do?
Jonathan
basex-talk@mailman.uni-konstanz.de
-
Andy Bunce -
Christian Grün -
Graydon Saunders -
Jonathan Robie