-
Notifications
You must be signed in to change notification settings - Fork 664
chore(generator): fail early for bad walk OID #1411
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
Conversation
27c6aa7
to
dda4c35
Compare
dda4c35
to
f768ecc
Compare
Example run:
|
This needs a DCO sign-off. You can use |
f768ecc
to
8b3332f
Compare
Done. |
@SuperQ There is a failing test but it seems unrelated to my change. As it is a failure in downloading a MIB. Please let me know if there are any other changes you would like. Thanks. |
See #1412 |
checks now fixed - go ahead 🚶 |
In `generator.yml` and in a `walk:` section. If an OID starts with a period, for example `.1.3.6.1.4.1.20916`, this will fail to be found, as it should be: `1.3.6.1.4.1.20916`. But the error message lacks detail when this happens. Fail early if an OID starts with a "." and explain why. Signed-off-by: John L. Villalovos <[email protected]>
163a25d
to
6fa705d
Compare
Thanks. I went ahead and rebased it. |
In
generator.yml
and in awalk:
section. If an OID starts with aperiod, for example
.1.3.6.1.4.1.20916
, this will fail to be found,as it should be:
1.3.6.1.4.1.20916
. But the error message lacksdetail when this happens.
Fail early if an OID starts with a "." and explain why.