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

Dashboards and Charts drop a red 'Unexpected error' message when user is anonymous #16507

Closed
3 tasks done
trepmag opened this issue Aug 30, 2021 · 4 comments
Closed
3 tasks done
Labels
#bug Bug report

Comments

@trepmag
Copy link
Contributor

trepmag commented Aug 30, 2021

This issue happens when user is anonymous.

Expected results

List of public dashboards or charts

Actual results

Red 'Unexpected error' message

Screenshots

Selection_343

How to reproduce the bug

  1. Add dashbords and charts and set access to public
  2. Browse dashboards or charts unconnected (anonymous)
  3. See the error as show in the screenshot

Environment

  • superset version: 1.3.0
  • python version: as distributed in the superset 1.3.0 image
  • node.js version: as distributed in the superset 1.3.0 image

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

This was tested with the the 1.3 branch using npm run prod and npm run dev-server

@trepmag trepmag added the #bug Bug report label Aug 30, 2021
trepmag added a commit to trepmag/superset that referenced this issue Aug 30, 2021
@mignaulo
Copy link

@trepmag This is a really great find. We also ran into this same issue. Thanks for reporting and fixing it!
I'm not sure how superset deals with external contributions, are you able to submit a PR with your code change?

@stale
Copy link

stale bot commented Apr 18, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. For admin, please label this issue .pinned to prevent stale bot from closing the issue.

@stale stale bot added the inactive Inactive for >= 30 days label Apr 18, 2022
@jhult
Copy link
Contributor

jhult commented Apr 20, 2022

Did the fix for this get merged?

@stale stale bot removed the inactive Inactive for >= 30 days label Apr 20, 2022
@rusackas
Copy link
Member

We no longer support 1.x (and will soon drop support of 2.x, as 4.0 is nearly out). If this is still a problem, I'd suggest opening a new issue. Closing this for now to work toward a more maintainable backlog.

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

Successfully merging a pull request may close this issue.

4 participants