Automatic retry on read error

[njh]

Hello,

I used your owfs library inside my Node-RED owfs node:
https://github.com/njh/node-red-contrib-owfs

I have a feature request to perform automatic retries, when there is an occasional error - in particular when the special value of 85 is read from a DS18B20. I have been trying to seperate concerns, and only include code relating to Node-RED and its UI in my module

Would you accept a Pull Request that adds this functionality to your library?
It would involve somehow passing a retries and interval values, when creating the client.

nick.

[njh]

Any thoughts on this? Would we be wasting our time to send a Pull Request?

[njh]

ping

[benediktarnold]

Sorry for such a late response. I am currently not very motivated to maintain this package since I don't use it myself. We have two options

1. I would accept your PR without any questions
2. I could add you as an npm owner or transfer the package ownership completely to you. This is imho the best Solution since your node-red contribution is the biggest user.

[njh]

Thanks for getting back to me @benediktarnold
Totally understand about lack motivation of maintaining something that you aren't using.

I have a lot of 1-wire devices connected to various Node-RED instances...
If you would transfer the Github repo and npm ownership to me, I promise to look after it!

[benediktarnold]

@njh I added you as an owner in npm. You should be able to publish releases from now on.

The github repo can't be transferred since you already have a fork. If you delete your fork, the transfer should be possible.

[njh]

Thanks! I have deleted my Github repo fork now.

[colinl]

@njh Just starting to look at this again (though it will have to be at a fairly leisurely pace due to pressure of other stuff). I see you are in an active development stage at the moment. Maybe best that I wait till you reach a stable point in order to avoid confusion.

[njh]

Yes, probably a good idea.

I am nearly done with tidying up type changes, but maybe #19 and #22 would be good to get sorted.