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
Better BibLaTeX exporter hangs on exporting progress screen without any file output #1180
Comments
You can also get a log by starting Zotero with |
@retorquere Is this log here helpful? https://gist.github.com/schmittlauch/09ec9c7f72d16c436b55351e7aec5e32 |
This is an existing auto-export that no longer updates, right? Not a new auto-export you're setting up? |
I see an error in the gist, but it's a Zotero error, not a BBT error. It's an |
(I can't reproduce it yet locally given the existing references you sent, those export cleanly with your settings) |
🤖 this is your friendly neighborhood build bot announcing test build 5.1.76.3934 ("don't log full translator") Install in Zotero by downloading test build 5.1.76.3934, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...". |
Ignore @blip-bloop for now. |
It used to be, then I deleted the .bib file to start from scratch, hoping this would fix it. Interestingly, even the built-in BibLaTeX exporter fails when exporting to the previously used bib file:
But exporting to another directory works fine with the built-in exporter. Could really be a Zotero bug |
Is there a possibility to list and/or cancel the existing file-auto-update subscriptions of Better BibTeX? Maybe there's an orphaned one lying around. |
I have a build coming up in 10 minutes or so that should help -- please don't remove the existing AE yet so that I can test this, but I think the problem is that inside Zotero, your export path looks like
which I'm guessing is not how it looks to you. |
You can see your existing AEs in the BBT preferences. |
Ah, nobody ever expected paths to be non-ASCII only :D |
I don't do anything that requires ASCII, I just record the path as it is given to me by Zotero -- unfortunately, unicode handling in javascript is a mess. It's encouraging that at least also standard BibTeX fails -- at least it's not a regression in BBT maybe. |
🤖 this is your friendly neighborhood build bot announcing test build 5.1.76.3937 ("Really weird that we should suddenly be getting unicode mangling") Install in Zotero by downloading test build 5.1.76.3937, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...". |
A little longer than 10 minutes, but try 3937. |
@retorquere After installing the test build, Zotero always asks me for a restart because of newly added translator modules. But that happens after each restart.
|
Odd, doesn't happen here. Please restart with debugging enabled, ignore the request to restart because new translators were installed, let BBT finish initializing (if it does), and send a new debug log. |
Ugh no wait. |
We're still at the usual (Zotero-internal?) exception: https://gist.github.com/schmittlauch/7a89ade4290fd7ffd4b07890fb0c82e0 |
🤖 this is your friendly neighborhood build bot announcing test build 5.1.76.3938 ("test installed as casted bool") Install in Zotero by downloading test build 5.1.76.3938, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...". |
Try 3938. |
The "please restart" loop is gone. But I still see an exception in the log and the export still hangs. https://gist.github.com/schmittlauch/ac7451d0b246ce04d572908040635a3a If you say that this is a Zotero-internal bug I can go and report it upstream. |
I can try again with some older Zotero versions |
If a regular save with the standard BibTeX translator has the same problem, then it does look like a Zotero problem. I thought it was located elsewhere where I could test for it beforehand but that wasn't it. If you can replicate it with a regular export, it would be helpful if you would report it to the Zotero forums directly. If that is the case, for BBT, you can in the interim just remove the auto-export and set it up to an ASCII path until that is resolved -- if this analysis holds, there's nothing I can do about it. If it doesn't occur with older Zotero versions that would be very good to know -- regressions always have their full attention. In case you're curious why the export hangs: translations happen asynchronously, so I can kick them off and must then wait to be notified that they're done (successfully or unsuccessfully). Unfortunately the translator inside Zotero errors out before it can do that, so any code that waits for that signal will wait forever. I could set a timeout, but the length of the timeout would be arbitrary (sometimes exports just take very long). The end-of-translation notifiers should just work, but the kind of error we see in this log are usually tricky to catch inside Firefox (which is still what Zotero is on the inside). |
Is this replicable with just the Zotero export? |
Yes, it was replicable with the Zotero export, but in the end turned out to be a distro packaging issue. Sorry about that. Thanks for your efforts. I already donated once and may do again later (= |
Thank you, and don't worry about it. I'd rather hear about problems that turn out to be non-problems than not hear about problems. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description: The Better BibLaTeX exporter does not produce a bibliography file anymore and hangs at the export progress screen infinitely.
The options used were "export notes" and "keep up to date".
This used to work before, and I discovered the issue by noticing that my bibliography file was not kept up to date anymore.
Report ID: GQGYUH5W-euc
Zotero version: 5.0.66
Better BibTeX version: 5.1.76
Exporter used: Better BibLaTeX with "export notes" and "keep up to date"
Expected behavior: The exporter creates a valid BibLaTeX file and finishes after some time.
Actual behavior: The exporter does not even create a file and hangs at the progress meter.
The Zotero debug log contains several JS exceptions and will be included in the next issue comment. As the progress screen blocked any interaction with the main Zotero window, I could only create a Better-BibTeX report before actually exporting anything.
The text was updated successfully, but these errors were encountered: