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

Stuck in "Exporting items" with 7.0.0-beta.71+03d0ea436 #2831

Closed
Sciroccogti opened this issue Apr 9, 2024 · 6 comments
Closed

Stuck in "Exporting items" with 7.0.0-beta.71+03d0ea436 #2831

Sciroccogti opened this issue Apr 9, 2024 · 6 comments

Comments

@Sciroccogti
Copy link

Debug log ID

D1678910747

What happened?

Debug log cannot be generated because the BBT debug log just wont popup. I think the new version is not supported yet.

Copy link

github-actions bot commented Apr 9, 2024

Hello there @Sciroccogti,

Hope you're doing well! @retorquere is here to help you get the most out of your experience with Better BibTeX. To make sure he can assist you effectively, he kindly asks for your cooperation in providing a debug log – it's like giving him the key to understanding and solving the puzzle!

Getting your debug log is a breeze and will save us both time in getting your problem resolved or the new feature you'd like implemented. Trust me, it's way quicker than discussing why it's important. 😃

How to Share Your Debug Log:

  1. If the issue involves specific references, citekey generation, or exports, just right-click on the relevant item(s) and choose "Better BibTeX -> Submit Better BibTeX debug log" from the menu.

  2. For other issues, follow these simple steps:

    • Restart Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled).
    • Reproduce the problem.
    • Select "Send Better BibTeX debug report..." from the help menu.

Once you hit that submit button, you'll get a special red debug ID. Just share that with @retorquere in this issue thread. If the question is regarding an export, don't forget to include what you see exported and what you expected.

By sharing your debug log, you're giving @retorquere a clearer picture of your setup and the items causing the issue. It's like a superhero cape for him – he can swoop in and tackle the problem much faster.

We totally get that your time is valuable, and we appreciate your effort in helping @retorquere help you. You might be surprised at how much this simple step speeds up the whole process.

Thanks a bunch!

PS: If the Debug Log menu does not appear, or it does not send the debug log

A fallback option is available under "Help" > "Send debug log to file.io".

@GYukai
Copy link

GYukai commented Apr 9, 2024

Same here

@retorquere
Copy link
Owner

See #2829

@retorquere
Copy link
Owner

Please subscribe to #2829 if you want to track progress

@Sciroccogti
Copy link
Author

Right, it seems to be the same problem.
Luckily Linux version works fine so far.

@retorquere
Copy link
Owner

If it had broken on Linux I would have known sooner, because my test suite runs on linux.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants