Index Usage source string cut short

[bjornawo]

A long file path for the collection.xconf file causes the string to be cut short making it difficult to figure out what should be indexed.

[joewiz]

@bjornawo Could you please post a screenshot illustrating this? I'm having trouble figuring out where you're seeing this.

[bjornawo]

[joewiz]

@bjornawo I meant to ask: Could you confirm your version of eXist and monex?

I think I see the problem, even in the current releases of eXist 3.1.0 running monex 0.9.7: The app:truncate-source() function (see source) that is responsible for trimming the path here should be at least showing the filename, but it assumes the path separator is a forward slash /, but the paths in your screenshot show Windows filesystem paths, which use the backslash \. I'm curious, though, I would expect expath packages (as the path indicates are being run here) to resolve to the database, not to the filesystem. Do you know your system is referencing these modules in the expathrepo directory on the filesystem as opposed to the database? If not, we can investigate further.

[joewiz]

@bjornawo One more observation: The fact that some of the entries in the Source column show no path at all suggests to me that you're running an older, pre 0.9.6 version of monex when some fixes to path truncation were released. If a monex update is available to you via Dashboard > Package Manager, you might try the current release for some relief, though this won't fix the Windows path issue, where my observations/questions above still are valid.

[bjornawo]

@joewiz It seems like we are running an older version of eXist-db (2.2) with Monex version 0.7. The newer Monex versions will only generate a HTTP 400 bad request.

I will get back to you if I get the chance to test the path issues in Windows on a newer release.

[joewiz]

The current version of monex requires eXist 3.x. I would have thought eXist 2.2 would warn you when installing an incompatible version, but I guess not.

Good luck!

[line-o]

Can we close this issue?