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
Version 4.17.0 + fail #557
Comments
Thank you very much for the report! |
Is this with a simple layout? Which version of Windows are you using? I have tried Windows 10 on an Intel chip and created a new small layout (sp new hw) and successfully created a PDF. |
I am running the standard version 4.17.4 Running a simple layout works, but running a more complex layout fails. But I cannot debug what exactly from the more complex layout breaks the publishing as the error messages don't say anything related to the layouts. |
I assume that the XML file is “too big” for the memory. I'll test it and create a work around... |
(Sorry for spamming you). I assume that the error also happens when you use 4.16 and |
Hi, Tried: then tried so the issue is with the XPath parser. I see the new XPath parser lxpath is supposed to be better. |
There are currently no difference in the layout or xpath functions. The XPath expressions can now access parent nodes ( I hoped that there is no migration necessary, everything should work out of the box. I'll provide a workaround to save the XML that is currently held in memory to an intermediate file. This might help with the out of memory error. |
Version 4.17.5 has a new option (still experimental, undocumented):
or in
Which writes the internal representation of the XML data to intermediate files and skips passing big strings. This might be a workaround for using the default lxpath XPath parser. |
This option makes the XML parser (lxpath) to write the Lua table to a file instead of passing a string. This is related to #557
(now online at https://download.speedata.de) |
Hi, I tried sp 4.17.7 with --option xmlfile=true It still failed, but now I have this error in the publisher.log file:
|
This looks much better. But unfortunately impossible to track down without layout or data. If you think you can send a copy.. The contact data is at https://www.speedata.de/imprint/ |
Hi, First error message was regarding a setvariable. It was on the 61 setvariable from 67 so I found it was this: Not sure why I was setting it to none, but this was working with luxor. After changing none to 0 and re-running the publishing, it never finishes.
Also in the protocol the last line is not finished, as below:
|
Still hard to debug. lxpath is more strict than the old parser but there can be errors of course. I feel your pain but currently I cannot do very much. |
I think you should stay with the luxor xpath parser, it won't go away. Just set it to default in your project. For new projects I'd recommend keeping the new default (lxpath) and complain when errors occur. |
Just in case you are still interested: the version 4.17.10 has a new implementation of the lxpath parser which should use much less memory while parsing XML files. Since I was not able to reproduce the problem, I don't know if this influences the problem. |
sorry for not elaborating this further (right now, I will do it as soon as I have time to investigate this). I have an error code 1 just by compiling a script (that I use to extract images from other files) with version 4.17.19 instead of version 4.17.0. That being said, if error code is 1, do you want a new issue reporting what triggers the error or do I report it in this already opened report? (Sorry for the confusion, but I think that part of it comes from not considering that issues are what people experience and reports are what GitHub calls [and numbers as] issues.) |
This issue is okay. |
I get this error message:
If this is a missing file/dependency, I wonder whether you need the sample code that might trigger this. Many thanks for your help. |
I can reproduce the problem, thank you very much for the report. I am not sure how fast I can fix it, but I give my very best... |
Fine for me. I cannot use the newest version, so I stick to 4.17.0. |
Many thanks for your help. |
I also want to close this issue. Don't hesitate to open a new one if you still see errors. |
Hi,
All sp versions after 4.16.0 are failing with errors.
Version 4.16.0 works
Starting with 4.17.0 all are failing with below errors:
I mention, I am running the Windows version.
<Status><Error code="1">Error executing sdluatex (bin\sdluatex.exe)</Error><Errors>1</Errors></Status>
in terminal I get below errors:
The text was updated successfully, but these errors were encountered: