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

Collection permissions page not working in master #4456

Closed
luissancho opened this issue Feb 28, 2017 · 5 comments · Fixed by #4476
Closed

Collection permissions page not working in master #4456

luissancho opened this issue Feb 28, 2017 · 5 comments · Fixed by #4476
Labels
Administration/Permissions Collection or Data permissions Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Type:Bug Product defects
Milestone

Comments

@luissancho
Copy link

  • Your browser and the version: Chrome 56.0
  • Your operating system: OS X 10.12.3
  • Your databases: MySQL
  • Metabase version: metabase-head:latest
  • Metabase hosting environment: Elastic Beanstalk
  • Metabase internal database: Postgres

captura de pantalla 2017-02-28 a las 12 22 17

Something went wrong in the latest realease with the collection permissions page. It was working fine in previous update.

@camsaul
Copy link
Member

camsaul commented Feb 28, 2017

@luissancho, it looks like the screenshot isn't showing up, can you post it again?

@salsakran
Copy link
Contributor

@luissancho can you post the contents of your server logs and js console when this happens?

@salsakran salsakran added Type:Bug Product defects Administration/Permissions Collection or Data permissions Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness and removed Need More Info labels Feb 28, 2017
@salsakran
Copy link
Contributor

reproduced it on our internal stats instance.

@luissancho
Copy link
Author

It seems everything is working well in terms of queries. This is the log:

Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/user/current 200 (2 ms) (1 DB calls)
Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/session/properties 200 (2 ms) (1 DB calls)
Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/dashboard 200 (5 ms) (2 DB calls)
Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/collection 200 (6 ms) (2 DB calls)
Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/permissions/group 200 (6 ms) (2 DB calls)
Mar 01 15:48:11 DEBUG metabase.middleware :: GET /api/collection/graph 200 (14 ms) (4 DB calls)

Chrome dev console is showing the same.

@camsaul
Copy link
Member

camsaul commented Mar 1, 2017

@salsakran should we add this to the 0.23.0 milestone? Don't want to ship the release knowing there are regressions

@salsakran salsakran added this to the 0.23.0 milestone Mar 1, 2017
@kdoh kdoh closed this as completed in #4476 Mar 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administration/Permissions Collection or Data permissions Priority:P1 Security holes w/o exploit, crashing, setup/upgrade, login, broken common features, correctness Type:Bug Product defects
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants