Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

calling a non-existent templating function no longer(?) reports error #33

Closed
ghost opened this issue Aug 8, 2018 · 3 comments · Fixed by #34
Closed

calling a non-existent templating function no longer(?) reports error #33

ghost opened this issue Aug 8, 2018 · 3 comments · Fixed by #34
Labels

Comments

@ghost
Copy link

ghost commented Aug 8, 2018

@merenyics commented on Jul 20, 2018, 3:56 PM UTC:

What is the problem

If I remember correctly, prior to version 4.3 calling a templating function like this
<div class="some:function"/>
resulted in an error being thrown immediately, indicating that the given function does not exist. Right now, using 4.3, the server does not respond within a reasonable amount of time, I can see in Monex that a query is running (view.xql) but it won't return, I need to kill it manually.

What did you expect

I expected to get the error message I used to get, instead of the query hanging

Describe how to reproduce or add a test

Just try calling a non-existent function using templating

Context information

Please always add the following information

  • eXist-db version 4.3
  • Java version Java8u161
  • Operating system Windows 10
  • 64 bit
  • How is eXist-db installed? (JAR installer)
  • no custom changes

This issue was moved by joewiz from eXist-db/exist#2050.

@ghost
Copy link
Author

ghost commented Aug 8, 2018

@adamretter commented on Jul 20, 2018, 5:30 PM UTC:

wolfgangmm I wonder if this is that infinite issue I pointed out to you - where it tries to call a function with 1 parameter, then 2, then 3 and then so on and so on...

@ghost
Copy link
Author

ghost commented Aug 8, 2018

@windauer commented on Aug 1, 2018, 3:24 PM UTC:

I exerienced the same issue and can confirm this!

@joewiz
Copy link
Member

joewiz commented Aug 8, 2018

@merenyics I've filed a PR that fixes the problem in my testing: #34. Please feel free to test the fix and let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant