-
Notifications
You must be signed in to change notification settings - Fork 77
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
Fixing parlai onboarding #439
Conversation
done_act = agent.act() | ||
if done_act is not None: | ||
break | ||
time.sleep(0.3) |
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.
question: could we have this as a variable in case we wanted to find the optimal value?
The code looks good to me. I tried this in mock, sandbox and live. Mock worked well. In sandbox, when it was transitioning it looked like it was refreshing a bit too long, but it was generally good. The live (prod) version is going fine but a bit too slow (that might be related to other factors though). |
c74f1e9
to
d222f4d
Compare
d0a6231
to
352aa28
Compare
Codecov Report
@@ Coverage Diff @@
## mturk-hit-sync-speedup #439 +/- ##
==========================================================
+ Coverage 65.95% 66.07% +0.11%
==========================================================
Files 78 78
Lines 7084 7097 +13
==========================================================
+ Hits 4672 4689 +17
+ Misses 2412 2408 -4
Continue to review full report at Codecov.
|
…into fixing-parlai-onboarding
Overview
#421 included a bug for specific cases of
ParlAIBlueprint
onboarding. This fix resolves the issue, and also resolves an issue where the timeout status wasn't being pushed forward in onboarding.Details
#421 introduced a bug specifically for
ParlAIBlueprint
onboarding worlds, as theParlAIBlueprint
is the only type of live task wherein either the backend (theWorld
) or the frontend (viahandleSubmit
) can submit the onboarding. In the case that the world exited cleanly, this would lead to a message to the frontend telling it to submit.Unfortunately, #421 improved the onboarding flow to ensure that the transition from running onboarding to registering would happen in the same order every time. Specifically, the requirement is that
_on_submit_onboarding
now has to trigger the termination of the onboarding runner. In the case where the backend triggered this for parlai onboarding by just exiting an onboarding world, that wasn't the order things happened in.This updates the
ParlAChatITaskRunner
to first mark the agent as done, then wait for the submit packet (to come through_on_submit_onboarding
before terminating.Testing
Launched a task world with onboarding worlds that submit on the backend, was able to transition into the main world with no refreshes, no disconnects, and no other behavior.
Launched a task world with onboarding, timed out, then ensured the timeout was pushed to the frontend.