Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReferenceError: requestText is not defined #163

Open
stefan-sigle opened this issue Feb 13, 2024 · 2 comments
Open

ReferenceError: requestText is not defined #163

stefan-sigle opened this issue Feb 13, 2024 · 2 comments

Comments

@stefan-sigle
Copy link

stefan-sigle commented Feb 13, 2024

Running Zotero translate server latest via docker-compose. Worked out perfectly until yesterday, but now does not resolve any DOI identifiers anymore. PMIDs are working fine still.

Request is a POST on http://localhost:1969/search with a DOI like 10.1200/JCO.2023.41.17_suppl.LBA3000

Logs are the following:

(3)(+0000001): Translate: All translator detect calls and RPC calls complete:

(3)(+0000000): 	DOI Content Negotiation: 100

(3)(+0000000): 	mEDRA: 105

(5)(+0000000): Translate: Running handler 0 for translators

(4)(+0000001): Translate: Parsing code for DOI Content Negotiation (b28d0d42-8549-4c6d-83fc-8382874a5cb9, 2023-09-22 09:54:11)

(3)(+0000000): Translate: Beginning translation with DOI Content Negotiation

(node:62) UnhandledPromiseRejectionWarning: ReferenceError: requestText is not defined
    at processDOI (eval at <anonymous> (/app/src/translation/sandboxManager.js:70:4), <anonymous>:67:17)
    at doSearch (eval at <anonymous> (/app/src/translation/sandboxManager.js:70:4), <anonymous>:62:9)
    at Zotero.Translate.Search.rest (/app/modules/zotero/chrome/content/zotero/xpcom/translation/translate.js:1406:49)
    at loadPromise.then (/app/modules/zotero/chrome/content/zotero/xpcom/translation/translate.js:1396:39)
    at process._tickCallback (internal/process/next_tick.js:68:7)
(node:62) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)

Are we rate limited for DOI lookups or anything? Does anybody else have trouble?

@stefan-sigle
Copy link
Author

Update: so i build the docker image locally and it works like a charm.

@dstillman
Copy link
Member

Sorry, we haven't pushed an updated version to Docker Hub in a few years. We'll try to get to that soon. In the meantime, latest code in git should work fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants