"Code promise is not resolved in noWait mode"

[Emiliano Heyns]

I have a BBT user who's getting errors because translators are not being updated; in his logs, I see "Code promise is not resolved in noWait mode". Any idea? I've not seen this before.

[Emiliano Heyns]

On Wednesday, November 29, 2017 at 6:08:59 PM UTC+1, Emiliano Heyns wrote:

I have a BBT user who's getting errors because translators are not being updated; in his logs, I see "Code promise is not resolved in noWait mode". Any idea? I've not seen this before.

I have another user who has this error (https://github.com/retorquere/zotero-better-bibtex/issues/893) which seems to interfere with the quick-copy handling. Any insights would be much appreciated -- I don't know where in Zotero this happens, nor do I know a likely cause.

[Emiliano Heyns]

I'm hitting this problem again, reproducibly. I do a Zotero.Translators.reinit(), but this does not seem to be enough. No idea what else I can do.

[Emiliano Heyns]

I don't know how the code-caching of Zotero works. I'm trying to enter the BBT translators into the cache to prevent the noWait problem.

[Emiliano Heyns]

I'm trawling through the Zotero sources, but I have not been able to find a way to make codePromise = translator.getCode() from translate.js return a pre-resolved promise. I could really use some help here.

[Dan Stillman]

On 1/26/22 4:14 PM, Emiliano Heyns wrote:
> I'm trawling through the Zotero sources, but I have not been able to
> find a way to make codePromise = translator.getCode() from
> translate.js return a pre-resolved promise. I could really use some
> help here.

The .code property of the loaded translator needs to be populated. You
can do that by pre-calling getCodeForTranslator() once with
translator.cacheCode set to true, as the Quick Copy code does:

https://github.com/zotero/zotero/blob/1743360de75beb30ef24db61b6e418de08c63c02/chrome/content/zotero/xpcom/quickCopy.js#L336-L349

[Emiliano Heyns]

That throws an

Error: TypeError: Zotero.Translators.getCodeForTranslator is not a function

for me

[Emiliano Heyns]

I can call get and reinit on Zotero.Translators, but just before I try to call getCodeForTranslators, these are the properties on Zotero.Translators: ["init","reinit","load","loadFromFile","get","getAllForType","getAll","getWebTranslatorsForLocation","getSearchURIs","getImportTranslatorsForLocation","getFileNameFromLabel","getTranslatorsDirectory","save","cacheInDB","makeTranslatorProvider"]

[Emiliano Heyns]

getCodeForTranslator seems to only exist in the beta.

[Emiliano Heyns]

Should I expect this

new Zotero.Translator({...header, cacheCode: true, code })

to cache the code for the non-beta? It does seem to work.

[Emiliano Heyns]

I have one user where I consistently get what seems to me a conflicting result from `Zotero.Translators.get` (Zotero 5.0.96.3 on Linux); `header` is a translator header JSON object;

const destFile = Zotero.getTranslatorsDirectory()

destFile.append(`${header.label}.js`)

const exists = destFile.exists()

const installed = Zotero.Translators.get(header.translatorID)

with `exists` always being true, but `installed` always being `false`. We have verified the BBT translators (which is what I'm testing for) do exist prior to start. Any idea? I cannot reproduce this myself.

[adoma...@gmail.com]

Can you post some links to your code that's responsible for handling this? There have indeed been some translation code changes between Zotero 5 and the beta, so that's likely the cause of the issue. Hard to advise without seeing the code.

[Emiliano Heyns]

It is this part:

https://github.com/retorquere/zotero-better-bibtex/blob/gh-2033/content/translators.ts#L542-L546

Given that the translators exist in the translators directory before start, I would expect (and usually see, just not for this user) Zotero.Translators.get(header.translatorID) to return non-false

[adoma...@gmail.com]

`Zotero.Translators.save()` only stores the files in the translator folder. You need to call `Translators.reinit` first (which I see you do in your own `init()` function) and then call getCodeForTranslator for all the translators that will need to have preloaded code. You should only call getCodeForTranslators() for translators that actually need the code available in noWait mode (which is primarily for things like drag-and-drop, since no async function calls are allowed to set drag and drop cntents). You can do this at a similar point in the code as we do for quickCopy - on init for the selected translator, and then on translator changes.

[Emiliano Heyns]

That's what I'm trying to achieve, but for this particular user I always get false for Zoterro.Translators.get, which I interpret as "does not exist yet". I can test for file existence, but that seems like the wrong approach.

[adoma...@gmail.com]

Is that test code being ran after Zotero.Translators.init() had finished running?

[Emiliano Heyns]

Not explicitly -- I am waiting for schemaUpdatePromise. Is there something I can await for the translators.init?

[adoma...@gmail.com]

You can await `Zotero.Translators.init()` itself, which will return a promise that is either already resolved or will resolve when translators have been initialized.

[Emiliano Heyns]

As far as I can tell this get returning false is unique to this user. I cannot reproduce this on the platforms I have access to (which includes Linux this user has)

[Emiliano Heyns]

Looks like I can just await Zotero.Translators.init() before doing anything else?

[adoma...@gmail.com]

Looks like I can just await Zotero.Translators.init() before doing anything else?

  Before doing anything with translators for sure, yes.

 

 

[Emiliano Heyns]

That fixed it. Super. This has been a long-standing annoyance in BBT, happy that that is now gone. Thanks!

[Emiliano Heyns]

turns out the problem still exists. could really use some insight to fix this. the problem is a nuisance again because note-d&d runs translators.