search for: unserializing

I ran into an interesting error unserializing a file created with ascii=TRUE: R 3.5.1 (Windows or Linux): > unserialize(serialize(list(raw=as.raw(c(39,41))), NULL, version=2, ascii=TRUE)) Error in unserialize(serialize(list(raw = as.raw(c(39, 41))), NULL, version = 2, : ReadItem: unknown type 29, perhaps written by later ver...

...sinterpreted and the rest of the data stop making sense. I also tried going explicitly through a text connection, and that seems exactly equivalent. -pd > On 7 Nov 2018, at 23:35 , Michael Sannella via R-devel <r-devel at r-project.org> wrote: > > I ran into an interesting error unserializing a file created with > ascii=TRUE: > > R 3.5.1 (Windows or Linux): >> unserialize(serialize(list(raw=as.raw(c(39,41))), NULL, version=2, > ascii=TRUE)) > Error in unserialize(serialize(list(raw = as.raw(c(39, 41))), NULL, > version = 2, : > ReadItem: unknown type...

Hi, While debugging a network server I'm developing I noticed something unusual - call to unserialize() resulted in an error about loading a namespace. I was a bit taken back by this - why should unserializing an object cause a namespace lookup? Are there any other side-effects of unserialize() that I should be cautious about? I've been digging through the R_Unserialize() call, I haven't found the loadNamespace bit yet but I assume its in there somewhere. Is there anyway to guard against R eager...

...unserialize(con) Warning message: In unserialize(con) : cannot unserialize ALTVEC object of class 'mmap_real' from package 'simplemmap'; returning length zero vector ``` It seems like simplemmap did not get loaded correctly on the worker. If you run `library( simplemmap)` before unserializing the ALTREP, there will be no problem. But I suppose we should be able to unserialize objects without preloading the library? This issue can be reproduced on Ubuntu with R version 4.0.2 (2020-06-22) and Windows with R Under development (unstable) (2020-09-03 r79126). Here is the link to simplemmap...

I stumbled upon the following: f <- parallel::mcparallel(raw(0L)) parallel::mccollect(f) # $`77083` # NULL but f <- parallel::mcparallel(raw(1L)) parallel::mccollect(f) # Error in unserialize(r) : read error traceback() # 2: unserialize(r) # 1: parallel::mccollect(f) (restarting because the above appears to corrupt the R session) f <- parallel::mcparallel(raw(2L))

...alize(con) : > cannot unserialize ALTVEC object of class 'mmap_real' from package > 'simplemmap'; returning length zero vector > ``` > It seems like simplemmap did not get loaded correctly on the worker. If > you run `library( simplemmap)` before unserializing the ALTREP, there will > be no problem. But I suppose we should be able to unserialize objects > without preloading the library? > > This issue can be reproduced on Ubuntu with R version 4.0.2 (2020-06-22) > and Windows with R Under development (unstable) (2020-09...

...sage: > In unserialize(con) : > cannot unserialize ALTVEC object of class 'mmap_real' from package > 'simplemmap'; returning length zero vector > ``` > It seems like simplemmap did not get loaded correctly on the worker. If > you run `library( simplemmap)` before unserializing the ALTREP, there will > be no problem. But I suppose we should be able to unserialize objects > without preloading the library? > > This issue can be reproduced on Ubuntu with R version 4.0.2 (2020-06-22) > and Windows with R Under development (unstable) (2020-09-03 r79126). > &g...

I use recordPlot() to save plots to disk that I render later to a variety of formats. This works fine for base R plots and ggplot2 plots, and also used to work for lattice plots. However somewhere in version 2.14 things stopped working for lattice plots. Here is an example: library(lattice); histogram(rnorm(100)); x <- recordPlot(); saveRDS(x, "myplot.rds"); y <-

Hi folks, I've attached a patch to the svn trunk that improves the performance of the serialize/unserialize interface for vector types. The current implementation: a) invokes the R_XDREncode operation for each element of the vector type, and b) uses a switch statement to determine the stream type for each element of the vector type. I've added R_XDREncodeVector/R_XDRDecodeVector functions

...> cannot unserialize ALTVEC object of class 'mmap_real' from package > > 'simplemmap'; returning length zero vector > > ``` > > It seems like simplemmap did not get loaded correctly on the worker. If > > you run `library( simplemmap)` before unserializing the ALTREP, there will > > be no problem. But I suppose we should be able to unserialize objects > > without preloading the library? > > > > This issue can be reproduced on Ubuntu with R version 4.0.2 (2020-06-22) > > and Windows with R Under development...

Dear R-Users, I need a very fast and reliable database solution so I try to serialize a data.frame (to binary data) and to store this data to an SQLite database. This is what I tried to do: library(RSQLite) con <- dbDriver("SQLite") db <- dbConnect(con, "test") dbSendQuery(db, 'CREATE TABLE frames("simID" INT, "data" BLOB)') data.bin <-

I don''t even know if this is possible. I want to use an object as an attribute for one of my classes. I can save it to the db fine, looks like...but I need to be able to use it after I pull the object from the db. Right now the attribute is just a String, but I need it to be a Runt::Intersect object. Does anyone know how I can unserialize the attribute so I can use it as an object?

Someone solved the problem of saving R-objects to a database? These are the two varaints I've tried so far without success: 1) ser = rawToChar(serialize(obj, NULL, ascii=TRUE)) dbSendQuery(link, paste("insert into table values(1, '",ser,"')",sep='')) The field to save the object in the MySQL Database is of type text. unser = dbGetQuery(link,"select

Are the functions 'R_Unserialize' and 'R_InitFileInPStream' allowed to be used in R packages? I guess I'm just not clear on the implications of this comment in 'Rinternals.h': /* The connection interface is not yet available to packages. To allow limited use of connection pointers this defines the opaque pointer type. */ I have a function in the

Hi all, I'm working with some huge array in R and I need to load several ones to apply some functions that requires to have all my arrays values for each cell... To make it possible, I would like to load only a part (for example 100 cells) of all my arrays, apply my function, delete all cells loaded, loaded following cells and so on. Is it possible to unserialize (or load) only a

Daniel, thanks for the test case. I did run it in valgrind but nothing showed up, however ... I'm starting to have a suspicion that this has something to do with identical() - look at this: > identical(M1,M2) [1] FALSE > all(serialize(M1,NULL)==serialize(M2,NULL)) [1] TRUE > identical(unserialize(serialize(M1,NULL)),unserialize(serialize(M2,NULL))) [1] FALSE >

Hello, I have some code which generates lattice objects. The function recieves serialized forms of the lattice objects which it then unserializes and then adds to an ArrayList<REXP>. REXPRaw rser = new REXPRaw( target ); //target contains the raw serialized forms of lattice objects rconn.assign("temp",rser); REXP ret =

...e: > Looks like I added that warning 22 years ago, so that should be enough > notice :-). I'll look into removing it now. Dear Luke, I've got a somewhat niche use case: as a way of protecting myself against rogue *.rds files and vulnerabilities in the C code, I've been manually unserializing "plain" data objects (without anything executable), including environments, in R [1]. I see that SET_ENCLOS() is already commented as "not API and probably should not be <...> used". Do you think there is a way to recreate an environment, taking the REFSXP entries into ac...

Does anyone have a Perl or PHP Icecast2 Status Page Parser? Thanks. -greg. __________________________________________________________________________ Greg J. Ogonowski VP Product Development ORBAN / CRL, Inc. 1525 Alvarado St. San Leandro, CA 94577 USA TEL +1 510 351-3500 FAX +1 510 351-0500 greg@orban.com http://www.orban.com

Hi all, I''ve recently upgraded a rails 3.0.20 app to 4.0.0.beta1 and realize that the serialize function must have changed in between (not sure if related to json security fixes). In the MySQL database I have for the serialized column: --- id: 6695079125_10151776148744126 In rails 3 this would be parsed back as string ("6695079125_10151776148744126") while in rails 4