-
Notifications
You must be signed in to change notification settings - Fork 52
Feature: Added RRSet comments support #87
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
Open
PetrusHahol
wants to merge
9
commits into
pan-net:master
Choose a base branch
from
PetrusHahol:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 7 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
9ffb499
Added RRSet comments support
de70a43
Added RRSet comments
13d2065
Fixed confusing comment
78f1876
Fixed documentation indent
402f0c6
Merge branch 'fork_master' into main_master
09e5900
Fixed caches error handling if its overflowed
a473860
Merge branch 'pan-net:master' into master
PetrusHahol 802fde7
Changelog has extended
4863811
Through the error from Cache.Set
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mbag
Have a look at this change. I think it's better to through not an error but a warning message here.
If it needed, I can create it as a separate MR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PetrusHahol I think it should return error (for example JSON marshaling above returns error), because user enables caching and expects objects to be cached. But if there is error and they are not cached, however, the execution continues with only warning. This might not be something they want to pass.
Also, I'm wondering now if the error described is only possible error, i.e. if it wouldn't be better to just do
return nil, err
as in other error checks. Because, if in fact, theclient.Cache.Set
fails for some other reason, it might get obscured by our custom error message. But this was my error, that I haven't spotted before merging.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh, I forgot to ask. Why do you think it's better to just log warning, and continue with the execution?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm.. Actually I also think it may lead to some different error. I will change it.
I have just totally otherwise picture of it. In case users use cache and something went wrong with it, we can still continue execution and in a meanwhile let them know that something crashed. User can immediately stop execution. But maybe you're right, it might lead to DDoS of PowerDNS API, like if it would be without caches enabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello guys, any update with the "comment" paramenter ?