Add feedback component to loading page

[Etesam913]

Overview

A very common circumstance where feedback might want to be received is during loading.

There are times where a task my be stuck in loading forever. The researcher should be able to know directly if a large chunk of workers are not able to see the task.

This was brought up to me by @EricMichaelSmith

Changes:

• Feedback component shows after loading for 5 seconds (should this number be adjusted? not exactly sure about the average loading times).

Video

feedback-on-loading.mp4

[codecov-commenter]

Codecov Report

Merging #888 (abb44a8) into main (b165bb2) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #888      +/-   ##
==========================================
- Coverage   64.65%   64.60%   -0.06%     
==========================================
  Files         108      108              
  Lines        9312     9312              
==========================================
- Hits         6021     6016       -5     
- Misses       3291     3296       +5     

Impacted Files	Coverage Δ
mephisto/abstractions/architects/mock_architect.py	88.23% <0.00%> (-2.62%)	⬇️
mephisto/data_model/unit.py	77.59% <0.00%> (-0.55%)	⬇️

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

[Etesam913]

@EricMichaelSmith Is this kind of what you expected?

[JackUrb]

This is cool! Only issue is that the most common reason this happens is because the mephisto router is alive, but the Mephisto server that was associated with it no longer is connected. After #829 however then this would cover the actual loading use cases.

[EricMichaelSmith]

@EricMichaelSmith Is this kind of what you expected?

Yeah! This is really cool to see, and it'll let us get feedback about broken HITs. I feel like, in my experience, emails about broken HITs are at least as common as all other email topics put together...

[pringshia]

This is a clever use case for the new Feedback component!

I would suggest a 10 second delay, 5 seems a little too quick to me. It would also be nice to have the timeout value as a constant, and perhaps we can expose that at the top of the app.jsx file. (in the future other configurable constants could also be colocated there)

[facebook-github-bot]

Hi @Etesam913!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!