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

Assigning citation keys every time zotero is open #2797

Closed
stefabat opened this issue Feb 27, 2024 · 29 comments
Closed

Assigning citation keys every time zotero is open #2797

stefabat opened this issue Feb 27, 2024 · 29 comments

Comments

@stefabat
Copy link

Debug log ID

92XXXWL2-euc/6.7.162-6

What happened?

Every time I open zotero, betterbibtex (re)assigns the citation keys. I have a pretty big library (1000+ items), so this behavior is annoying.

@retorquere
Copy link
Owner

There's nothing in that log. Please go to the Help menu, choose Debug Output Logging and Restart with logging enabled, let Zotero restart and BBT resolve the keys, then send a new debug log.

@stefabat
Copy link
Author

Sorry for that, the new debug log is L55E5APF-euc/6.7.162-6

@retorquere
Copy link
Owner

retorquere commented Feb 27, 2024

Can you disable the scite plugin (and restart) to see if that makes a difference? I see that scite is firing off 1617 item changes in L55E5APF-euc, BBT might be reacting to those.

@retorquere
Copy link
Owner

without further feedback I'm going to have to close this issue.

@stefabat
Copy link
Author

stefabat commented Mar 1, 2024

Hi, sorry for the late reply, very busy days.

The same happens even if I disable the scite plugin. The debug log for that is: MURF2VPZ-euc/6.7.163-6

What is strange is that I have another pc that has a very similar setup, and I don't see this problem. There, I also have scite enabled, and even more plugins enabled. I submitted a debug log also for that one, which is: UT3QE65G-euc/6.7.163-6

Thanks for looking into this! Very much appreciated!

@retorquere
Copy link
Owner

I don't see any non-startup BBT activity in the log. Can you go into preferences, advanced, config editor, accept, search for LogEvents, double-click it to set it to true, and send a new log?

@stefabat
Copy link
Author

stefabat commented Mar 1, 2024

It was already set to true. Maybe is there a way to completely delete the configs of both zotero and betterbibtex, and I can try to redo a fresh install?

Also, I am using the same setup on three computers, so maybe if the settings do not match on all three exactly, in some of them they trigger this reassignment of keys?

@stefabat
Copy link
Author

stefabat commented Mar 1, 2024

I have now mirrored the settings of my laptop to the computer on which don't have this problem, but the problem remains on the laptop (even disabling all other extensions, and reinstalling the betterbibtex extension from a freshly downloaded xpi file.

Copy link

github-actions bot commented Mar 1, 2024

🤖 this is your friendly neighborhood build bot announcing test build 6.7.163.2797.5889 ("add logging")

This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.163.2797.5889, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

@retorquere
Copy link
Owner

Reinstalling won't make a difference, that just removes the code, not the data it acts on. I see no activity in the previous log, can you try this build and generate a new log? It won't fix anything, it only adds logging.

@stefabat
Copy link
Author

stefabat commented Mar 4, 2024

I'll try it tonight when I get home. Thanks

@stefabat
Copy link
Author

stefabat commented Mar 4, 2024

I don't know what is broken, but even though it tells me there are 46k lines in the debug, when I try to send them to, in the pane where I can see the debug log, I see almost nothing. I downloaded the .tgz file, and that contains the full debug log.
In any case, the new debug log I submitted is: CC9SM8SN-euc/6.7.163.2797.5889-6

Let me know if you can see the 46k lines, if not, I have it and I can upload it here or send it to you.

By the way, I ran zotero only with betterbibtex active, and I still see the issue.

retorquere added a commit that referenced this issue Mar 4, 2024
@retorquere
Copy link
Owner

that's expected, zotero usually freezes when you show long text there, so I only show the first portion. I see attempts to generate new keys but no new keys are actually being assigned. A new version will drop here soon with more logging, please send a new log from that.

Copy link

github-actions bot commented Mar 4, 2024

🤖 this is your friendly neighborhood build bot announcing test build 6.7.163.2797.5895 ("Merge branch 'master' into gh-2797")

This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.163.2797.5895, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

@stefabat
Copy link
Author

stefabat commented Mar 5, 2024

New one in: UBD5S63L-euc/6.7.163.2797.5895-6

@retorquere
Copy link
Owner

Can you close Zotero and get me a copy of better-bibtex.sqlite and zotero.sqlite? You can email them to emiliano.heyns@iris-advies.com

@bradmont
Copy link

bradmont commented Mar 8, 2024

Hi, chiming in that I'm also having this problem, and have been for a while (really, I've been ignoring it for a few months, the pop-up notification is a bit distracting but it's not preventing me from getting work done). It was happening on v6 and also now on the v7 beta. I submitted my log, Debug ID D1700262065 (with LogEvents enabled). I am not seeing anything specifically better-bibtex related though.

@retorquere
Copy link
Owner

I can't read D<number> logs, those go to the Zotero team. I need a Better-BibTeX debog log, which ends in -euc or -apse.

@bradmont
Copy link

bradmont commented Mar 8, 2024

Oh, sorry, that makes sense. Is this better? 66Q6U3ZQ-fio-XcY7FfUAyq5c

@bradmont
Copy link

bradmont commented Mar 8, 2024

Sorry, I think I did the wrong thing and sent it to file.io, this looks like the format you described: 3P8UIGS9-euc/6.7.164-7

@retorquere
Copy link
Owner

File.io is fine (it's in the help menu briefly during start as a fallback in case BBT log doesn't work), but the -euc/-apse logs are much more convenient for me, so thank you. Unfortunately the release build you are running doesn't have the logging I built into 5895, so there's not much I can tell from this log, sorry.

@bradmont
Copy link

bradmont commented Mar 8, 2024

Ah, oops! I installed the debug build above and tried again, here's the ID: JYJ9ZIBD-euc/6.7.163.2797.5895-7

@retorquere
Copy link
Owner

Seems to be the same problem. I'll need a copy of zotero.sqlite and better-bibtex.sqlite here too. Make sure to shut down Zotero first -- it should not be running while to copy or bundle these files.

Copy link

github-actions bot commented Mar 9, 2024

🤖 this is your friendly neighborhood build bot announcing test build 6.7.164.2797.5910 ("dynamic queries")

This update may name other issues, but the build just dropped here is for you; it just means problems already fixed in other issues have been folded into the work we are doing here. Install in Zotero by downloading test build 6.7.164.2797.5910, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

@bradmont
Copy link

bradmont commented Mar 9, 2024

Great, just sent the sqlite files over email. :)

@retorquere
Copy link
Owner

please try build 5910

@bradmont
Copy link

bradmont commented Mar 9, 2024

yes! this seems to have resolved the problem. Now when I open Zotero the citekeys pop-up appears for a half second (too fast for me to read what it says) and disappears again. Thank you!

@retorquere
Copy link
Owner

@stefabat?

@stefabat
Copy link
Author

It works for me too, same behavior as for @bradmont. Thanks for the effort!

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

No branches or pull requests

3 participants