Sergej Herbert
Sergej Herbert
### Description I am developing a backend for a fixed client (grafana simpod json datasource). One of the endpoints is a post request with an empty body (see below). Sadly...
Hi, sadly I am only a user of an OPC/UA server and neither an expert nor its administrator. But I had the following problem using a CLI tool I built...
Since [this PR](https://github.com/mattn/go-sqlite3/pull/926) the underlying version of SQLite should be >=3.35 (and it is). The PR even mentions the new maths function added. However, when I try to use math...
**Describe the bug** A clear and concise description of what the bug is. The initial issue was raised in the Grafana community: - https://community.grafana.com/t/legend-names-for-graphs-appear-double/61069 - https://community.grafana.com/t/legend-appears-twice-when-i-have-data-sources-on-one-graph/70780
As the version contains an "rc-X" suffix the changelog is not correctly parsed into the release notes during the Github Actions build process.
### Initial Checks - [X] I have searched GitHub for a duplicate issue and I'm sure this is something new - [X] I have searched Google & StackOverflow for a...
Grafana updated their alerting and moving to the new version should make sense. https://grafana.com/docs/grafana/latest/breaking-changes/breaking-changes-v10-0/#grafana-legacy-alerting-is-deprecated-and-no-longer-accepts-internal-or-external-contributions
During the generation of the changelog snippet for the Github release the latest changes are ignored. I.e. when publishing v3.5.0 of the plugin these notes where shown ## Changelog For...
The following error appears for the "create-artifacts" job: > [create-artifacts](https://github.com/fr-ser/grafana-sqlite-datasource/actions/runs/8204228264/job/22438469728) Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3, actions/setup-go@v4, actions/upload-artifact@v3. For more...
In v3.3.0 (2023-06-11) a new configuration was introduced to handle security risks. The most secure value is 0 but it prevents attaching databases, which might be used in previous features....