-
Notifications
You must be signed in to change notification settings - Fork 25
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
Candidates response fails on _dict_cleanup #3
Comments
May I ask which version if spotlight you are running? |
Of course you may :-)! Locally I'm fairly certain the version is 0.6.5 and at http://spotlight.sztaki.hu:2222 it should also be 0.6.5. The responses from my local server and the sztaki.hu server are the same. Doesn't the issue reproduce with your server? |
Haha no, or at least it was not above our notification threshold oops. I have a fix which I'm pushing in the next 15 minutes. That happens because in |
That's great, I'll try it right away! |
So that should be fixed now! Would not have been that fast if you would not have supplied the raw curl response :) Thanks for that. Hope it works? Waiting for your confirmation! |
It works like a charm =)! Many thanks for your fast (and late-night) bugfix; I wasn't expecting that! |
Glad to hear that! Well, I'm recovering a RAID5, so if you encounter any other error tonight, chances are high that I'll be awake and able to fix it ;-) Have fun with spotlight! |
Hey,
Thanks for writing this nice wrapper. It makes Spotlight calls a lot more convenient!
I'm running into a problem with the candidates response, seemingly only when exactly two candidate URIs are found for a surface form.
With curl:
I'm not entirely sure what the conditions are under which _dict_cleanup() fails, but I have only found examples with exactly two candidate URIs. If needed, I can provide you with some more examples.
Any idea what is causing this hiccup?
Cheers,
Alex
The text was updated successfully, but these errors were encountered: