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

[async] error: component not found for job <id> #12913

Closed
3 tasks done
rwspielman opened this issue Feb 3, 2021 · 2 comments · Fixed by #13350
Closed
3 tasks done

[async] error: component not found for job <id> #12913

rwspielman opened this issue Feb 3, 2021 · 2 comments · Fixed by #13350
Assignees
Labels
assigned:preset Assigned to the Preset team global:async-query Related to Async Queries feature

Comments

@rwspielman
Copy link
Contributor

We are sporadically seeing the error 'component not found for job ' in the dev console when loading dashboards with Global Async turned on. The charts never loads. When searching through the network requests, we can see that the api request to async_event does in fact return the correct job and we can follow the result_url in that api response to the data of the missing chart. It does not make a call to the explore_json/data api for that chart.

Just a shot in the dark: My thoughts are possibly a race condition between loading of the ui components and the return of the api response? It seems to always be the first charts that return from async_result api (and usually in a separate request from the others that do end up loading)

Expected results

Charts to load properly

Actual results

Chart never loads, and error 'component not found for job ' warning in console.

Screenshots

Screen Shot 2021-02-03 at 12 12 58 AM

Screen Shot 2021-02-03 at 12 13 51 AM

How to reproduce the bug

  1. Turn on Global Async
  2. Create dashboard/charts
  3. load dashboard
  4. reload dashboard after cache
  5. may need to refresh a couple of times and wait for a chart to continuously have the spinning loader / the error in the console show up. it is very sporadic

Environment

(please complete the following information):

  • superset version: master 9fa52d3
  • python version: 3.8
  • node.js version: 12

postgres backend
redis cache storage
redis async storage

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@rwspielman rwspielman added the #bug Bug report label Feb 3, 2021
@rwspielman
Copy link
Contributor Author

FYI @robdiciuccio - I saw you were in charge of the async feature commits

@junlincc junlincc added global:async-query Related to Async Queries feature and removed #bug Bug report labels Feb 4, 2021
@robdiciuccio robdiciuccio self-assigned this Feb 20, 2021
@robdiciuccio robdiciuccio added the assigned:preset Assigned to the Preset team label Feb 25, 2021
@robdiciuccio
Copy link
Member

@rwspielman can you test the fix in #13350 to see if that resolves your issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
assigned:preset Assigned to the Preset team global:async-query Related to Async Queries feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants