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

400 response when loading due to missing "tags" registry #27343

Closed
w33ble opened this issue Dec 17, 2018 · 3 comments · Fixed by #27423
Closed

400 response when loading due to missing "tags" registry #27343

w33ble opened this issue Dec 17, 2018 · 3 comments · Fixed by #27423
Assignees
Labels
bug Fixes for quality problems that affect the customer experience PR sent Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas Team:Visualizations Visualization editors, elastic-charts and infrastructure

Comments

@w33ble
Copy link
Contributor

w33ble commented Dec 17, 2018

Kibana version: 6.6+

Describe the bug:

When loading Canvas (or Kibana in general, thanks to #27175) and the socket is started, there's a lone 400 response related to a "tags" registry.

Not sure if this was introduced as part of #26068 or if the issue existed before it. I also couldn't tell at a quick glance why it's trying to load tags.

Steps to reproduce:

  1. Open debugger console
  2. Load Kibana (or Canvas once [Regression] Socket connection is always created #27175 is fixed)

Screenshots (if relevant):

screenshot 2018-12-17 13 54 02

GET http://localhost:5601/ztz/api/canvas/plugins?type=tags net::ERR_ABORTED 400 (Bad Request)

@w33ble w33ble added bug Fixes for quality problems that affect the customer experience Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas Team:Visualizations Visualization editors, elastic-charts and infrastructure labels Dec 17, 2018
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-canvas

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-app

@w33ble
Copy link
Contributor Author

w33ble commented Dec 17, 2018

I believe this is what's causing the error, but I haven't dug into why the registry isn't exposed via the endpoint.

@cqliu1 cqliu1 self-assigned this Dec 17, 2018
@w33ble w33ble added the PR sent label Dec 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience PR sent Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas Team:Visualizations Visualization editors, elastic-charts and infrastructure
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants