Skip to content

Fix typos and improve clarity in troubleshooting.md #656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jjpinto wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −6
Open

Fix typos and improve clarity in troubleshooting.md #656

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions docs/content/docs/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ bref = "When something goes wrong"
In most cases, you will find the answer to your problem in the logs.
Watermill offers a significant amount of logs on different severity levels.

If you are using `StdLoggerAdapter`, just change `debug`, and `trace` options to true:
If you are using `StdLoggerAdapter`, just change `debug` and `trace` options to true:

```bash
logger := watermill.NewStdLogger(true, true)
````
```

## Debugging Pub/Sub tests

Expand All @@ -26,12 +26,12 @@ make up
go test -v ./... -run TestPublishSubscribe/TestContinueAfterSubscribeClose
```

### grep is your friend
### Grep is your friend

Each executed test case has a unique UUID.
It's used in the topic's name.
It's used in the topic name.
Thanks to that, you can easily grep the output of the test.
It gives you detailed information about the test execution.
This gives you detailed information about the test execution.

```bash
> go test -v ./... > test.out
Expand Down Expand Up @@ -86,7 +86,7 @@ main.main()
When running in production and you don't want to kill the entire process, a better idea is to use [pprof](https://golang.org/pkg/net/http/pprof/).

You can visit [http://localhost:6060/debug/pprof/goroutine?debug=1](http://localhost:6060/debug/pprof/goroutine?debug=1)
on your local machine to see all goroutines status.
on your local machine to see the status of all goroutines.


```bash
Expand Down