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
uac: bad error in log #643
Comments
I guess you used it to refresh one record, because the process of loading the records at startup should ignore such records. reg_db_set_attr() triggers 'continue' in such case and it is used in a for-loop. I am going to push a patch that will ignore also for the refresh operation. In that case reg_db_set_attr() was used alone, not within a loop. |
- reg_db_set_attr() does a continue on empty value, but for this operation was not used inside a loop - reported by Dmitri Savolainen, GH #643
it is startup error also |
It is error indeed, but the record should not be added in that case, right? |
record is added } |
Obviously -- reg_db_set_attr() is a while loop itself so the continue applied there. Pushed another patch -- can you test it? If all ok, I will backport. |
it works as expected, thanks! |
Thanks for reporting and testing, I will backport. While it could have been ok without domain, the other attributes are important and same check was done for all. |
there is define in uac_reg.c (define reg_db_set_attr(attr, pos)) which may generate logs like this:
really, record was added, so it should be converted to WARNING or it is neсessary add any more restrict logic
The text was updated successfully, but these errors were encountered: