Simon Vetter
Simon Vetter
Just came here to report the same symptoms as @mspielberg: - mounting through either net use, launchctl-64.exe or through the explorer UI all fail with "System error 67 has occurred"...
I can confirm. Another way to reproduce is to keep starting peer tests from the web console (in router commands). Doing this will also get my nodes back in OK...
Setting nat = false in the configuration file seems to have fixed it a while back for me (my nodes aren't behind NAT, obviously).
Hi freman, first off, thanks for chiming in! While moving transports into subpackages would be great, there's a lot of inter-dependency right now in the code (e.g. the RTU transport...
Oh, I see. I like the idea of being able to pass a transport when creating a client, i'll whip something up ASAP.
Hey man, thanks for reporting it! Glad to see you around hacking on open source projects :-) Are those races only present in tests, or is it in the server...
Sorry for the late reply, I've been fairly busy lately. Does https://github.com/simonvetter/modbus/tree/simon/fix-test-races solve your issues? If yes, I'll merge and do a point release.
nice! v1.5.1 pushed. Thanks again!
Hi Stephen, wouldn't simply using a cast work in this case? This is how I usually do it: * read a 16-bit, signed integer: var reg uint16 err, reg =...
Closing this for inactivity. Feel free to reopen if needed.