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

Fix exception with stoul for droppruning #573

Merged
merged 1 commit into from
Jun 28, 2024
Merged

Conversation

shastrinator
Copy link
Contributor

When src/dst prefix lengths were unset, fields
contained an empty space, which was inadvertently added while parsing for mask, which caused an
exception in opflex_agent

@shastrinator shastrinator force-pushed the fix_dropprunecore branch 2 times, most recently from 6f90903 to f728699 Compare June 27, 2024 22:51
When src/dst prefix lengths were unset, fields
contained an empty space, which was inadvertently added
while parsing for mask, which caused an
exception in opflex_agent

Signed-off-by: Kiran Shastri <shastrinator@gmail.com>
@coveralls
Copy link
Collaborator

Coverage Status

coverage: 78.716% (-0.1%) from 78.839%
when pulling cf54871 on fix_dropprunecore
into 5e6f2cb on master.

@coveralls
Copy link
Collaborator

Coverage Status

coverage: 78.768% (-0.07%) from 78.839%
when pulling cf54871 on fix_dropprunecore
into 5e6f2cb on master.

@mchalla mchalla merged commit 43cc55a into master Jun 28, 2024
5 checks passed
@mchalla mchalla deleted the fix_dropprunecore branch June 28, 2024 00:28
}
boost::system::error_code ec;
addr = asio::ip::address::from_string(address_string, ec);
if (ec) {
LOG(ERROR) << "Invalid address for filter " << filter_idx;
return -1;
}
if(pfxLen) {
if(!pfxLenArg.empty()) {
LOG(INFO) << "PrefixLen is set!";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realize that this is already merged, but do we feel that this should be an INFO level log?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No doesn't need to be, missed removing it post debug. Can be removed with some later commit. Thanks

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 this pull request may close these issues.

4 participants