Skip to content
#

dashboard

Here are 5,181 public repositories matching this topic...

netdata
grafana
kvrhdn
kvrhdn commented May 28, 2021

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

strapi
hkovacs
hkovacs commented Jun 22, 2020

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

directus
rijkvanzanten
rijkvanzanten commented Jun 17, 2021

When upgrading Directus, there might a (couple) migration(s) that have to be run in order to get the database up to speed with the latest version of Directus itself. When the API is started up, we should check and show a warning when the migrations required for the latest version haven't been applied (yet).

This should also prevent a lot of "Help my app shows error XYZ after upgrading Directus"

chatwoot
sojan-official
sojan-official commented May 24, 2021

When sending an SMS response in Chatwoot, I am character limited to 140 or whatever. However, when I go to "New message" via the contacts panel, I am not character limited, and I was able to send a 300 character test message out. This is an inconsistency in the UI, and not sure why do the character limit, if we can successfully send larger messages

ref: https://discord.com/channels/6474125452

bandwhich
llchan
llchan commented Mar 31, 2020

It would be useful to be able to toggle/flag into a process-level mode to group by pid and display more process-level information like the full command line.

  • For the "Utilization by process name" window, we could group by pid rather than process name so that it's easier to find specific heavy network resource consumers.
  • For the "Utilization by connection" window, including the pid + cmdlin

Improve this page

Add a description, image, and links to the dashboard topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the dashboard topic, visit your repo's landing page and select "manage topics."

Learn more