public/grafana
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[v9.2.x] Use relref resolved from nearest section (#58721)

Browse Source 
Use relref resolved from nearest section (#58718)

As image-rendering is a branch bundle, it is considered a section by
Hugo and relrefs should be resolved from there even for child pages.

The behavior that worked in `next` but not `latest` could be explained
by the lenient but potentially ambiguous relref resolution algorithm
Hugo uses. However, I have not determined the exact difference between
the two sets of content that causes `next` to work but `latest` not to.

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>

Signed-off-by: Jack Baldry <jack.baldry@grafana.com>
(cherry picked from commit b9d8bcb59b)

Co-authored-by: Jack Baldry <jack.baldry@grafana.com>
This commit is contained in:
Grot (@grafanabot)
2022-11-14 17:13:05 -04:00
committed by GitHub
co-authored by Jack Baldry
parent a8ceec0ed9
commit bc708d3543
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/sources/setup-grafana/image-rendering/troubleshooting.md
+3 -3
View File
@@ -30,9 +30,9 @@ filters = rendering:debug
You can also enable more logs in image renderer service itself by:
- Increasing the [log level]({{< relref "../../image-rendering#log-level" >}}).
- Enabling [verbose logging]({{< relref "../../image-rendering#verbose-logging" >}}).
- [Capturing headless browser output]({{< relref "../../image-rendering#capture-browser-output" >}}).
- Increasing the [log level]({{< relref ".#log-level" >}}).
- Enabling [verbose logging]({{< relref "./#verbose-logging" >}}).
- [Capturing headless browser output]({{< relref "./#capture-browser-output" >}}).
## Missing libraries