-
Notifications
You must be signed in to change notification settings - Fork 18
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
Translator tester: Only test URL-specified translators when ready. #21
Open
zoe-translates
wants to merge
1
commit into
zotero:master
Choose a base branch
from
zoe-translates:run-url-specified-tests-after-translators-ready
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works, but it isn't very good IMO to depend on non-obvious promise behavior.
When you call a function that returns a promise, the code in that function starts executing immediately. It only pauses on the first
await
. In this case, itawait
s pretty early on and we don'tawait
anything in this function between here and the newPromise.all()
, so everything works as expected, but that's pretty fragile. IfhaveTranslators()
should only run oncetranslatorTestViewsToRun
is ready, we shouldn't call it at all until that's the case.So instead we could do something like
and below:
(That change also makes the different translator types run sequentially instead of in parallel, which is probably more what we want here.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about reverting this change, and simply do (pseudo-javascript)
on this line? This too works, and it's shorter.
I think here, it's not that
haveTranslators()
has to run aftertranslatorTestViewsToRun
is ready. ActuallyhaveTranslators()
is the function that makestranslatorTestViewsToRun
ready by populating it.The problems in
init()
, on the line 428 withawait Promise.all(... big arrow function)
, is that the arrow function creates runaway promises. In each loop in.map()
the async arrow function calls the promise-returninghaveTranslators()
, forgets about it, and immediately returns (a promise that resolves to)undefined
. So theawait Promise.all()
doesn't wait for the promises that do the actual work, only the promises that initiate the work (results of calling the arrow function). That's why thisawait Promise.all(...)
resumes prematurely.