dashboards

When a user searches for a value on the cases list page the UI does not pass any search_fields value. This causes Elasticsearch to query all available fields within the case saved object. This could cause some confusion as to why some cases are returned in the search results because we don't display all the data from a case in the UI.

References: https://github.com/elastic/kibana/blob/main/x-

README.md is still pointing to addons/strip-limits.libsonnet addon as a way to strip containers from set resource limits. However since release-0.8 resource requests are first-level settings and users should use

When you open page UI Elements -> Cards i see TABS are not showing content until you click on other and back on first, same for pills.

Possible fix : ( worked for me )

<script type="text/javascript"> $(document).ready(function(){ $('.nav-item').tab('show'); $('.nav-tabs li a:first').trigger('click'); }); </script>

ALL software version info

Panel 0.13.1

Description of expected behavior and the observed behavior

Setting PANEL_OAUTH_PROVIDER is ignored, authentication is only used when passing --oauth-provider to panel serve. The authentication user guide suggests otherwise
"the oauth_provider can be set on the commandline using the --oauth-provider CLI argument to panel serve or the

https://grafana.com/docs/grafana/latest/panels/field-overrides/

Dash 2.1.0 added shorthand support for dcc.Dropdown, dcc.Checklist and dcc.RadioItems. It would be good to support the same syntax with dbc.Select, dbc.Checklist and dbc.RadioItems respectively.

See community post and [corresponding pull request](https://github.com/plotly/da