Work on zotero 7 support is underway

Debug log ID
NA
What happened?
Beta build for Zotero 7 (Z7) was released last week with major improvements and modernization of the codebase. I tried to install BBT with no success. It seems the current version of BBT is incompatible with Z7 beta.

That is correct

Is there a timeframe?

No. I'm actively working on it, and I keep thinking I'm close and then hitting another problem. It could be days, weeks or months.

... Thanks for your hard work!

Will the plugin Zotero Debug Bridge be updated to be  compatible with zotero v7?

I've uploaded the new version, 6.7.79 should work with 7.

No. I'm actively working on it, and I keep thinking I'm close and then hitting another problem. It could be days, weeks or months.

In a bit of good news, I'm one failing test away from getting BBT to bootstrapped, which is the most important hurdle.

I've uploaded the new version, 6.7.79 should work with 7.

Thanks. However, it prompts me:
The add-on "C:\Users\hmy\Desktop\debug-bridge-6.7.79.emile.limonia.xpi" could not be installed. It may be incompatible with this version of Zotero.

Same here, unfortunately. Running Zotero 7.0.0-beta.7+7c902d40a on Apple Silicon.

New version is up, same version number though.

Download again, and still cannot be installed.

I started the wrong version. I can replicate the install problem. Looking into it.

New version installs on 7

Now it installs on v7

I've just uploaded a new version. The commit will come tonight, but I just added the manifest.jsin that was missing.

Ok thank you very much! I was wondering because I am trying to do the porting of ZotFile to Zotero 7 as well, but I am having some issues that I do not understand (I am also not an expert on this, but it might help).

There's still something wrong with debugBridge.

DebugBridge is OK, and the last failing test for bootstrapped has now passed. Bootstrapped support is rudimentary at this point, it works (all my tests pass), but it's not as efficient as it could be. Cleanup on that is the next step. From this point on, debug builds will be announced here, you're very welcome to try them out, on Zotero 6 for now. When Zotero 7 compat is in, I will announce this here. This issue might get chatty from here on out.

Thank you for the awesome work!
I'm on Zotero 7.0.0-beta.7+7c902d40a on Apple Silicon. Tried to download and install test build <IP_ADDRESS>55 and it is not installing.
I saw that you said this version is running on Zotero 7, am I missing something?

No, this is the first version of BBT that is bootstrapped (aka restartless). It's a requirement for Zotero 7, but isn't sufficient.

It was the major hurdle though.

Thanks for being soooo darn fast - AGAIN - with work on an update for a beta release.

Fingers crossed but it doesn't look to be nearly as much work as the 4 to 5 port, and 6/7 compatibility is feasible, so I can move into 7 gradually. It will also fix a long-standing bug in BBT on macos.

tried installing zotero-better-bibtex-6.7.79 on Zotero (7.0.0-beta.8+77682cb45) on Intel Mac
Installation failed with following error:
1685993726059	addons.xpi	WARN	Invalid XPI: Error: File /Users///zotero-better-bibtex-6.7.79.xpi does not contain a valid manifest(resource://gre/modules/addons/XPIInstall.jsm:691:11) JS Stack trace: loadManifest@XPIInstall.jsm:691:11

this is the first version of BBT that is bootstrapped (aka restartless). It's a requirement for Zotero 7, but isn't sufficient.

求更新以适应新的版本

Working on it. Please stop asking. You can subscribe to this issue (you are now subscribed) to follow updates.

First snag: bootstrapped extensions apparently have problems which are pretty fundamental in their startup/shutdown handling. I've been waiting for a response from the Zotero crew, but they haven't gotten back to me yet.

Thx for hanging in there!

I'm really curious what they'll come up with. If my information is right, this is how restartless extensions have worked from the beginning some 12 years ago. It there's no fix, I'll have to rethink some pretty fundamental things in BBT.
But they've indicated before that with Zotero 7 they're considering making changes to the platform itself, so it's not impossible that they'll fix this. But it would mean that there would be a clean break for 7 support, not dual 6/7 support.

Thanks for your hard work!

But it would mean that there would be a clean break for 7 support, not dual 6/7 support.

If we want to support both z6 & 7, there is one more thing: the locale system.
Unfortunately but anyway we will face it sooner or later, the dtd support is going to be removed and registering preference pane no longer supports that in the latest beta of Z7.
An unofficial example here: https://github.com/windingwind/zotero-plugin-template/issues/49
(Not an officially announced change yet, but I think @retorquere might want to test it)

Removed as in static XUL files can no longer load DTDs for l10n? Everything must use props/FTL now? That pretty much kills static XUL loading.

Removed as in static XUL files can no longer load DTDs for l10n? Everything must use props/FTL now? That pretty much kills static XUL loading.

Well, just for the preference pane currently, but as Firefox 115 does not support dtd anymore, they will be removed from everywhere, yes. Maybe soon there will be an official announcement on this to provide a more detailed explanation.
FTL also can localize static XUL and is actually more flexible than DTD, so XUL elements are still alive. Maybe loading dtd with XUL is still allowed in Z7 for now, but my view as a plugin developer is to prevent using them (DTD).

😡💢‼☠ I don't need this in my life right now. Loading prefwindow with DTDs is gone in Z7?

Well, maybe just wait for the official announcement. Mozilla removed dtd, and Zotero will have to follow.
One possible good news is, maybe we do not need to do it manually. I see Zotero is working on an auto-conversion script from dtd to ftl.
[1] https://github.com/zotero/zotero/issues/3146
[2] https://github.com/zotero/zotero/pull/3153

I already have a DTD parser, so a converter is trivial to make. What is not trivial is converting my preferences window to non-XUL. I have a lot of automation around my prefs screen.

Hi there, sorry if this is already answered. is there a download for the latest beta release that may/could work on 7?

@satikusala as I know, there in no ported release yet, there are apparently some nontrivial issues related to porting of the plugin, you could read the previous comments in this thread

I'm waiting for putting out a beta until they've fixed https://groups.google.com/g/zotero-dev/c/mcpbvdEP8qw ; with that bug still in place there's a reasonable chance of data loss, and I don't want to deal with that.

Err... I think that is it. This passes my test suite on Zotero 7 beta. Beta from 2023-07-03 or later please -- Zotero fixed some bugs that BBT depends on, but there isn't really a good way to detect the particular beta release.

BBT seems to be stuck at "Starting object serializer" (see image attached). I am running the test build <IP_ADDRESS>05 of BBT.

BBT seems to be stuck at "Starting object serializer" (see image attached). I am running the test build <IP_ADDRESS>05 of BBT.

upon the freeze on "staring object serializer", restarting zotero seems to be able to rectify the freeze at this stage. Now it freezes on "starting user interface"

Same issues as above (freezes at starting object serializer on install, freezes at starting user interface on restart), only one error message in the console that I can tell refers to the plugin:

These appear only after trying to open the BBT preferences:

Reprodicible. No more info needed on this right now.

New build out.

I only just activated Z7, but ... when I try to open the BBT preferences, it just prompts me for a XUL file.

What efficiency!
Just confirming that the citekeys are back!!! and just now I tried exporting some entries - it works!
Hope I don't blow off all the happiness, but the preferences menu is still like this: https://i.imgur.com/ktxgbYf.png

Perhaps related issue: BBT sometimes seems to prevent manual changes to the metadata of an entry (e.g. date of publication, university of a published thesis amongst others) disabling BBT brings back the ability to change information.

Hope I don't blow off all the happiness

I detest UI work, so... but it's part of the package. This is reproducible.

BBT sometimes seems to prevent manual changes

I'd need a debug log for that

classic prefpane loading is completely b0rked on Z7 so that means I must move to the new prefpane format. This will take time.

hello, may I ask which zotero beta version is the latest for Mac m1?
I am using zotero 7.0.0-beta.16+1766f8bb5 and installed BBT test build <IP_ADDRESS>13.
I could not see the citekey in the row and also like others only see preferences of BBT is loading.
Thank you.

That is the right version of Zotero, but the prefs not loading is currently a known problem which I'm working on. For any problems not pertaining to the prefs screen I'd need a debug log.

That is the right version of Zotero, but the prefs not loading is currently a known problem which I'm working on. For any problems not pertaining to the prefs screen I'd need a debug log.

Thank you very much.
here is the debug log and I disabled all other plugin only use BBT and there are no citekey show in the row.
1688450336395	addons.xpi	WARN	Checking /Applications/Zotero.app/Contents/Resources/distribution/extensions for addons
[JavaScript Error: "NS_NOINTERFACE: " {file: "resource://gre/modules/ComponentUtils.jsm" line: 90}]
createInstance@resource://gre/modules/ComponentUtils.jsm:90:36
1688450336810	addons.xpi	WARN	Addon with ID undefined already installed, older version will be disabled
[JavaScript Error: "fromFileURI expects a file URI" {file: "resource://gre/modules/osfile/ospath_unix.jsm" line: 188}]
[JavaScript Error: "Error: Addon must include an id, version, and type" {file: "resource://gre/modules/addons/XPIProvider.jsm" line: 1710}]
[JavaScript Error: "Error: Addon must include an id, version, and type" {file: "resource://gre/modules/addons/XPIProvider.jsm" line: 1710}]
[JavaScript Error: "NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById]" {file: "resource://gre/modules/TerminatorTelemetry.jsm" line: 87}]
[JavaScript Error: "NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById]" {file: "resource://gre/modules/TerminatorTelemetry.jsm" line: 87}]
[JavaScript Error: "NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById]" {file: "resource://gre/modules/TerminatorTelemetry.jsm" line: 87}]
No chrome package registered for chrome://zotero-better-bibtex/skin/bibtex-menu.svg
[JavaScript Error: "TypeError: emptyListMessage is null" {file: "chrome://zotero/content/standalone/standalone.js" line: 631}]
ZoteroStandalone</this.updateAddonsPane/<@chrome://zotero/content/standalone/standalone.js:631:7
[JavaScript Error: "NotFoundError: Could not get children of file(/Users/phdluffy/Library/Application Support/Zotero/Crash Reports/events) because it does not exist" {file: "resource://gre/modules/CrashManager.jsm" line: 682}]
_getUnprocessedEventsFiles/<@resource://gre/modules/CrashManager.jsm:682:12
No chrome package registered for chrome://zotero-better-bibtex/skin/preferences.css
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
No chrome package registered for chrome://zotero-better-bibtex/skin/attention.svg
appName => Zotero, version => 7.0.0-beta.16+1766f8bb5, os => macOS 13.4.1, locale => zh-CN, extensions => Better BibTex for Zotero (<IP_ADDRESS>13, extension), Zotero Reference (0.5.9, extension, disabled), Zotero Better Notes (1.1.4-0, extension, disabled), Zotero Citation (0.3.2, extension, disabled), Zotero Figure (0.0.8, extension, disabled), Zotero PDF Translate (1.1.0-0, extension, disabled), Make It Red (2.0, extension, disabled), Zotero Addon Template (0.2.0, extension, disabled), Zotero Style (2.6.8, extension, disabled)

@retorquere Just wanted to express my appreciation for your work. I upgraded to Z7 today and installed BBT first thing. Working great! 👍

Apparently there are still problems (reported by @kzssc), and the prefs pane will need a ground-up rewrite.

No issues here but looking forward to the prefs pane!

I look forward to having it done. I hate UI work.

There's a reason I'm a LaTeX holdout 🙄

Hope I don't blow off all the happiness

I detest UI work, so... but it's part of the package. This is reproducible.

BBT sometimes seems to prevent manual changes

I'd need a debug log for that

Just to briefly clarify:

I ran into the same problem as @PhDLuffy when attempting at sending the debug log as the window is blank.

I reported that metadata can sometimes be changed:  I suspect, this might be due to BBT not fully loaded in Z7.

Once BBT is loaded, any click in the metadata box doesn't prompt the editing of the text box (though right-click still works though some option is greyed out too, see screenshot). My guess is that there might be some overlay issue? Not sure.
https://i.imgur.com/rEnwjdR.png

Overlays don't work at all in Z7, so it should not be possible that they're causing interference of any kind.

Thanks for all your work on this! Installed the latest test build <IP_ADDRESS>13 with Z7 7.0.0-beta.16+1766f8bb5. It runs, cache is being built. I did not expect the preference pane to show up (it doesn't) based on the above discussion. Alas, I also do not see the cite keys.
Here's the code from the Developer Error Console.
1688572446780	addons.xpi	WARN	Checking /Applications/Zotero.app/Contents/Resources/distribution/extensions for addons
NS_NOINTERFACE: [ComponentUtils.jsm:90](resource://gre/modules/ComponentUtils.jsm)
Missing resource in locale en-AU: browser/menubar.ftl
Missing resource in locale en-CA: browser/menubar.ftl
Missing resource in locale en-NZ: browser/menubar.ftl
fromFileURI expects a file URI [ospath_unix.jsm:188](resource://gre/modules/osfile/ospath_unix.jsm)
1688572447284	addons.xpi	WARN	Addon with ID undefined already installed, older version will be disabled
Error: Addon must include an id, version, and type 2 [XPIProvider.jsm:1710:13](resource://gre/modules/addons/XPIProvider.jsm)
Missing resource in locale en-AU: browser/menubar.ftl
Missing resource in locale en-CA: browser/menubar.ftl
Missing resource in locale en-NZ: browser/menubar.ftl
Uncaught (in promise) undefined
NS_ERROR_FAILURE: Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsITelemetry.getHistogramById] 3 [TerminatorTelemetry.jsm:87](resource://gre/modules/TerminatorTelemetry.jsm)
Style with ID http://www.zotero.org/styles/apa already loaded from apa.csl [style.js:182](chrome://zotero/content/xpcom/style.js)
No chrome package registered for chrome://zotero-better-bibtex/skin/bibtex-menu.svg
Missing resource in locale en-AU: browser/menubar.ftl
Missing resource in locale en-CA: browser/menubar.ftl
Missing resource in locale en-NZ: browser/menubar.ftl
Uncaught TypeError: emptyListMessage is null
    updateAddonsPane chrome://zotero/content/standalone/standalone.js:631
[standalone.js:631:7](chrome://zotero/content/standalone/standalone.js)
1688572490809	addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data(resource://gre/modules/addons/AddonUpdateChecker.jsm:342:23) JS Stack trace: onLoad@AddonUpdateChecker.jsm:342:23
UpdateParser/<@AddonUpdateChecker.jsm:286:54
1688572490810	addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data(resource://gre/modules/addons/AddonUpdateChecker.jsm:342:23) JS Stack trace: onLoad@AddonUpdateChecker.jsm:342:23
UpdateParser/<@AddonUpdateChecker.jsm:286:54
1688572490813	addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data(resource://gre/modules/addons/AddonUpdateChecker.jsm:342:23) JS Stack trace: onLoad@AddonUpdateChecker.jsm:342:23
UpdateParser/<@AddonUpdateChecker.jsm:286:54
1688572491001	addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data(resource://gre/modules/addons/AddonUpdateChecker.jsm:342:23) JS Stack trace: onLoad@AddonUpdateChecker.jsm:342:23
UpdateParser/<@AddonUpdateChecker.jsm:286:54
1688572491045	addons.update-checker	WARN	Request failed: https://github.com/retorquere/zotero-storage-scanner/releases/download/release/update.rdf - 404: Not Found
1688572491276	addons.update-checker	WARN	onUpdateCheckComplete failed to parse update manifest: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data(resource://gre/modules/addons/AddonUpdateChecker.jsm:342:23) JS Stack trace: onLoad@AddonUpdateChecker.jsm:342:23
UpdateParser/<@AddonUpdateChecker.jsm:286:54
1688572495020	addons.xpi-utils	WARN	Add-on<EMAIL_ADDRESS>is not compatible with application version. 2
1688572495021	addons.xpi-utils	WARN	Add-on<EMAIL_ADDRESS>is not compatible with application version.
Error running bootstrap method 'startup' on<EMAIL_ADDRESS>DB2.getCollection(...) is null [better-bibtex.js:36260](jar:file:///Users/jrennstich/Library/Application%20Support/Zotero/Profiles/oxt32dqe.default/extensions/better-bibtex@iris-advies.com.xpi!/content/better-bibtex.js)
NotFoundError: Could not get children of file(/Users/jrennstich/Library/Application Support/Zotero/Crash Reports/events) because it does not exist [CrashManager.jsm:682](resource://gre/modules/CrashManager.jsm)
unreachable code after return statement
[contentAreaUtils.js:1178:2](chrome://global/content/contentAreaUtils.js)
Missing resource in locale en-AU: browser/menubar.ftl
Missing resource in locale en-CA: browser/menubar.ftl
Missing resource in locale en-NZ: browser/menubar.ftl
Uncaught TypeError: emptyListMessage is null
    updateAddonsPane chrome://zotero/content/standalone/standalone.js:631

Are there other outputs I should/could generate?

I'm going to bring the standalone debug log plugin to Z7 for the interim. I'm still waiting for confirmation from Zotero why the UI parts for debug lig (and first run) don't work, but they may also be deprecated. Which would be a PITA. But whatevs.

Can I just manually edit a JS or whatever preferences file for the time being? If yes, what is that file?

Go into the zotero advanced prefs and open the config editor. All prefs are there, most are safe to edit, there are a few where you can enter any string but BBT expects a few certain values. Anything that has "options" in the site docs is that way.

Cite keys are now visible. But I am unable to edit the Info-fields in Z7, all other fields work. The only field I am able to click into and select the text under Info is the Citation key field.
BBT Version
6.7.92
Z7
7.0.0-beta.16+1766f8bb5

6.7.92 wasn't supposed to work on the beta, that was by accident. I've scheduled 6.7.94 which will disable beta support, the only beta-support is on the latest build dropped in this issue. I'll look into the startup error tomorrow.

All working again here - THX!

6.794 is not yet showing up when I update. Do I need to install a separate build?

6.7.94 will not show up for Zotero 7 (by design), I do not want people using the release builds on Z7b. Only the builds that drop on this issue are ready for test.

No changes (with Version <IP_ADDRESS>64) here unfortunately. Not able to edit under the "Info" Tab in Z7 (7.0.0-beta.17+8017b2ab1).
Used the BBT Debug Option. Buttons in the window do show up but are not titled. When I click on restart with logging enabled, nothing happens.

When I click the blue button I get the other attached dialog box.

I don't know why the UI texts do not show. The Zotero team hasn't responded yet to my request.

4577，preference still loading and a very long stem showed next to citekey.
very long

Are you sure you are on 4577? That string no longer exists in the source.

preferences will need significant effort to get done. Redoing the translations was the first necessary step, but I don't really expect prefs to be done the coming week. I'm now working on getting the debug log submission to work again. That takes priority over prefs because without it I'm severely handicapped in diagnosis.

 That string no longer exists in the source. (edit: and I cannot reproduce the problem)

I don't know why.
Thank you very much for your recent work, I only would like to export .bib file to my latex folder like older BBT version.
bbt-version-4577
open-preferences
window-loading

Export should work (all tests pass), but BBT in it's current state still has many UI flaws on Zotero 7. I cannot say when that work will be finished because I'm still finding out new things that don't work on Z7, and I don't know how many more I will find.

 That string no longer exists in the source. (edit: and I cannot reproduce the problem)

I don't know why.

Can you uninstall BBT, quit zotero entirely (cmd-q if you're on a mac), restart Zotero, then reinstall BBT, and see if the problem goes away? There's currently still a problem with installing BBT while it is running.

 That string no longer exists in the source. (edit: and I cannot reproduce the problem)

I don't know why.

Can you uninstall BBT, quit zotero entirely (cmd-q if you're on a mac), restart Zotero, then reinstall BBT, and see if the problem goes away? There's currently still a problem with installing BBT while it is running.

Be easy bro, I have another mac with zotero5 and BBT which works perfectly, I just start to transform my workflow from intel mac to m1 mac and this is why i am trying Zotero7(m1 natively). It doesn't influce my work. I just want to help you test the BBT beta on Mac.
uninstall BBT(even delete the staged file in zotero extesion folder), quit zotero entirely (right click on dock to quit complately), restart Zotero7 beta, reinstall BBT 4577.
After install the BBT 4577,  BBT stuck on the right-up corner side.  (better bibtex: starting object serializer)
right click on the dock to complately quit Zotero7 and then restart Zotero7, BBT works and the (better bibtex: starting...) vanished which mean the citekey all done.
and then everything the same, preferance is loading like older test version and no preferance pane in the zotero setting.
delete plugin complately even in the extensions
BBT installed without restart Zotero7 something stuck
restart zotero7 complately, figure2 no longer stuck.
nothing in the zotero setting which i used to export bib file in older BBT version

Ugh, so it's a reinstall problem. Which is a bummer because I can't easily create automated tests for it. But I know where to look.
 So much has changed there.

User interface for the BBT logger works fine now. Sending debug log takes v long, I assume this is caused by my rather larger database.
Otherwise no changes re editing in Info tab.
Thanks for all you hard work on this!

Nah, the base UI works, but the code that hooks it up to my code doesn't run, so it doesn't actually send off the log, and you can click backward and forward without any effect. I've asked again with the zotero devs whether the hookup code is still supposed to work, if not, I have some leads on a workaround. But documentation on the Firefox base they build on is non-existent, so it's all reverse engineering. And the zotero devs have their hands full and can only occasionally respond.

BBT Logging works like a charm here now.
Here's my ID
MPZXG757-euc
Again, thank you for the quick fix!
No changes otherwise (as you probably expected).

4595, mac 13.4.1, Zotero7 beta.
zotero setting now we can see the BBT pane but still loading
use BBT preference.open we could see this error window

No changes here. Debug ID 73FZUGSW-euc

The BBT menu now shows up now. Looks very good.
But still no editing of biographical information under the info tab.
Thanks for all your hard work! So much progress in the last few days.

Same here. Debug ID NGRSFTDU-euc

Still no editing in the info tab.

@roam-user  for me BBT <IP_ADDRESS>16 is not comaptible with 7.0.0-beta.17+8017b2ab1.

4616, mac 13.4.1, Zotero7 beta.
God said, Let there be light: and there was light.
the preferance is back
zotero setting preferance now is OK

No changes. Made a video of the Preference pane. I am able to click/select some items, none of the drop-down lists work for me.
Log ID: BTBV2E3J-euc
https://github.com/retorquere/zotero-better-bibtex/assets/22581234/5af48edc-4881-4edb-b961-65b0c3d933fe

A new build will drop in 10 or so that should fix that. As per usual BBT is quite the stress-test for Zotero, I'm touching a host of obscure stuff many other plugins don't have to deal with. With the new build the prefs pane should largely be useable, if a bit ugly at the moment. If that's settled I'm going to look at the item pane, which is where the fun stuff lives. That pane does not want to be modified. I have to work around that in an entirely new (but equally inappropriate) way. I'm surprised at how much headway I'm making actually.

@danieltomasz I cannot reproduce this. Can you check with the latest build?

@danieltomasz I cannot reproduce this. Can you check with the latest build?

4636, mac 13.4.1, Zotero7.0.0-beta.17+8017b2ab1
in zotero setting BBT preferance is working now.
thank you very much !
zotero setting BBT preferance

BBT <IP_ADDRESS>36  works with   7.0.0-beta.17+8017b2ab1 for me., preference pane is loading and looking really good

Debug log ID IFBYYKWR-euc
Drop down working now!
https://github.com/retorquere/zotero-better-bibtex/assets/22581234/5bf66844-0cf0-4d3a-8cf2-80f4d65ba7c4

Working here too.
FWIW, I originally installed over a previous version, and it didn't work. After uninstall -> install, it's working well.
By the way, thank you so much for all the work you've put into this!

Oh yeah reinstall on running doesn't work yet.

Info in Itempane is not editable for me on MacOS 13.4.1 with build 4637.

Have you restarted zotero? Upgrades without restart don't work yet.

Yes, several times.

Then I'll need a debug log. Please choose "restart with logging enabled" from the help menu, try to edit a few fields, and send a log. I'm on macos myself, and all the fields (not the citekey btw) are editable for me.

Didn't work for me either at first. Once I restarted Zotero for the third time WITH the debug modus active, it started to work! Weird.
Debug IG: D1530395687

Also, the Citation Key field now looks like all the other fields. Prior it was a textbook in wich I could select the citation key, but not edit it. Great! Thanks so much for making this work!

After uninstalling and reinstalling BTT, and restarting Zotero several times, the fields are now editable and look better than before.
Thank you so much for your making this work!

Sent Debug Log: 7T6KW42G-euc

Just installed test build <IP_ADDRESS>37 with Zotero 7.0.0-beta.17+8017b2ab1 on MacOS 13.3.1 and after one restart the fields are editable again 🥳(except for the citekey field, as expected). Thank you so much @retorquere for all your work on this so far.

Sent Debug Log: 7T6KW42G-euc

No relevant error in the log alas. If you see it happening, just submit a log and post the ID here, hopefully the error is severe enough that it shows up in the log even with debugging off. I'll update https://github.com/retorquere/zotero-debug-log for Z7, installing that forces the debug log to be on always, but it doesn't currently work in Z7.

Just installed test build <IP_ADDRESS>37 with Zotero 7.0.0-beta.17+8017b2ab1 on MacOS 13.3.1 and after one restart the fields are editable again 🥳(except for the citekey field, as expected). Thank you so much @retorquere for all your work on this so far.

Couldn't do it without the help y'all are providing, so right back at ya.

Couldn't reproduce the error. Now it worked after the first install und restart of Zotero.

That's a Zotero debug log, I have no access to these; I need a BBT debug log (the ones with -euc or -apse in the ID).

Sorry, my bad!
Debug ID: U4T8HQ4A-euc

The issue described in #2066 is a bit more severe now (using test build <IP_ADDRESS>41).  Now, the Item Type field becomes selected and hitting the arrow keys changes the selected item.

I'm still having trouble installing 4681 on Zotero 7.0.0-beta.22+676f820f8

If you rename the .xpi to have the extension .zip instead, can you view its contents? If it's not a valid zip file, something went wrong during the download.

If you rename the .xpi to have the extension .zip instead, can you view its contents? If it's not a valid zip file, something went wrong during the download.

Can view its contents, yes. (prefs.js, manifest.json, locale, etc.)
The Zotero error I got was: The add-on "Better BibTex for Zotero" could not be installed. It may be incompatible with this version of Zotero.
Thank you!

I have the same problem as @yiqinfu. I cannot install the Release v6.7.94 on Zotero 7.0.0-beta.22+676f820f8 (64-bit) on Windows 10.
I can rename the .xpi to .zip and see its contents.
I also get the same error message after trying to install the plugin by selecting the .xpi file: "The add-on "Better BibTex for Zotero" could not be installed. It may be incompatible with this version of Zotero."
Thank you.

@yiqinfu are you also on windows?

I also get exactly the same on Ubuntu 23.04.

I have the same problem as @yiqinfu. I cannot install the Release v6.7.94 on Zotero 7.0.0-beta.22+676f820f8 (64-bit) on Windows 10.

Are you trying to install v6.7.94, or <IP_ADDRESS>41 (I see that the latter has expired, I've scheduled a new beta which will drop here shortly)? v6.7.94 (the release version) is not compatible with Zotero 7, that's as it should be. Only the beta releases dropped in this issue will install in Zotero 7.

Sorry, it was indeed the v6.7.94 and not the <IP_ADDRESS>41.
I can now download the latest test build <IP_ADDRESS>88.
I was looking for the Zotero 7 version in the pre-releases, in the same way as for the PDF-Preview plugin: https://github.com/windingwind/zotero-pdf-preview/releases

BBT doesn't use the pre-releases that way. There's really only one github prerelease, which is where all issue builds are dropped (https://github.com/retorquere/zotero-better-bibtex/releases/builds), but I use issue-specific pre-releases, so you can't really deduce from the version numbers there which is the "latest" (because that is issue-specific).

@yiqinfu this was not the problem you had, right? You were installing a non-release build dropped in this channel.

@yiqinfu this was not the problem you had, right? You were installing a non-release build dropped in this channel.

Yes, I was installing 4681 on a Mac. I just tried 4689 (the latest build available), and it's working! Thanks.

No idea what changed in the interim (I'm on a Mac myself, and I could install it), but I'll take it.

Zotero 7.0.0-beta.23 is now the minimum version supported.

Not sure if this is v7 related. Just tried to refresh citation keys for an entire collection and got stuck in this popup without any controls to proceed. Keyboard doesn't work either. Tried escape, enter, space and combinations with control keys. Had to restart Zotero to regain control.

OK so dialogs are broken again. Looking into it.

The citationKey is correctly generated. But, the Sycning is not working for me.

I'm not sure what you mean by syncing?

I mean exporting. It used to update the exported file updated. Doesn't it?

I am also unablet install <IP_ADDRESS>98 and latter versions on Mac Ventura. It says it is incompatible with Zotero 7.
<IP_ADDRESS>97 installs correctly.

I am also unable install <IP_ADDRESS>98 and latter versions on Mac

4698 is not compatible with Zotero 7. Only builds dropped on this issue will install on Zotero 7.

Please do not install any builds by looking for the latest on https://github.com/retorquere/zotero-better-bibtex/releases/builds. I'll see if I can add the issue number into the version, but these builds are linked to from various issues, and they will have very different code enabled between issues before I merge them into the main build. I might be testing stuff there that will never make it into any release, beta or otherwise.

@Dello auto-export does pass the tests on build 4697; anything that drops here has passed the full test suite. A new build will drop here shortly, of that still doesn't work, please reproduce the problem and send a debug log.

Please do not install any builds by looking for the latest on https://github.com/retorquere/zotero-better-bibtex/releases/builds.

Oh, ok. Thanks.

🤖 this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>2.4738 ("tooltips")
Install in Zotero by downloading test build <IP_ADDRESS>2.4738, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

This one installed correctly.
But, where is the BB's preference window supposed to appear?
I am not getting it in Zotero's Preference.
https://take.ms/WBwom

Please choose restart with debugging enabled from the help menu, let zotero restart, open the preferences, and then send a BBT debug log from the help menu.

@Dellu prefs show for me on MacOS and Linux, and auto-export works on both for me. Without a debug log, there is nothing I can do.

@Dellu Zotero 7 beta 25 was broken and didn't show prefs for any plugin, beta 26 restores them somewhat, but I'm seeing rendering issues.

I am unable to get this version started in Z7 (7.0.0-beta.26+6dcc70f53) on MacOS. It's stuck (see screenshot). Cannot make logs, as it does not load unfortunately.
No issues with 4738, worked smoothly and fine.

Same here.
The Status message I see in the BBT Settings is:
Status: TypeError: affectedBy[translator2.label] is undefined

@jrennstich I got the same, but after restart of Zotero and waiting some this was resolved

I was wondering about that renaming issue as well (also thought, it's an Z7 issue)! Some PDFs could be renamed, others could not. All PDFs that were downloaded in some predetermined common naming fashion (Accepted Version, SAGE PDF Full Text, PDF Full Text, etc.) can only be renamed once you edit that name, then it works fine.

@jrennstich I got the same (MacOS 13.4.1 Zotero 7.0.0-beta.26, BBT <IP_ADDRESS>2.4748) but after restart of Zotero and waiting some this was resolved
For people on Z7, does renaming files from parent metadata work for you? With BBT active renaming doesnt do anything or literally use "{{ firstCreator suffix= - }}{{ year suffix= - }}{{ title truncate=120 }}.pdf"as a name of the file
https://forums.zotero.org/discussion/106560/renaming-files-broken-in-zotero-7-beta-26-affecting-zotero-6?new=1
I was thinking that it was issue with Z7 beta, but after sevaral attempts to disable/downgrade BBT and restarting, renaming started working again (with BBT inactive)

I have the latest BBT version installed, and 'Rename from Parent Metadata' works for me (using Zotero's still non-editable renaming schema…).

My steps, this is complex interaction, it may be as well cause by changes in Zotero

On Zotero 7 beta installing and enabling BBT  <IP_ADDRESS>2.4748: PDF cannot be renamed
Disabling BBT will enable me to rename, but this give me pattern  "{{ firstCreator suffix= - }}{{ year suffix= - }}{{ title truncate=120 }}.pdf"
Switching Back to Zotero 6 and BBT 6.7.94 stills holds this pattern ( "{{ firstCreator suffix= - }}{{ year suffix= - }}{{ title truncate=120 }}.pdf")
Switching to Zotero 7 (which disable the plugins by safe mode and incompatibility of 6.7.94) give me  back normal renaming
But then when I swithc back to  Zotero 6  I get this bad pattern string as a name again "{{ firstCreator suffix= - }}{{ year suffix= - }}{{ title truncate=120 }}.pdf"

Thx, @danieltomasz for the suggestions. I was finally able to get 4748 to run. Alas, when I tried to send a log I ran into new issues. Every time I try to "Send BBT log" I get a dialog, that says, I need to Restart with Logging enabled. Which is fine. Only, it tells me so every time after every update. When I click on the blue button (see attached img) I get the message "Please wait while the debug log is submitted."

when I click the same blue button again, I get the message in the next attached img.

The send debug log wizard is broken again. I have no idea why, because I haven't made any changes to it.

What is interesting about my renaming problem

there is probably some  malformed  settings, the pdf rename to " firstCreator suffix= - }}{{ year suffix= - }}{{ title truncate=120 }}.pdf" and in Zotero 7 without safe mode
with Zotero 7 safe mode renaming works ok

I am not to exit safe mode, even with disabled plugin (so this setting somewhat persist?)
In new test profile, I am not able to install  BBT <IP_ADDRESS>2.4748, I am getting   error, "Better BibTex for Zotero is incompatible with Zotero 7.0.0-beta.26+6dcc70f53."

I see now too that the object serializer does not finish. Installation is still without problems for me -- I don't know what to say about that. I can't reproduce it.

Regarding the installation - steps to reproduce:

I am creating new clean profile on Zotero 7
When I am try to install zotero-better-bibtex-<IP_ADDRESS>2.4748.xpi I am geting the above error
When I install first zotero-better-bibtex-<IP_ADDRESS>2.4738.xpi and then install zotero-better-bibtex-<IP_ADDRESS>2.4748.xpi everythings works

I've done the same and cannot reproduce this (on Mac Ventura should that matter). Can you take this up on the Zotero forums? There must either be something in the metadata I'm providing that isn't right, or there's a more general problem with installing plugins in the beta, since that not-compatible report comes before any of the plugin code is executed.

I was wondering about that renaming issue as well (also thought, it's an Z7 issue)! Some PDFs could be renamed, others could not. All PDFs that were downloaded in some predetermined common naming fashion (Accepted Version, SAGE PDF Full Text, PDF Full Text, etc.) can only be renamed once you edit that name, then it works fine.

This happening without BBT installed, I created an issue at Zotero forum
https://forums.zotero.org/discussion/106562/rename-file-from-parent-metadata-doesnt-always-work-in-z-7-beta-26?new=1

The betas dropped here ought to be release-quality for Z6. If something doesn't work in Z6 that gets top-priority to fix.

When  installing latest BBT in Z7 and switching with the same profile  from Z7 to Z6 and back to Z7 I am quite consistently getting info about incompatibility, when I install latest BBT in Z6 and switch  to Z7 everything seems to be ok, could other users can reproduce?

I can reproduce this. I'll report it to Zotero.

All working well here now.
Debug Log ID: CA2LHA6K-euc

It was possible to choose BBT-sentence case from a right-click (Mac) when clicking into the title of an entry. Would it be possible to add that feature again?

I'm looking into it but haven't found out how yet.

With test build <IP_ADDRESS>2.4762 on 7.0.0-beta.26+6dcc70f53
.bib file export automatically without any issues. The problem is "BetterBibTeX JSON" export when "Export Notes" is enabled.
I still get the message "TypeError: affectedBy[translator2.label] is undefined"

Disabling and enabling installed BBT causes TypeError: DB2.getCollection(...) is null with <IP_ADDRESS>2.4762 in Z7
I dont know how to send a log as doing this cause BBT to not turning on until next restart, where the log might be saved on disc?

Disabling/enabling doesn't currently work (see list at the top).

@roam-user 4763 should fix the auto-export problem.

4764 has disable/enable support, but don't toggle it on and off too fast because of this. I hope this will be taken up by Zotero, if not, I have a workaround (which is inelegant and slightly fragile, so I'd rather not use it).

It now works flawlessly! That was really fast! Thank you so much.

It now works flawlessly! That was really fast! Thank you so much.

Same here!

After a reboot of Zotero, I am stuck here (better bibtex: translators

Managed to get the installation to work after a complete system reboot, de- and following reinstallation of BBT 4764.
Debug Log-ID: F652BEYL-euc

After a reboot of Zotero, I am stuck here (better bibtex: translators (MacOS/Z7 7.0.0-beta.26+6dcc70f53, BBT 4764)

I am working on an emergency debug log sender.

Citation key is now completely editable!

That is correct :). I'm not entirely decided on the behavior, but something like this was going to have to happen anyway when Zotero adds a formal Citation Key field for all item types.

When I edit the citation key, I see the new value in the sidepane along with an indication that it has been pinned:

However, in the automatically exported .bib file, the new value does not appear (perhaps the action wasn't triggered?). Below are the automatic export settings:

If I manually export, then the new value is reflected.
This is with BBT <IP_ADDRESS>2.4764 on Zotero 7.0.0-beta.23+fb5934563.

Added to the list of open issues, I'm working on the export dialog right now.

One minor UI issue here on a Mac:

@jrennstich this is known issue with latest Z7 beta https://github.com/retorquere/zotero-better-bibtex/issues/2522#:~:text=prefs screen has rendering issues on beta 26

I had a previous build of BBT that was working on Zotero 7 but this morning it kept being stuck on "better bibtex: cache" for some reason ; tried installing the latest (test build <IP_ADDRESS>2.4768) but been getting this error message:

Any idea?
By the way, thank you for all the active dev on this plugin :)

I’ve been able to install test build <IP_ADDRESS>2.4770 and it seems to be working fine so far, no error message and nothing gets stuck.

BBT adds an option "send debug log to file.io" to the help menu that it removes after initialization. While it is a much less convenient way for me to receive logs than with the regular debug log, these will work regardless of (pretty much) any error in BBT startup. It will send the debug log and any items you happen to have selected in the main pane.

I am using a plugin in Obsidian that is calling Zotero by referencing BBT,
This pluging works with latest beta in Z6 but not in Z7
Plugin from Obdsidian calls Zotero search

When I have open Z7 console I see errors from better-bibtex.js.
XPCOMUtils.generateQI is not a function or TypeError: XPCOMUtils.generateQI is not a function
Mozilla deprecated XPCOMUtils some time ago,  (XPCOMUtils.generateQI is now ChromeUtils.generateQI -)
https://groups.google.com/g/mozilla.dev.platform/c/Vi6H4SFkSOk
I commented on it in the github thread here https://github.com/mgmeyers/obsidian-zotero-integration/issues/223
I just droping it here in case if there is quick fix, otherwise the developer of the Obsidian Plugin might jump in with more details

I am replicating the same behaviour with this vscode plugin https://marketplace.visualstudio.com/items?itemName=mblode.zotero
It is opening Zotero search and finding the item, but no item is inserted as 'XPCOMUtils.generateQI is not a function` appear in the error console

@warwickmm auto-export after editing the citekey works again.

I installed <IP_ADDRESS>2.4775 and editing the citekey still doesn't appear to trigger auto-export.

@danieltomasz aw 🤬🤬🤬🤬🤬 that's part of a reverse-engineered shim for the zotero citation plugin framework. That's not a small thing to re-do. 😮💨 I'm taking this up tomorrow, it's late here. I had so hoped I'd be close to tying up 😞 .

I installed <IP_ADDRESS>2.4775 and editing the citekey still doesn't appear to trigger auto-export.

Y'all know what follows...

Confirmed, it works now.  Thanks!
I did some testing and realized that no changes (e.g., editing a title) were triggering an auto-export.  Turns out I needed to right-click on My Library -> Export Library ... -> select Better BibTeX -> check "Keep updated".  This was working fine with Zotero
and I've never unchecked that, so perhaps something along the way must have disabled that setting.

But the auto-export was still present in the prefs?

XPCOMUtils.generateQI is not a function or TypeError: XPCOMUtils.generateQI is not a function

Actually might be a simple fix. Build incoming, but I need to get some sleep.

Yes.  Also, upon checking "Keep updated", the "Background export" checkbox is automatically checked.  However, upon revisiting that menu, "Background export" is unchecked.  Not sure if that's expected.

@warwickmm not expected, no. That probably means the export options handler errored out.
We're close to getting this finished, but I have too many interleaved discussions here running now. Anyone still having problems (like @warwickmm, possibly @danieltomasz, depending on incoming build 4777), can you please open a new issue with "Z7" in the title? I will still (also) drop builds here when I fix something, so if you're at any point not active with an issue, you can get your builds here.

Good new on Z7 is that my tests consistently finish way faster on Z7.

@danieltomasz 4776 should fix CAYW

W-O-W the heaviest test in my suite runs between 9:31 and 12:05 on Zotero 6 and 0:34 and 0:38 on Zotero 7.

@retorquere 4776 is working and fixing the problem, thank you!

Thank you very much @danieltomasz and @retorquere !

When upgrading BBT to test build <IP_ADDRESS>2.4783, I get the following error.

I get the same error if I repeat the install (installing <IP_ADDRESS>2.4783 ontop of itself)
Zotero 7.0.0-beta.26+6dcc70f53

"translator init takes insanely long"
I'm seeing this on the recent builds. I've left it sitting for many minutes and it doesn't halt. I've had to resort to reverting to an earlier BBT beta.

"translator init takes insanely long"
I'm seeing this on the recent builds. I've left it sitting for many minutes and it doesn't halt. I've had to resort to reverting to an earlier BBT beta.

As always, need debug log.

:robot: this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>2.4790 ("unregister for debug log")
Install in Zotero by downloading test build <IP_ADDRESS>2.4790, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

@vancleve 4790 fixes the unregister error. I'm leaving the emergency sender on for now. Any more problems will have to be reported as separate issues -- sorry for the abrupt cutoff, but I was getting lost in what still needed fixing.

Build 4811 (also about to drop on #2602 as 4812) starts the UI and leaves the init of the zotero translator framework (which takes 8-10 seconds) to the background.

I've unlocked the issue again -- questions are fine here again, but if there is anything that is broken in some way, please file a new issue with a debug log. Builds will continue to drop here until BBT is out of beta.

Just the one issue of citekey display/edit (plus squashing bugs, there have been a few over the past week) that waits on a new API under development by the Zotero team, and then BBT is feature-complete for Zotero 7.

When the citekey edit/display is back, then yes. For now, BBT cannot display the citation key in any way in Zotero 7. A change in Z7beta is in the works to make it possible again. I will announce here when it's back. But for anything involving a debug log, please either open a new issue, or join another non-#2522 issue where the problem is reported.

For Zotero 6 that is. For 7 I'm still waiting on directions (#).

Well that's not great.

A close simile of BBT sentence-case is now the standard sentence-case in the latest beta.

Should this issue be closed since it's done and you are dropping Zotero 7 compatible versions of zotero-better-bibtex in the normal release site https://github.com/retorquere/zotero-better-bibtex/releases ?

It is still open to keep visible for everyone that this last line is not finished and why:

[ ] "citekey display/edit field awaits API from Zotero"

I’m just leaving this here in case it helps anyone: we can still see the BBT key for individual items by right-clicking + choosing "Change Bibtex key" in the BBT menu. Obviously it’s a bit more involved than seeing it in the Info pane but nonetheless makes BBT functional for Z7 in the meantime.
Also, it’s weird that the key still shows up for Preprint items but not Journal articles...

You can also see the citation key by adding it to the item list columns.

Will this update be compatible with the epub file too? I'm not able to import highlights from epub file in obsidian ? I don't know if this is problem with plugin or zotero itself ? Or Do I have to do something different?

That's not functionality that is related to BBT.

Just to confirm that I'm not an anomaly: exporting BBT can ramp the power consumption to 3,000 compare to, say, 70 for safari? Also rendering interaction with Zotero UI very laggy?
https://i.imgur.com/MtCXgK9.png
7.0.0-beta.43+f803c0cc4
M1 13.6

Depends entirely on how many items are being exported.
If you want a diagnosis, please open a new issue with a debug log ID.

A build is going to drop here in 10 minutes or so; this build changes the internal database for the auto-exports in a lead-up to a cleanup and performance change. This build, as always, has passed the full test suite, or it couldn't drop here, but I want to make abundantly clear
this changes the structure of the BBT database
this change is fully reversible but needs a manual intervention to do so before you can go back to the GA release. I intend to release this change somewhere this week because it's holding up other work; I've tested it to death but I'm just nervous about a change like this. I would hugely appreciate it if some of you who use auto-exports would try it out. You  should see zero functional difference. I fully expect this change to Just Work.

Error upon installing new update, attaching screenshot.

Are there other errors in the log about creation of the autoexport table? The table should have been created just before this.

I can't replicate this unless I force the error. But the "send debug log to file.io" will be active in the help menu -- please send a log.

on the upside -- as long as that error is there, your database has not been migrated, so you can go back to the current release without changes.

I can't replicate this unless I force the error. But the "send debug log to file.io" will be active in the help menu -- please send a log.

not on my part. The BBT cannot finish start-up, and the debug option is unavailable from the menu. :(

Just to be sure -- it's not the regular BBT debug log sender, it's the generic log sender that is at the bottom of the help menu here:

just to reiterate, at this point you can just 6.7.123 and the problem will go away. But I'm keen to find out what happens on your system that doesn't happen on mine (or the test infra for that matter). I'm also on Mac so that's not it.

(that option goes away 15 seconds after successful init of BBT, but if BBT does not initialize fully, it should stay in the menu)

hmmm i just now reverted back to the previous version and then re-installed the new one - now no error log. intriguing.

No issues updating for me.

hmmm i just now reverted back to the previous version and then re-installed the new one - now no error log. intriguing.

It's the kind of intrigue I could do without... The file.io option was really missing then? I have no explanation for that either.
Anyhow valuable to have seen this here rather than at rollout 🙄

When you click on "export now", does it export? If you set up a new auto export, does it appear in the prefs?

The existing auto export still works.  However, when I right-click on a library and select Export, I see that "Keep updated" is unchecked.  Not sure if that's expected.

When you click on "export now", does it export? If you set up a new auto export, does it appear in the prefs?

Yes to both.

Man, in the notification I only saw everything up to and including "however", got me worried there 😉.
Keep updated always defaults to off, although that was broken for a while. The idea is that a new auto export is always a deliberate choice, not something you could accidentally set up.

Thanks for the feedback -- the new database setup is going to roll out this weekend. A new version will drop, which as always be an automatic upgrade for the testers here.

BBT cannot start when upgrading to 6.7.125, revert back to 6.7.124 works

On it -- sorry it took so long, I was out of coverage.

🤖 this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>2.5210 ("replace, not insert")
Install in Zotero by downloading test build <IP_ADDRESS>2.5210, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

Getting the following error msg (both from the internal update via Zotero and reinstall from file)

Error: Error(s) encountered during statement execution: UNIQUE constraint failed: better-bibtex.name [QUERY: UPDATE betterbibtex."better-bibtex" SET name = ? WHERE name = ?] [PARAMS: "migrated.autoexport", "better-bibtex.autoexport"] [ERROR: UNIQUE constraint failed: better-bibtex.name]

Debug Log ID for BibTEX
FWQHC4FQ-G8hGh1qUoHha

I cannot reproduce this -- I know this is an extreme measure, but can I get a copy of your better-bibtex.sqlite (taken with Zotero not running -- cmd-Q is you're on a mac). Can be sent to<EMAIL_ADDRESS>

This version fixed the problem - thanks!

I cannot reproduce this -- I know this is an extreme measure, but can I get a copy of your better-bibtex.sqlite (taken with Zotero not running -- cmd-Q is you're on a mac). Can be sent to<EMAIL_ADDRESS>
That email address go rejected. Perhaps the attachment is too large (5 MB)?

Shouldn't be, but if you still have a copy of the db pre-fix, please keep it and I'll get you a place to upload it.

Ah I see you used we transfer - stellar. Regardless of it being fixed, I still want to see if I can find the cause.

That database only has the pre-migration state, I had expected to find a partial migration.

That database only has the pre-migration state, I had expected to find a partial migration.

Is there something I can/should do? I just keep updating the latest Z7 betas (currently running 7.0.0-beta.46+c27bac2ad)

No, nothing to do, the fix will have removed the conflict state.

I just encountered the following popup.  It this of any concern?

It is if you experience it again after a disable/enable of BBT.

A build is going to drop here in 10 minutes or so; this build is the phase 2 for changes the internal database, this time for citation keys in a lead-up to a cleanup and performance change. This build, as always, has passed the full test suite, or it couldn't drop here, but I want to make abundantly clear
this again changes the structure of the BBT database
this change is fully reversible (and will remain so) but needs a manual intervention to do so before you can go back to the GA release. I intend to release this change somewhere this weekend because it's holding up other work; I've tested it and the migration is simpler this time so should be more robust, but, again, I'm just nervous about a change like this. I would hugely appreciate it if some of you would try it out. You should see zero functional difference. I fully expect this change to Just Work (famous last words, eh?).

Naturally. Let the games begin... (thanks for providing such amazing software and support).

Following error after app reboot.

Error: Error(s) encountered during statement execution: there is already another table or index with this name: migrated-better-bibtex [QUERY: ALTER TABLE betterbibtex."better-bibtex" RENAME TO "migrated-better-bibtex"] [PARAMS: ] [ERROR: there is already another table or index with this name: migrated-better-bibtex]

Debug Log ID wouldn't work on first attempt. Reboot, then:
AL39N2A8-w1qSfZ6d5RgB

Following error after app reboot.

Error: Error(s) encountered during statement execution: there is already another table or index with this name: migrated-better-bibtex [QUERY: ALTER TABLE betterbibtex."better-bibtex" RENAME TO "migrated-better-bibtex"] [PARAMS: ] [ERROR: there is already another table or index with this name: migrated-better-bibtex]

I tested this. How does this happen? This is like the previous error on upgrade, and this one is simpler; a table rename in SQLITE should be atomic.
I'll be right back, I need to test something.

Open the javascript console, check the "async" checkbox, and run
//await Zotero.DB.queryAsync('ATTACH DATABASE ? AS betterbibtex', [OS.Path.join(Zotero.DataDirectory.dir, 'better-bibtex.sqlite')])

await Zotero.DB.queryAsync('DROP TABLE betterbibtex."migrated-better-bibtex"')

then restart BBT, and send a debug log.

5260 will flash a warning if the migration fails, although I still don't know how it's technically possible. If that still happens, just install the regular release and wait with further testing.

Open the javascript console, check the "async" checkbox, and run
//await Zotero.DB.queryAsync('ATTACH DATABASE ? AS betterbibtex', [OS.Path.join(Zotero.DataDirectory.dir, 'better-bibtex.sqlite')])

await Zotero.DB.queryAsync('DROP TABLE betterbibtex."migrated-better-bibtex"')

then restart BBT, and send a debug log.

Sorry, but what's the javascript console?

🤖 this is your friendly neighborhood build bot announcing test build <IP_ADDRESS>2.5260 ("HOW CAN A RENAME YIELD A COPY?!?!")
Install in Zotero by downloading test build <IP_ADDRESS>2.5260, opening the Zotero "Tools" menu, selecting "Add-ons", open the gear menu in the top right, and select "Install Add-on From File...".

This time, I got the same error message when installing the new test build.

Error: Error(s) encountered during statement execution: there is already another table or index with this name: migrated-better-bibtex [QUERY: ALTER TABLE betterbibtex."better-bibtex" RENAME TO "migrated-better-bibtex"] [PARAMS: ] [ERROR: there is already another table or index with this name: migrated-better-bibtex]

After reboot, same problem:

Error: Error(s) encountered during statement execution: there is already another table or index with this name: migrated-better-bibtex [QUERY: ALTER TABLE betterbibtex."better-bibtex" RENAME TO "migrated-better-bibtex"] [PARAMS: ] [ERROR: there is already another table or index with this name: migrated-better-bibtex]

5260 will flash a warning if the migration fails, although I still don't know how it's technically possible. If that still happens, just install the regular release and wait with further testing.

No warning flashed here unfortunately, only the error message :-(


Search Services (UI)

Feature Request
Desired behaviour
After https://github.com/dockstore/dockstore/issues/2576  .  UI's search page should handle services
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 1.7
┆Issue Number: DOCK-791

Can wait


Automatically apply charset='utf-8' to script

Avoid mandatory charset='utf-8' string, for example to properly encode ellipsis

Oh, or the cherry-picked commit just needs to be toggled on: https://github.com/ch4ot1c/showdown/commit/10a893e5b3a6d38a0cd5c8d0e41691090681edc0#diff-04c6e90faac2675aa89e2176d2eec7d8R356 🤦
But perhaps there are other cases this could be useful.


Improve simulation for multiple observables

When simulating a circuit with multiple logical observables, currently we need to call sinter.collect one time for each observable. This can waste plenty of time because the computation circuit stays the same and in principle we only need to run the simulation once to get all the statistics for the OBSERVABLE_INCLUDEs in the circuit.
However, when I looked into sinter I found no easy way to do that.
One thing might be helpful is the count_observable_error_combos argument in sinter.collect:
count_observable_error_combos: Defaults to False. When set to to True,
            the returned stats will have a custom counts field with keys
            like `obs_mistake_mask=E_E__` counting how many times specific
            combinations of observables were mispredicted by the decoder.

I thought about setting the custom_error_count_key to one of the observables with the minimum correlation surface(i.e. we can assume it has relative low logical error rate) like obs_mistake_mask=_E_. Then sinter will apply max_errors to that observable to make the number of samples kind of reasonable for each observables. Some similar strategies might also be viable.

+1 for solving this. We definitely only want to be running two simulations,
one for all output Z correlation surface, and one for all output X
correlation surfaces.
On Wed, Oct 16, 2024, 5:56 AM Yiming Zhang @.***> wrote:

When simulating a circuit with multiple logical observables, currently we
need to call sinter.collect one time for each observable. This can waste
plenty of time because the computation circuit stays the same and in
principle we only need to run the simulation once to get all the statistics
for the OBSERVABLE_INCLUDEs in the circuit.
However, when I looked into sinter I found no easy way
https://quantumcomputing.stackexchange.com/questions/29273/using-sinter-to-collect-error-rates-of-multiple-observables
to do that.
One thing might be helpful is the count_observable_error_combos argument
in sinter.collect:
count_observable_error_combos: Defaults to False. When set to to True,
the returned stats will have a custom counts field with keys
like obs_mistake_mask=E_E__ counting how many times specific
combinations of observables were mispredicted by the decoder.
I thought about setting the custom_error_count_key to one of the
observables with the minimum correlation surface(i.e. we can assume it has
relative low logical error rate) like obs_mistake_mask=E. Then sinter
will apply max_errors to that observable to make the number of samples
kind of reasonable for each observables. Some similar strategies might also
be viable.
—
Reply to this email directly, view it on GitHub
https://github.com/QCHackers/tqec/issues/364, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAXTFN72WVBT4GAQZZKW3Z3ZO6BAVCNFSM6AAAAABQBNAH36VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU4TCOBRGA2DEOA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

In my mind, this issue is a great starting point for contributing to the community. It is not tightly coupled to the codebase, yet its resolution is very important and beneficial.

Hi @inmzhang, is anyone working on this issue? If not, I am interested in working on this!

Hi @inmzhang, is anyone working on this issue? If not, I am interested!

Hi @purva-thakre, I've actually started thinking about this issue recently, but I do not have a good solution in mind yet. I don't think any one else is working on it--please feel free to assign yourself.
I'll assign myself as well to avoid confusion. Do you have a solution in mind or would it be helpful to discuss? Let me know and I'll email you.
Thanks,
Kabir

Hi @KabirDubey , I am new to this project.
I definitely don't have a well sketched-out idea for how to resolve the issue. I was hoping to familiarize myself with the project by working on the issue.
I wouldn't mind working on this together. I don't have permission to assign myself.


how to return custom error messages through winrt::Result?

I want to return my own error message in winrt::Result. To do that I'm doing this:
winrt::import!(
    dependencies
        os
    types
);

fn main() {
  let e = winrt::Error::new(winrt::ErrorCode(0), "My error message");
  println!("{}", e.message());
}

This code unexpectedly prints "The operation completed successfully." - default message for error with code 0.
Debugging this I found that in 'Error::message(&self)' method the condition "if !self.info.is_null()" fails and message() method fallbacks to creating default error message for specified error code.
Probably the "info: IResrictedErrorInfo" is null because flag UseSetErrorInfo is not set by RoSetErrorReportingFlags, as specified here: https://docs.microsoft.com/en-us/windows/win32/api/roerrorapi/nf-roerrorapi-rooriginateerror:

If the UseSetErrorInfo flag is set by calling the RoSetErrorReportingFlags function, and the calling thread has been initialized in COM, the function creates an appropriate error object that supports IRestrictedErrorInfo and associates it with the COM channel by calling SetErrorInfo.

Unfortunately it's still hard for me to directly call windows API from Rust, so I can't test this hypothesis right now

That's because zero is the value for a success code rather than a failure code. Try this instead:
const E_FAIL: winrt::ErrorCode = winrt::ErrorCode(0x80004005);
let e = winrt::Error::new(E_FAIL, "My error message");
println!("{}", e.message());

You can use the is_ok and is_err methods to determine whether an ErrorCode represents success or failure. This is based on the structure of an HRESULT.

Thank you! WIth this error code this works. Though I tried to use other error codes (1,2,30 for example) and the default messages for these errors were printed.
So it's still unclear for me how could I know that the 0x80004005 value should be used?

Because those are all success codes. If you follow the link I shared and look at the structure of an HRESULT, you will see that bit 31 is the severity bit. If, and only if, that bit is set (0x8000_0000) will the error code represent failure rather than success.

By the way, nice game! 👍

Thank you! Will try to keep it up to developmennt of this great winrt project

Thanks, here's an example of how you might use Win2D with the latest version of winrt-rs.
https://github.com/kennykerr/win2d-rs


Add stats

Like a list of users who have it in their readme so that pull requests can be made for updating legacy links also maybe how much traffic it gets although I think there is already smth like that in there

https://github.com/max1mde/fancy-readme-stats/commit/5d775969c28fc790a97be43a81e807a3f52b1937


Fix bug in edit command

Squashed bug where the SupplyItem linked to a supplier is not updated when that supplier's name and phone are both edited in 1 command

Codecov Report

Merging #158 (321ecdd) into master (308c63d) will increase coverage by 0.02%.
The diff coverage is 83.33%.

@@             Coverage Diff              @@
##             master     #158      +/-   ##
============================================
+ Coverage     69.87%   69.90%   +0.02%
  Complexity      705      705
============================================
  Files           111      111
  Lines          2440     2442       +2
  Branches        293      293
============================================
+ Hits           1705     1707       +2
  Misses          625      625
  Partials        110      110

Impacted Files
Coverage Δ

...java/seedu/address/logic/commands/EditCommand.java
93.50% <50.00%> (ø)

...ddress/logic/commands/EditItemSupplierCommand.java
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


ICU-656 Used markdown renderer when searching for at channel in large channels

Like the server, we now use the markdown parser to strip out any text that can't trigger mentions before searching for at channel notifications. The regexes we used before had some degenerate cases that would cause the browser to lock up while they were processed, so they had to go.
Ticket Link
https://mattermost.atlassian.net/browse/ICU-656
Checklist

Added or updated unit tests (required for all new features)

@ccbrown That's a really good point. I was thinking of making it look like it does on screen, but that doesn't make sense for mentions


WSL 2 Nginx Connection Refused For Browsers and Telnet but Allows cURL

Environment
Windows build number: Microsoft Windows [Version 10.0.19041.508]
Your Distribution version: Ubuntu 20.04 LTS
WSL Version: WSL 2
Linux version 4.19.84-microsoft-standard (oe-user@oe-host) (gcc version 8.2.0 (GCC)) #1 SMP Wed Nov 13 11:44:37 UTC 2019
Steps to reproduce
Nginx doesn't allow connection to any browser suddenly. This morning it was working fine.
$sudo service nginx start

This starts normally but all connections are refused
on Google Chrome

Telnet
telnet localhost gives me
Trying <IP_ADDRESS>...
telnet: Unable to connect to remote host: Connection refused

cURL
curl localhost gives me
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Nothing on access.log and error.log of nginx

WSL logs:
Expected behavior
When Nginx is running, it should be serving the page.

Actual behavior

Connection refused for all browser and telnet connections.

Tried rebooting the machine several times but the issue remained the same. Not sure if Windows preserves the state of WSL during subsequent boots.
However, shutting down the WSL from PowerShell manually and reopening the WSL shell again solved the problem
This is what I did

Closed the WSL sell
Shutdown the WSL from PowerShell wsl --shutdown
Reopened the WSL shell
Started the nginx and other services like before and everything worked just fine


Implement CSS library, decide which library and stuff, get it working

For the CSS we will be using Tailwind, to save us the frontend headaches. Any customization we will have to create overrides or a theme for it.
https://tailwindcss.com/

sweet


Nut leaf blocks not having item form causing issues

Issue is especially apparent when using Immersive Weathering, game crashes when it attempts to show the nut leaf variant of the leaf pile item.

This is coming in the next update, thank you for your feedback!

Should be fixed now!


Add support for sodium mod

Noticed when trying out the mod is was only partially compatible with sodium. Colored Chests rendered properly but it seemed as though the redirect in the SectionBuilderMixin was never getting called to render the colored Barrels.
There is probably a better place for this mixin, but it does not help that sodium is in the middle of package renaming. Also new to modding and render is very confusing.
Working with Sodium

Oh, that's really nice. I will test that in a few hours and merge it


[Question] Can i use User object replace for Accounts.users ?

I use many fields with user. so how to combine or replace Accounts.createUser() with User class created by astronomy ?
Meteor standard have Meteor.loginWithPassword, Meteor.loginWithFacebook .... so can i handle this with User class ?

The accounts package operates on plain JS objects so if you want to use Astronomy with it you have to give it back plain object using the raw method.
// Create Astronomy document using raw object.
const user = new User(rawUserObject);
// Get back raw object from Astronomy document.
user.raw();

yep, so how to validate user when i use Accounts.createUser by using User class ?
currently, i validate by hand:
if (!user.username)
...
if (user.point === 0)
...

and validate function in User class is client side right ?
Have any way i use it in server ?

You don't perform validation in the Accounts.createUser method. Instead you should use the Accounts.onCreateUser hook.
Accounts.onCreateUser(function(options, rawUser) {
  const user = new User(rawUser);
  user.validate();
  return user.raw();
});

It will be even easier with the new version that is comming
Accounts.onCreateUser(function(options, user) {
  User.validate(user);
  return user;
});

thanks @jagi  so much, i think this must be in Document Page :+1:


unexpected status code 200 while pushing to pushgateway

Describe the bug
the issue with the unexpected status code 200 is back: https://github.com/vshn/k8up/issues/106
Logs
If applicable, add logs to help explain your problem.
I0312 12:37:07.416570       1 handler.go:44] wrestic/statsHandler/promStats "level"=0 "msg"="sending prometheus stats"  "url"="http://prometheus-pushgateway.monitoring.svc.cluster.local:9091"
E0312 12:37:07.421030       1 backup.go:96] wrestic "msg"="prometheus send failed" "error"="unexpected status code 200 while pushing to http://prometheus-pushgateway.monitoring.svc.cluster.local:9091/metrics/job/restic_backup/instance/backup: "
I0312 12:37:07.421070       1 main.go:177] wrestic "level"=0 "msg"="all pod commands have finished successfully"

Environment (please complete the following information):

Image Version: e.g. v1.0.3
k3s version v1.20.4+k3s1 (838a906a)
go version go1.15.8

Hi @gi8lino
Thanks for reporting this!
That's odd, the fix for this has been merged a long time ago and the tag worked for you then.
We may have to check if some commit slipped in that changed the prometheus dependencies.

It turns out the PR that should have fixed this (https://github.com/vshn/wrestic/pull/23) was never actually merged. A more recent PR (https://github.com/vshn/wrestic/pull/65) has now been merged instead. I don't have information on when a new restic release will be released.
We have to see whether we try to include improvements to the parsing of the restic output in the next release as well – or if we do a release in the meantime.
@Kidswiss maybe you have more to say on this topic?

Thanks for your feedback


some parameter explaination still are ambiguous

[Enter feedback here]
as to this command :
az network vpn-site update
one parameter : --address-prefixes
this is the explanation from microsoft:
--address-prefixes
Space-separated list of CIDR address prefixes.
this is the address of remote VPN site prefixes or local prefixes?
I suggest that you can draw a topology , every explaination is based on the topology IP. So it will be clear to reader
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 8bc92fbe-8731-dc15-c23e-5b58163ee03a
Version Independent ID: 48314a31-ffc3-6896-38c2-aa3fa811c1af
Content: az network vpn-site
Content Source: latest/docs-ref-autogen/ext/virtual-wan/network/vpn-site.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S176

@andywangqt Could you explain more plain about what you wish us to improve?

Closed as inactive


ENH: Add @Metric ... where you want to only time a few (of many) methods on a class

@Timed on a class means collect metrics on all the public methods by default. Which means you need to put @NotTimed on lots of methods.
It would be better to have a @Metric on the class which means this class is interesting but only add metrics on methods that have the explicit @Timed on them.

Hmmm.  Haven't really need this to date.  Closing for now.


Empty State desktop image is empty

The Empty State desktop image is empty. As far as I see it points to https://raw.githubusercontent.com/MicrosoftDocs/msteams-docs/master/msteams-platform/assets/images/ui-templates/empty-state.png, but that image is empty.
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e739fdd6-8835-cfcd-f25c-1b4c7cb42afa
Version Independent ID: 3bbef1d2-6427-0c7f-bfe2-57bf016629da
Content: Designing your app with UI templates - Teams
Content Source: msteams-platform/concepts/design/design-teams-app-ui-templates.md
Product: msteams
GitHub Login: @heath-hamilton
Microsoft Alias: lajanuar

Hi @luismanez - Which image you are referring about? Is there any image in the doc that you are not able to view? Could you please explain your scenario in more detail?

Hi @Nikitha-MSFT,
In this link: https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/design/design-teams-app-ui-templates?tabs=desktop
In the section "Empty state -> Top use cases", the image is not appearing, as you can see in the screenshot below:

As far as I see in source code (github), the linked image is:
https://raw.githubusercontent.com/MicrosoftDocs/msteams-docs/master/msteams-platform/assets/images/ui-templates/empty-state.png
but that .png, is an empty image.
Hope it helps.

Thank you for Reporting the issue. Added the required doc labels, the Tech writing team will be followup.


Need to un-nest many properties

Resolution of namespaces when deeply nested requires module aliasing, and in cases like this can't be resolved properly.
Need to figure out the best way to preserve fluent api while removing nesting as much as possible. May be able to do something similar to this on a larger scale.

Redesigned the code generation to fix all of the namespace collisions. It's going to be less safe than before, but at least it works. 🙃

Nice!


Update README.md

Pull Request (PR) description

Updated the section Installation.

This Pull Request (PR) fixes the following issues

Task list

[ ] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #1233 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##            dev   #1233   +/-   ##
====================================
  Coverage    97%     97%
====================================
  Files        34      34
  Lines      4171    4171
====================================
  Hits       4083    4083
  Misses       88      88


Running it with a very long text prompt (or large number of classes)

Hello, I'm trying to run the object detection workflow using Grounding Dino SwinB model (groundingdino_swinb_cogcoor)
and I'm having 1000+ classes in my dataset (LVIS). When passing the text prompt and image to the model for forward pass, I'm getting this output:

Token indices sequence length is longer than the specified maximum sequence length for this model (4283 > 512). Running this sequence through the model will result in indexing errors

Does it mean that the inference will not be working properly when we have LVIS classes? Is there any workaround for it so that I'm still able to use all the classes in the text prompts and get results on LVIS?

Hello, I'm trying to run the object detection workflow using Grounding Dino SwinB model (groundingdino_swinb_cogcoor) and I'm having 1000+ classes in my dataset (LVIS). When passing the text prompt and image to the model for forward pass, I'm getting this output:

Token indices sequence length is longer than the specified maximum sequence length for this model (4283 > 512). Running this sequence through the model will result in indexing errors

Does it mean that the inference will not be working properly when we have LVIS classes? Is there any workaround for it so that I'm still able to use all the classes in the text prompts and get results on LVIS?

GroundingDINO did not support such a long text prompt for inference, you can split LVIS classes into different parts and running more than one forward pass

Ahh I see, thank you for the confirmation. I was also planning on doing just that... splitting the LVIS classes so that it fits into the text prompt and then running multiple forward passes covering all the classes...
I would be closing this issue since you have made it clear.

Hi! Sorry, just to confirm if I have understood it properly:

the maximum number of tokens to use in the input text sequence is [256] (max_text_len)
the maximum number of objects that can be detected in a single image are 900 (num_query)

am I right?
Thanks in advance!

Hi Daniel,
I believe you are correct. Thus we would need to split the class text prompt if it becomes too large. I'm splitting the classes by length of 81 each time, and using the zero-shot evaluation code uploaded by the authors @rentainhe @SlongLiu, and modified it for evaluating on LVIS.
Thanks,

Thanks @rohit901!

@rohit901 If you don't mind can you please share your evaluation code for this?

Sure, you can find it in my recent project's repo:https://github.com/rohit901/cooperative-foundational-models
could you please star the repo and spread the word about it, it would mean a lot!


Interactive

All the necessary requirements have been implemented:

Add a new JavaScript file and import it as a module. It contains methods related to the status update: completed: true/false
Add event listener to the checkbox (change).
Update items object's value for completed key upon user actions.
Store the updated array of items in local storage, so the user gets the correct list values after the page reloads.

None of the additional requirements (optional) have been implemented. They might be implemented in the next pull request.

Hi, @BrianSammit . Thanks for your review. The application was working on my local machine, otherwise, I would not send it to you. When you show me this snapshot, my colleagues and I, find out that I do not store the to-do list first. That is why the items did not show at the beginning. They were working on my machine because I had the data on my localStorage.
Now the changes to call storeStatus() have been introduced and everything works fine.

Thanks for the fast review!


How to package and distribute ?

How can we package and distribute the app made with guietta ?
I was able to build a GUI in no more than 2 hours, this is incredible, thks !!!!
Now we need to build a binary (for OSX) and distribute to our (internal) users.
Thanks

that was super easy, too :
https://doc.qt.io/qtforpython/deployment-pyinstaller.html

Hello @odeckmyn, good that you found something that works! I might even mention it in the tutorial. Since it is advice that comes directly from QT, I guess that it can be trusted :)


follow_me: fix double sending of location

We changed the behavior of add_call_every a while ago. It now triggeres immedately as well as later. This means that the manual immediate trigger is no longer necessary. Otherwise, this leads to weird double bursts.

Now sometimes 1-2 messages go missing and never arrive :/


Too much space between paragraphs in IEEE conference.

There should not be additional space between paragraphs in the IEEE conference papers.

Do you have a MWE for testing?

I'm not sure what you mean by MWE. I'm comparing to standard IEEE papers visually. I also gutted the standard IEEE bare_conf.tex, symlinked to my sections, and included them in that as a shell, and the two visually look different. I think there's also a line spacing difference, but I could be wrong.

Minimum Working Example - something I can throw in a scriptorium setup to test and compare

From my testing with scriptorium, there's something subtle going on with how \parskip is set in your example, but it seems to be using the same value. Adding \parskip 0ex removes the rubber spacing IEEEtran specifies and uses in both cases, eliminating the spacing in some place, but not changing the length of the paper. Instead, the columns end up slightly more ragged than when the rubber spacing exists.
I can't find anything other than overriding the IEEE formatting to eliminate this - removing biber, dropping a large number of packages, and hard-coding the variable names doesn't seem to have any impact on the spacing. There are some generic references to older versions of IEEEtran exhibiting this problem - have you checked that you don't have an old version installed somewhere?

Is this fixed by using the ieeeconf template in #27?

It appears to be!


cookieSignatureKeys configuration

Hello, everyone.
This is not an issue, but I'm not sure about where I should ask this. I'm a little bit lost.
It's about cookieSignatureKeys, in the examples I've seen always an array of two strings "secret1" and "secret2" in server config, but...
what kind of secret should I create, how and how many? I cannot use env variables, right? Because keys are used by middleware and it's not running into a NodeJS environment.
But if I have to add them in the source code, it's not a bad practice?
Sorry for the issue and I'll be waiting for anyone who can help me.
Thank you so much!!
PD: is it ok to open an issue for these questions, or should I avoid this?

Update: I just see that in the example project, middleware uses env variables, so I think I can use env variables to set secrets, right? I thought it could only be used in a NodeJS environment, but I think I was wrong.
But, I still want to know how many secrets I have to create and what kind of secrets? And with what tool could I do that?
Thanks!

PD: is it ok to open an issue for these questions, or should I avoid this?

I more than encourage you to ask those questions here :-) A lot of users would search for an answer, but refrain to create an issue if they don't find one. Asking questions will help you and other people looking for similar answer, so it's more than okay to ask them. Thanks!

Thank you so much, Amadeusz! Your explanation was perfect. I completely understand the importance of keys and how I can use them.
Now, I was thinking of asking another question about something I observed in my tests with this library. However, now that you mentioned that any cookie signed with the latter will be considered invalid and user will be forced to login page, I think this is a good opportunity to ask.
Let's suppose a cookie is removed (due to expiration, for example, or because the previous cookie signature key was deleted). If a user enters the web, initially the cookie won't be there. However, the onIdTokenChange method will be automatically executed, setting the cookies again, and the user will remain logged in. However, the user might find a weird situation because when they initially enter the page, the middleware checks cookies and redirects to the login page. Then, the client component reads the Firebase token (since it's still present) and sets the cookie again without requiring a login.
Is there, maybe, a way to also remove the Firebase token in storage when a cookie is removed (I mean, just if I should do something like that and I'm not currently doing it, I don't want to overthink these situation), or something similar? Or is this behavior acceptable? What's the correct approach in this scenario?
My primary concern revolves around user experience. It would be akward to user to be redirected to the login page only to discover that the user is still logged in... Am I mistaken?
I'm not sure if I've explained this very well. Please let me know if I haven't. My apologies, my English is not the best 😬.

@FacundoRaviolo
When user cookies expire, but firebase is still logged-in using browser storage, user will be redirected to /login page, just to be redirected back to desired page. This is how starter example works, where this kind of flow is expected.
The solution I see here is changing default [Authentication State Persistence] in Firebase Client – https://firebase.google.com/docs/auth/web/auth-state-persistence to inMemoryPersistence, but you would have to deviate from original example a bit and call /api/login and /api/logut outside of AuthProvider
I actually added an issue on this couple weeks back to explore this topic: https://github.com/awinogrodzki/next-firebase-auth-edge/issues/143

Thank you so much again!
I now understand.
Yeah, in the meanwhile my app can works like starter example. It's weird to be redirected to login and back again but it's something that happens a few times.
About the topic, I will think about it and try when I can.
But that's it. I just wanted to check if I was wrong.
Thank you, again, these answers were perfect.
And also thank you so much for this awesome library!


Update hello-world.md

add a space before colon in "godoc -http:8000", the correct command is "godoc -http :8000"

A space is crucial. This is the original repo quli/learn-go-with-tests/hello-world.md. godoc -http:8000 got an error which said "flag provided but not defined: -http:8000". This command should be modified to godoc -http :8000 or godoc -http=localhost:8000 .


Does expectFail catch not all inputs have been set error?

Try for a circuit with many signals (like >10)

Indeed it doesn't catch it! Added fix.


Adding expression(regEx) to query

In Step 1: Create a data source:
Can i add  an expression like /cv/.* in query or it has to be a relative path.
I mean in container >> query

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b32a534c-4c64-3e08-824a-cd298cd43022
Version Independent ID: c0a0ac07-8e05-011f-ee31-e063854f3162
Content: Indexing JSON blobs with Azure Search blob indexer
Content Source: articles/search/search-howto-index-json-blobs.md
Service: search
GitHub Login: @mgottein
Microsoft Alias: magottei

@ajamaeen Thank you for the detailed feedback. We are actively investigating and will get back to you soon.

@ajamaeen Thank you for your question. It is suggested to use the relative path within Azure Search environments.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Last available subnet within a space

Good day,
Thanks for all the nice work done with the solidserver provider.
I have a feature request, for being able to get last available subnet within a space when using the solidserver_ip_subnet module.
I know it probably makes more sense to abstract yourself from that kind of structure once you go IaC, but as of now it would be a nice feature for us.
Br
Jørgen

Hello Jørgen,
Could you please clarify your request, what exactly do you define as the "Last available subnet within a space" ?
If you have an example, I'm interested. I'm not sure we have the same definition in mind.
Thanks in advance.
Kind regards

Hello,
Sorry for being unprecise.
Say you have a /23 subnet: <IP_ADDRESS>/23.
If you split this into two /24 subnets, you'll get:
First subnet: <IP_ADDRESS>/24
Last subnet: <IP_ADDRESS>/24
So what I mean is that I want to be able to acquire the "last" subnet in this range.
Usually when we build new things we aim to have the server subnets first in the range and the link-nets etc in the end of the range.
Hope that clears things up.
Best regards.

Hello,
Unfortunately, the SOLIDserver API (/rpc/rpc/ip_find_free_subnet) that returns the  best matches intends to minimize
the fragmentation of the IP space and therefore only returns available subnets from the beginning of the prefix.
Implementing this logic from within the provider would not make sense, this 'feature' needs to be implemented in the SOLIDserver API itself.
Kind regards.


[Feature Request] [Kernel] Selectively choose whether to or not to read the AddFile stats during LogReplay

We want to have the thinnest, most-lightweight read schema during LogReplay (parsing AddFiles and RemoveFiles, to yield the active add files in the table).
Thus, we should only read the AddFile statistics field when

there exists a query filter, and
the connector is able to evaluate the stats-min/max etc. query (used to perform data skipping for that input query filter)

If either of 1 or 2 is false, then we should skip reading the add file stats column during LogReplay json/checkpoint parsing.

This doesn't yet seem relevant for 3.0 since the 3.0 delta-kernel release won't contain any stats-based column pruning. Thus there's no reason to read the stats in the first place, which is what delta-kernel is currently doing.

Closed in 09b6dc5 and 1f7a475


doc(realtimemonitoring): Adding a process to connect gatling to influ…

The current documentation is working only for the previous version of Ifnluxdb 1. X.
No need Grafana. With version 2 of influxdb, you need to use telegraf to load your data from graphite, and you can now create your dashboard in Influxdb directly.  If you need grafana, you can also connect grafana to influxdb 2.0 to use a flux connection.

@yankoho Thanks for contributing.
Actually, I'm wondering if we shouldn't simply have pointer to the official InfluxDB documentation instead of maintaining our own tutorials for a third-party technology.
WDYT?

Sorry, but indeed, I went with removing any third party specific tutorial.
Thanks anyway.


Incorrect location indicator in settings page due to disabled location permission.

Location indicator is set properly in the settings page.

Closing as this is no longer relevant with the work being done in #945


Question: authentication failed when connecting to vagrant

I am trying to connect to a vagrant setup. The ssh config is like:
Host default
  HostName <IP_ADDRESS>
  User vagrant
  Port 2200
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile /home/arkaroy/src/.vagrant/machines/default/virtualbox/private_key
  IdentitiesOnly yes
  LogLevel FATAL

I have put the config in ~/.ssh/config and the entry is correctly displayed under ssh targets of remote explorer. But I am getting error when trying to connect to the vagrant instance.
[Info  - 18:09:27.153] Resolving ssh remote authority 'ssh-remote+default' (attemp #1)
[Trace  - 18:09:27.170] Identity keys:
None
[Info  - 18:09:27.199] Trying no-auth authentication
[Error  - 18:09:27.213] Error resolving authority
Error: All configured authentication methods failed
	at _e (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:140706)
	at /home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:380002
	at authHandler (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:375630)
	at me (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:143579)
	at USERAUTH_FAILURE (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:132406)
	at 51 (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:283888)
	at e.exports.x (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:154321)
	at x.decrypt (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:247473)
	at e.exports.D [as _parse] (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:153845)
	at e.exports.parse (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:157648)
	at Socket.<anonymous> (/home/arkaroy/.vscode-oss/extensions/jeanp413.open-remote-ssh-0.0.17-universal/out/extension.js:1:139446)
	at Socket.emit (node:events:526:28)
	at Socket.emit (node:domain:475:12)
	at addChunk (node:internal/streams/readable:315:12)
	at readableAddChunk (node:internal/streams/readable:289:9)
	at Readable.push (node:internal/streams/readable:228:10)
	at TCP.onStreamRead (node:internal/stream_base_commons:190:23)

Any guidance in the right direction would be much appreciated.

@iarkaroy seems the extension can't find your ssh key, internally it reads the public key by appending .pub if necessary, does /home/arkaroy/src/.vagrant/machines/default/virtualbox/private_key.pub exists?

No. The file is just private_key, not private_key.pub. What can I do to
make it work?
On Sat, Oct 22, 2022, 01:14 Jean Pierre @.***> wrote:

@iarkaroy https://github.com/iarkaroy seems the extension can't find
your ssh key, internally it reads the public key by appending .pub if
necessary, does
/home/arkaroy/src/.vagrant/machines/default/virtualbox/private_key.pub
exists?
—
Reply to this email directly, view it on GitHub
https://github.com/jeanp413/open-remote-ssh/issues/29#issuecomment-1287369317,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB4CEQ6OIVJPGAB72NWEWG3WELXCHANCNFSM6AAAAAARLNXSHI
.
You are receiving this because you were mentioned.Message ID:
@.***>

As far as I know ssh keys are generated in pair, private and public, not sure why you don't have the public key but in any case just generate it.

The key generation is handled by vagrant itself. As per the article https://medium.com/@lizrice/ssh-to-vagrant-from-vscode-5b2c5996bc0e, this is how it is supposed to work. And as per the article, it works with https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh extension. But I am using vscodium.

I see, does the vagrant ssh key has a passphrase? if it doesn't, I can push a quick fix but if it does has passphrase it would be more complicated.
I plan to do the same thing as the official extension and use the ssh binary directly instead of using the a ssh library to avoid worrying about this

No. The ssh key does not have a passphrase. The vagrant ssh flow is meant to be without any manual intervention. So I suppose vagrant setup never use passphrase for ssh connection. I would be super useful if this can do the same thing as the official extension. Thanks for all the work you have done.

@iarkaroy published version 0.0.18 could test if it works now :pray:

Yes. It is connecting properly now. Thanks a lot.