Skip to content
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.

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

File name/path for link errors doesn't show #28

Closed
saswatamcode opened this issue May 16, 2021 · 0 comments · Fixed by #31
Closed

File name/path for link errors doesn't show #28

saswatamcode opened this issue May 16, 2021 · 0 comments · Fixed by #31
Assignees

Comments

@saswatamcode
Copy link
Collaborator

Currently, while running mdox on several files, say using file glob like mdox fmt -l {*.md, */*.md} it's not possible to tell where a particular error is due to outputs like below. Here there's no local link error so it's not possible to guess which file has the broken links from error message itself,

4 errors:
                "https://github.com/thanos-io/thanos/issues/1706" not accessible; status code 429: Too Many Requests
                "https://github.com/prometheus/prometheus/pull/5794" not accessible; status code 429: Too Many Requests
                "https://github.com/grpc-ecosystem/go-grpc-middleware/blob/v2/interceptors/logging/options.go#L58" not accessible; status code 429: Too Many Requests
                "https://github.com/grpc-ecosystem/go-grpc-middleware/blob/v2/interceptors/logging/options.go#L51" not accessible; status code 429: Too Many Requests
                "https://github.com/cortexproject/cortex/pull/2349" not accessible; status code 429: Too Many Requests
@saswatamcode saswatamcode self-assigned this May 16, 2021
@saswatamcode saswatamcode changed the title Add file name/path to link errors File name/path for link errors doesn't show May 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant