Hi! A quick note, in particular to packagers: Source for RKWard 0.7.1b are now available at https://files.kde.org/rkward/testing/for_packaging/ .
This bugfix release has a workaround for the important issue discussed, previously (see cited mail, below). It also comes with two further fixes for one crash and one hang, cherry-picked from the development version. If your distribution ships R 4.0.0, or will ship R 4.0.0 (instead of waiting for R 4.0.1), I would like to ask you to package this as soon as possible. Should you prefer to patch existing RKWard 0.7.0 packages, the most important patch to apply is this: https://invent.kde.org/education/rkward/-/commit/f1e12da76b7ea4dbcb99c8a38ce9dbb5cb96e1a6 An announcement on https://rkward.kde.org will hopefully follow, tomorrow, if I can find the time, and if our Windows and Mac builds proceed as planned. Thanks! Thomas Am Sun, 24 May 2020 10:14:17 +0200 schrieb Thomas Friedrichsmeier <[email protected]>: > Hi! > > This is a note of caution about using RKWard with R 4.0.0: > > -- Problem -- > > There is a bug in R 4.0.0 with respect to active bindings, which > RKWard is relatively likely to trigger. Running the following code > *twice* will render your RKWard session unusable, and **could result > in loss of data**: > > for (i in 1:2) { print (i) } > > Note that this affects top-level statements, only, i.e. in general > code that you enter in the console of run from a script, directly. > Not code in packages or RKWard plugins. > > -- Workaround -- > > If you have the choice, please delay upgrading R until R 4.0.1 is > released. > > If you have already installed R 4.0.0, you should set the option > > compiler::enableJIT(2) # or a lower value > > in each session. This can also be made permanent by copying it into > the field "Futher option commands to run in each session" in > Settings->Configure RKWard->R-Backend. > > -- Outlook -- > > The bug has been fixed in R devel, but no release date has been set to > R 4.0.1, yet. I will probably create a "bugfix"-release that enables > the above workaround by default in the coming day. Meanwhile I have > started working on a new approach to object modification detection > that does not rely on active bindings. > > Regards > Thomas
pgpHAyHq_1CNl.pgp
Description: Digitale Signatur von OpenPGP
