Trace log line number on error in parsing w3c log file #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| (e, line) => _logger.LogError( | ||
| LogEvents.FailedToParseLogFileEntry, | ||
| e, | ||
| "Failed to parse W3C log entry in {LogFileName} at line {LineNumber}.", |
There was a problem hiding this comment.
Moved it into resources in 2f9651f
|
LGTM |
|
|
|
LGTM |
joelverhagen
pushed a commit
that referenced
this pull request
Oct 26, 2020
* Trace log line number on error * Moved log message into common resources file
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This further facilitates diagnosing the cause of the error in the source file.
cc @maartenba @skofman1