Setting unsigned integer oid value

[stsojithomas]

Is there a way to set unsigned integer value to an oid?

Thanks!

[hh-h]

What happened if you pass unsigned integer via set? Could you add more details?

[stsojithomas]

In the changes, I changed decoder as well to Gauge32 to be consistent. However, that will break existing "reads" due to change from int to Gauge32 for those oids, unless caller updates their code to convert.

Alternate is to keep decoder as existing, and change type for set/encoder only. Thoughts?

[hh-h]

Sorry for the long response, I'll take a look at this. Also, I updated pipeline and deps, so you can sync your PR with master if you want.

[stsojithomas]

Thanks!
I have pulled the latest changes and the pipeline is running fine except for the pytests. I will fix the pytests once we decide on the decoder part (to leave it as int return type or match with encoder of Gauge32).

[hh-h]

I make initial PR, that's my vision, see #43
I'm not sure that it will be work without some encoders in rust, but I don't really have time to write them, so feel free to test my version and update it if needed.

[stsojithomas]

@hh-h Sorry for the delayed response.
Validated int, gauge32, and string in various combinations, and they work. No changes needed to the encoder as when we pass the appropriate tag, the device accepts the value.

The code may be merged and dist built.

Thank you!

[stsojithomas]

Fixed with release 0.7.2