similar to: Segfault when performing match on POSIXlt object

>>>>> Martin Maechler on Fri, 31 Aug 2018 16:00:07 +0200 writes: >>>>> Marco Giuliano on Fri, 31 Aug 2018 08:53:02 +0200 writes: >> Hi All, I found a possible unexpected behavior when >> performing match/%in% on POSIXlt objects, e.g. : >> d <- as.POSIXlt('2018-01-01') >> # match(<anything>,<POSIXlt>)

>>>>> Marco Giuliano >>>>> on Fri, 31 Aug 2018 08:53:02 +0200 writes: > Hi All, I found a possible unexpected behavior when > performing match/%in% on POSIXlt objects, e.g. : > d <- as.POSIXlt('2018-01-01') > # match(<anything>,<POSIXlt>) --> segfault match(0,d) > # consequently also this

>>>>> Marco Giuliano >>>>> on Fri, 31 Aug 2018 16:50:56 +0200 writes: > Hi Martin, should I file a formal bug report somewhere or > you've already done it ? No, I haven't, and as I may not address this bug further myself (in the near future), it may be best if you file a formal report. I will create an account for you on R's bugzilla

>>>>> Marco Giuliano writes: Thanks. Should be fixed in the trunk with c75224: will close the PR after more testing. Best -k > Bug report submitted : > https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17459 > Thanks! > On Fri, Aug 31, 2018 at 6:48 PM Martin Maechler <maechler at stat.math.ethz.ch> > wrote: >> >>>>> Marco Giuliano

>>>>> Joshua Ulrich <josh.m.ulrich at gmail.com> >>>>> on Tue, 6 Dec 2016 09:51:16 -0600 writes: > On Tue, Dec 6, 2016 at 6:37 AM, <frederik at ofb.net> wrote: >> Hi all, >> >> I ran into a segfault while playing with dates. >> >> $ R --no-init-file >> ... >> >

Hi Joshua, Thank you for minimizing my test case. > > Hope I'm not doing something illegal... > > > You are. You're changing the internal structure of a POSIXlt object > by re-ordering the list elements. You should not expect a malformed > POSIXlt object to behave as if it's correctly formed. You can see > it's malformed by comparing it's

Hi all, I ran into a segfault while playing with dates. $ R --no-init-file ... > library(lubridate); d=as.POSIXlt(floor_date(Sys.time(),"year")); d$zone=NULL; d$zone=""; d Attaching package: ?lubridate? The following object is masked from ?package:base?: date Warning message: package ?lubridate? was built under R version 3.4.0

A reply from stackoverflow suggests I might have hit this bug: https://sourceware.org/bugzilla/show_bug.cgi?id=14023 I can confirm that this glibc bug affects my system (latest CentOS 7). However, as far as I know, R is not multithreaded in its core. Is it possible that some library triggered this? Regards, Steve Tomas Kalibera <tomas.kalibera at gmail.com> ?2019?8?2??? ??4:59??? >

Hi, I am encountering a strange error in POSIXlt... anyone got a clue? > as.POSIXlt("1982-01-01") Error in as.POSIXlt.character("1982-01-01") : character string is not in a standard unambiguous format > as.POSIXlt("1992-01-01") [1] "1992-01-01" > as.POSIXlt("1972-01-01") [1] "1972-01-01" > as.POSIXlt("1962-01-01")

I have a data frame that contains dates, but when I use as.POSIXlt() I lose the hours on all records. I traced this down to a particuar hour which causes the issue... > as.POSIXlt('2004-10-31 02:00:00') [1] "2004-10-31" > as.POSIXlt('2004-10-31 03:00:00') [1] "2004-10-31 03:00:00" How do I tell as.POSIXlt() to ignore daylight savings and just convert to

Apparently, as.POSIXlt takes one o'clock as the start of the day : > as.POSIXlt(0,origin="1970-01-01") [1] "1970-01-01 01:00:00 CET" > as.POSIXlt(0,origin="1970-01-01 00:00:00") [1] "1970-01-01 01:00:00 CET" > as.POSIXlt(0,origin="1970-01-01 23:59:59") [1] "1970-01-02 00:59:59 CET" Cheers -- Joris Meys Statistical

Hi, I'm encountering a strange error in POSIXlt... anyone got a clue on this? > as.POSIXlt("1982-01-01") Error in as.POSIXlt.character("1982-01-01") : character string is not in a standard unambiguous format > as.POSIXlt("1992-01-01") [1] "1992-01-01" > as.POSIXlt("1972-01-01") [1] "1972-01-01" >

Dear list, When using as.POSIXlt with times measured down to microseconds the default format.POSIXlt seems to cause some possibly undesirable behaviour: According to the code in format.POSIXlt the maximum accuracy of printing fractional seconds is 1 microsecond, but if I do; options( digits.secs = 6 ) as.POSIXlt( 1.000002 , tz="", origin="1970-01-01") as.POSIXlt( 1.999998 ,

Hi Guys, I'm cooking up my time series code. I want a data frame with first column as timestamp in POSIXlt format. I hit on this the problem of how to create an array/list/vector of POSIXlt objects. Code is as follows > dtt=array(dim = 2) > t=as.POSIXlt( strptime("07/12/07 13:20:01", "%m/%d/%Y %H:%M:%S",tz="GMT")) > dtt [1] NA NA > t [1]

Hi all, following sample code illustrates the problem : Date1 <- Date2 <- as.POSIXlt(seq.Date(as.Date("2010-04-01"),as.Date("2011-04-01"),by='day')) identical(Date1,Date2) all.equal(Date1,Date2) identical() gives the correct answer. As there is no all.equal method for POSIXlt objects, all.equal.list is used instead. Subsetting using [[]] doesn't work

How can I extract only the time component from an POSIXlt object? For example if I try the following it still returns both the date and time... >as.POSIXlt(tr.date[1]) [1] "2010-10-18 21:46:53" >as.POSIXlt(tr.date[1],"%H:%M:%S") [1] "2010-10-18 21:46:53" round and trunc don't help... is there an "as.Time" equivalent to as.Date ? Thanks,

Full_Name: Aziz Chaouch Version: 2.2.1 OS: XP/2000 Submission from: (NULL) (132.156.89.240) Hi, I'm not sure this is a "bug" but here is the problem: I'm using the function as.POSIXlt to convert character strings into time objects. I'm using date format as "YYYY/M/D HH:MM" such as as.POSIXlt("1999/6/7 13:30"). Most of the time, this works fine. However

Hi, I'm having trouble understanding how trunc is operating on vectors of POSIXlt objects. Why does dates[1:4] in the last line return a bunch of NAs even though dates look like it has all the right elements? This worries me that something is off with my use of trunc. Is trunc not suppose to be vectorized with POSIXlt? If not, then how should I truncate a bunch of POSIXlt objects? I'm

The length() of a POSIXlt object is given as 9 regardless of the actual length. For example: > make.date.time function (year=c(2006,2006),month=c(8,8),day=2:5,hour=13,minute=45) {# convert year, etc., into POSIXlt object # d=as.character(make.date(year,month,day)) t=paste(hour,minute,sep=":") as.POSIXlt(paste(d,t)) } > t=make.date.time() > t [1] "2006-08-02 13:45:00"

The R script I run daily for hours looks like this: while (!finish) { Sys.sleep(0.1) time = as.integer(format(Sys.time(), "%H%M")) # always crash here if (new.data.timestamp() <= time) next # ... do some jobs for about 2 minutes ... gc() } Basically it waits for new data, which comes in every 10 minutes, and do some jobs, then gc(), then loop again. It