fix: typo in exception message #33
Merged
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
hectorvirgen
approved these changes
Oct 18, 2019
|
@prikha The CI settings have been fixed to build forked PRs. Do you mind merging/rebasing with master to trigger a new build? Edit: Never mind. It looks like closing a reopening the PR did the trick. |
grxy
pushed a commit
that referenced
this pull request
Oct 21, 2019
## [0.4.2](v0.4.1...v0.4.2) (2019-10-21) ### Bug Fixes * typo in exception message ([#33](#33)) ([0a337f3](0a337f3))
|
🎉 This PR is included in version 0.4.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
👋 I am trying distributed tracing. No luck so far, but I have noticed a small but misleading typo in the exception message. Fixed that and made the exception more specific.