similar to: Getting an R bugzilla account

I'd be curious to know what others think of Rich's patch. If it is acceptable, I can spend time that I was going to look at it this week on another bug. -----Original Message----- From: Rich Calaway Sent: Friday, June 23, 2017 6:34 PM To: Nathan Sosnovske <nsosnov at microsoft.com>; Duncan Murdoch <murdoch.duncan at gmail.com>; Andrie de Vries <apdevries at gmail.com>

On 04/07/2017 8:46 AM, Nathan Sosnovske wrote: > This doesn't really strike me as a bug. Lots of (most?) programming languages expect you to handle this as an error condition. If you tried the same thing in C you would get the same error. The bug is that there is no error signalled. It looks as though the write succeeded, when it didn't. Duncan Murdoch > -----Original

Hi Duncan, I'm guessing I'll be able to look at this over the weekend/next week (probably closer to next week). It is on my list of things to do and I've just had a few other prior commitments that I have to finish first. Sorry for the delay. I'll chime in with a status update next week. Nathan -----Original Message----- From: R-devel [mailto:r-devel-bounces at r-project.org]

The best way to test on Windows would probably be creating a small virtual hard disk (via CreateVirtualDisk), mounting it, and writing to the mounted location. I believe the drive could even be mounted to an arbitrary location on the filesystem (instead of a drive letter) so that drive letter conflicts don't come into play. -----Original Message----- From: R-devel [mailto:r-devel-bounces at

I would really like the bug fixed. At least this one, because I know people in my institute using this function. I understand your arguments about open source, but I also saw in this mail list a proposal for a fix for this bug for which there were no answer from the people who are able to include it in the distribution. It looks like if there were interesting bugs and the other ones. I don't

Hi, Duncan i have forwarded this thread to Nathan, who promised to look into it. Andrie On 17 Jun 2017 17:26, "Duncan Murdoch" <murdoch.duncan at gmail.com> wrote: > On 17/06/2017 9:13 AM, Ben Marwick wrote: > >> Hi Duncan, >> >> Thanks for your reply. Yes, it does seem to be specific to the CTYPE >> setting to Chinese on Windows. If I set it to

The following patch is not the most elegant, but it restores the Authors when "LC_CTYPE" is set to either "Chinese" or "Arabic": > Sys.setlocale("LC_CTYPE", "Chinese") [1] "Chinese (Simplified)_China.936" > citation("readr") To cite package ?readr? in publications use: (2016). readr: Read Tabular Data. R package

Hi, I have an input data > dput (input) structure(list(ScanDate = structure(c(16433, 16440, 16447, 16454, 16461, 16468, 16475, 16482, 16489, 16496, 16503, 16510, 16517, 16524, 16531, 16538, 16545, 16552, 16559, 16566, 16573, 16580, 16587, 16594, 16601, 16608, 16615, 16622), class = "Date"), OnPromotion = c(0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1, 1, 1, 1, 1, 0, 1, 1, 1, 1, 0, 0, 0, 1,

>>>>> Nathan Sosnovske via R-devel <r-devel at r-project.org> >>>>> on Mon, 26 Jun 2017 18:22:25 +0000 writes: > I'd be curious to know what others think of Rich's > patch. If it is acceptable, I can spend time that I was > going to look at it this week on another bug. It is a bit kludgy (*) of course, but I confirm it solves

On linux at least you can use `/dev/full` [1] to test writing to a full device. > echo 'foo' > /dev/full bash: echo: write error: No space left on device Although that won't be a perfect test for this case where part of the file is written successfully. An alternative suggestion for testing this is to create and mount a loop device [2] with a small file. [1]:

Hi, I've been using 1.0 but moved to beta to see if it works before release. Both b14 and b15 dies sometimes when accessing folders. Last time I fixed this by moving one message from folder to another and then back. Next I'm trying to build this with debugging enabled. Tomppa > Feb 14 11:52:33 dovecot: [ID 107833 mail.crit] IMAP(tomppa): file message-parser.c: line 674: assertion

Hi, I am having trouble trying to figure out why if_else is behaving the way it is, it may be my code or the way the data is structured. Below is a snapshot of a database am working on and it represents a longitudinal survey of study participants in a trial with weekly follow up. The variable "survey_start" represents the start of the study-defined one year follow up (which we called

I don't fully understand the logic you are trying to implement, but something along the lines of foo <- cut(trialData$date, breaks = as.Date(c("2007-01-01", "2008-05-01", "2009-04-01", "2010-05-01",

That many ifelse statements is obviously rather a pain. Would you not have got what you want with ... paste("survey", year, sep="_") ? If that is not what you're looking for (eg because 'year' is the observation year and not the study start year), perhaps something that picks the minimum year for a subject or other relevant group might work? For example

Hi Kevin, I ran the code on the full data set and was able to reproduce the problem that you are facing. My guess is that you have an error in your intuition and/or logic, and that this relates to the use of the subscript [1]. Specifically, on the full dataset, the condition trialData$date[trialData$survey_start == "Y" & trialData$year == 2013 & trialData$site ==

This doesn't really strike me as a bug. Lots of (most?) programming languages expect you to handle this as an error condition. If you tried the same thing in C you would get the same error. -----Original Message----- From: R-devel [mailto:r-devel-bounces at r-project.org] On Behalf Of Lipatz Jean-Luc Sent: Tuesday, July 4, 2017 5:40 AM To: Duncan Murdoch <murdoch.duncan at gmail.com>

Dear Shorewall Users :-) I''ve been playing with shorewall for some time now - I found it really interesting and easy tool to organise all the rules and so on (beforethat I''ve been using simple iptables rules in shell script ;-) Generally it''s quite easy to be used, but anyway found one problem which I cannot handle myself - or in other words - cannot find appropriate

I have a zone "rw" defined as tun0 in interfaces. From that zone, pings to zone "loc" succeed but pings to remote networks (On IPsec VPNs) are rejected in the all2all chain. From my point of view, these pings should be in the rw2cctc chain. (rw to cctc is ACCEPTed in policy.) I must have a hole in my config, where would it be? Thanks, A.

Hi all! I have upgraded Dovecot 0.99.11 installation that's worked with LDAP to Dovecot 1.0-test52 and I can't get LDAP to work. I noticed the /etc/dovecot.conf is slightly different, so I have adjusted changes. If I use the standard auth (passw & pam) everything works fine, however when I user ldap for auth Dovecot starts but then dies: dovecot: Nov 26 14:14:36 Error: Auth process

I'm seeing the following error in our logs when removing mailboxes (we are using mdbox and dovecot 2.1.8): Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Error: stat(/mailstore/domains/test.com/test/mdbox/mailboxes/Spam) failed: Operation not permitted Aug 1 20:03:36 msgsrv dovecot: imap(test at test.com): Mailbox deleted: Spam When I run truss against the process it appears the