Closed NathanSkene closed 4 years ago
Thank you for flagging this!
What I want to fix generally is that if the worker encounters an early error, it still sends this back to the master loop.
In this particular case, I'll see what I can do. It is a bit more complicated because
>=1.0
) API, so it should occur only on major (x.0.0
) version bumps. Yet, R routinely breaks functionality in minor versions, and it is impossible to anticipate which or whenSo maybe the best approach is to display a warning if the SSH R has a different major or minor version than the master process.
Can you check if a message is serialized with your R<3.5.0
, can it be unserialized with R>=3.6.0
?
i.e.:
saveRDS(serialize(1:10, NULL), "test.rds") # on your server w/ R<3.5.0
unserialize(readRDS("test.rds")) # on your local machine with current R
Thanks for looking into it!
I ran this line on the server running R 3.4.1:
saveRDS(serialize(1:10, NULL), "test.rds")
Downloaded the file and opened in locally with R 3.6.0. It worked fine.
This will be addressed by #150.
Hi,
Firstly, many thanks for developing this great piece of software.
I've just been working on setting it up to connect via SSH to a SLURM cluster. I was finding that it would hang on "Sending common data ...". After checking the logs on the server I saw:
Might be worth adding a script to check the version of R first, and enable it to fail more gracefully if the wrong version of R is loaded?