From 63feabe2709ffe4a5b25225f9f271811f8e93cf9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20Geisend=C3=B6rfer?= Date: Fri, 14 Oct 2022 08:23:41 +0200 Subject: [PATCH] fix broken links (#20) * fix broken links * remove non-existing link --- block.md | 2 +- examples/block-net/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/block.md b/block.md index b76614f..8035201 100644 --- a/block.md +++ b/block.md @@ -166,7 +166,7 @@ Below is an example of block profile encoded in [pprof's protobuf format](./ppro - contentions/count - delay/nanoseconds -The `blockprofilerate` used to create the profile is not included, neither are [profiler labels](./profiler-labels). +The `blockprofilerate` used to create the profile is not included, neither are profiler labels. ``` $ go tool pprof -raw block.pb.gz diff --git a/examples/block-net/README.md b/examples/block-net/README.md index e8e98a2..1aa6a69 100644 --- a/examples/block-net/README.md +++ b/examples/block-net/README.md @@ -1,6 +1,6 @@ # block-net -This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](/block.md) or not. +This [program](./main.go) explores the [question](https://twitter.com/rogpeppe/status/1359202847708037124) whether network i/o (e.g. waiting on socket read/write operations) will show up in the [block profiler](../../block.md) or not. The program does the following: @@ -22,5 +22,5 @@ However, as you can see below, the block profiler [captures](./block.pb.gz) only ![block-net](./block-net.png) -This means that [block profiler](/block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o. +This means that [block profiler](../../block.md) is generally not able to give a good idea about goroutines that are waiting on network i/o.