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
Yes, I just heard from Amy Kristen who is "looking to meet new
guys"...
On Fri, Dec 02, 2016 at 11:31:56AM -0800, Kenny Bell wrote:
> Have others received spam messages after posting to this list?
>
> The two problem emails are hodgesdonna...@yahoo.com and
> amykristen4...@octbm.com.
>
> [
> new package, R_spam
Oh, you got my hopes up!
On Tue, Dec 06, 2016 at 12:24:20PM -0200, Marcelo Perlin wrote:
> Perhpas amy needs help with her new package, R_spam,which is not working
> well with R_scam. 😂
>
> Em 6 de dez de 2016 11:16, escreveu:
>
> Yes, I just heard from Amy Kristen who i
Hi,
I have recently tried to check the test coverage using library("covr") and,
interestingly, the command
> covr::package_coverage()
fails, while
> covr::package_coverage(quiet = FALSE)
runs through without problem. I traced the problem to a call to
utils::install.packages(), where the opt
The problem is not specific to this list. Any kind of public
list may mean that other subscribers (or even the whole world)
can see your email address. So whenever you mail to a (public)
list there is a good chance that afterwards, you will get more
spam. Not really much can be done about it, at l
Perhpas amy needs help with her new package, R_spam,which is not working
well with R_scam. 😂
Em 6 de dez de 2016 11:16, escreveu:
Yes, I just heard from Amy Kristen who is "looking to meet new
guys"...
On Fri, Dec 02, 2016 at 11:31:56AM -0800, Kenny Bell wrote:
> Have others received spam mess
On Tue, Dec 6, 2016 at 6:37 AM, wrote:
> 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
>
If you're asking about a bug in R, you should provide a
Hi,
This topic has come up previously, across the R e-mail lists and the spammers
need not be subscribers (but could be), but simply reasonably competent HTML
scrapers.
If you look at the online archives of the R lists, for example R-Devel for this
month:
https://stat.ethz.ch/pipermail/r-
I agree that no action should be taken.
It's somewhat mystifying that the robot known as "Amy Kristen"
responds so quickly after my post, and with such regularity (so far
twice per hour), using perhaps several email addresses - and using the
correct "Reply-To" headers. But more mystifying is that
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.
Hi,
FWIW, I checked the R-Devel subscriber list of e-mail addresses (as Co-Admin
with Martin I have access). There are presently 1,296 subscribers to individual
posts and 746 to post digests on R-Devel.
Neither of the two e-mail addresses referenced below as being the sources of
spam are liste
On Tue, Dec 6, 2016 at 10:30 AM, wrote:
> 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
>> PO
Hi all,
Here's a more minimal version of my earlier bug report (thanks, Joshua
Ulrich):
d=as.POSIXlt(Sys.time()); d$zone=NULL; d$zone=""; d
I got some helpful, if glib, feedback from Joshua that the segfault
may be caused by the changing of the order of the list elements in 'd'
(representing the
I agree this is a bug; R should never segfault. I wouldn't call it a
high priority one, since you can avoid the problem by not messing with
R's internal structures.
It's unlikely to get fixed unless someone posts it as a bug report to
bugs.r-project.org (because low priority bugs reported onl
I got a similar result from R-Studio 1.0.44 with
> sessionInfo()
R version 3.3.2 (2016-10-31)
Platform: x86_64-apple-darwin13.4.0 (64-bit)
Running under: OS X El Capitan 10.11.6
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats graph
> Joshua Ulrich
> on Tue, 6 Dec 2016 09:51:16 -0600 writes:
> On Tue, Dec 6, 2016 at 6:37 AM, wrote:
>> Hi all,
>>
>> I ran into a segfault while playing with dates.
>>
>> $ R --no-init-file
>> ...
>> > library(lubridate); d=as.POSIXlt(floor_date(Sy
On 12/05/2016 01:05 AM, peter dalgaard wrote:
On 02 Dec 2016, at 23:13 , Hervé Pagès wrote:
More generally one might reasonably expect 'unlist(x)' to be equivalent
to 'do.call(c, x)' on a list 'x' where all the list elements are atomic
vectors:
Well, both are generic, and e.g. there is no "
Thanks for the reply, Duncan.
It looks like Martin can commit a patch faster than I can open a bug
report...
Frederick
On Tue, Dec 06, 2016 at 12:39:32PM -0500, Duncan Murdoch wrote:
> I agree this is a bug; R should never segfault. I wouldn't call it a high
> priority one, since you can avoid
18 matches
Mail list logo
