similar to: Correct procedure when working on bugs tracked in bugzilla?

Hi! I was wondering whether anybody was looking at the bugs on Bugzilla. I'm asking because I've seen bugs tackled on the mailing list quite quickly, but two fully reproducible reports I've filed on Bugzilla haven't triggered any reaction in several weeks (for the older one). FWIW, these are: - Line goes beyond plot region

The R Bugzilla at <https://bugs.r-project.org/bugzilla3/> is down, for at least some hours by now. The error message from my web browser reads: Can't connect to the database. Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Is your database installed and up and running? Do you have the correct username and password selected

Hi All, I have a fix to this bug ( https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16454) and would like to submit a patch to the bug report on Bugzilla. I'd also like to start going through some of the other Windows-specific issues and start fixing those. The bug submission instructions indicate that I should ask here for a Bugzilla account. Is that still the correct procedure? Thanks!

tl;dr is the R bug tracker down or am I being an idiot? Help please ... ---- I decided I would follow up on https://stat.ethz.ch/pipermail/r-devel/2018-January/075410.html (reporting/suggesting a patch for an issue in stats::mantelhaen.test() with large data sets) Reading the instructions at https://www.r-project.org/bugs.html suggests that if I'm sure I have found something worthy of

I was browsing some recent R news at http://developer.r-project.org/blosxom.cgi/R-devel/NEWS/2016/01/03#n2016-01-03 And reading this item: "tapply() has been made considerably more efficient without changing functionality, thanks to proposals from Peter Haverty and Suharto Anggono. (PR#16488)" But I found that the link in the item goes to a page about the GUI, not tapply:

Dear Martin, Does the work on nchar mean that bugs #16090 and #16091 will be resolved [1,2]? Thanks, Mark [1] https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16090 [2] https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=16091 On Sat, Apr 25, 2015 at 11:06 PM, James Cloos <cloos at jhcloos.com> wrote: > >>>>> "GC" == G?bor Cs?rdi <csardi.gabor at

On 16/07/2017 6:17 AM, Anthony Damico wrote: > thank you for taking the time to write this. i set it running last > night and it's still going -- if it doesn't finish by tomorrow, i will > try to find a site to host the problem file and add that link to the bug > report so the archive package can be avoided at least. i'm sorry for > the bother > How big is that

Hi Milan, I can't reproduce your first bug in R 3.2 on Windows 8.1, and I fail to reproduce that one in R 3.1.2 as well. So that might explain why that one isn't tackled. The second bug you reported I can reproduce. Cheers Joris On Tue, Jun 16, 2015 at 9:18 PM, Milan Bouchet-Valat <nalimilan at club.fr> wrote: > Hi! > > I was wondering whether anybody was looking at the

On 16/06/2015 4:18 PM, Milan Bouchet-Valat wrote: > Hi! > > I was wondering whether anybody was looking at the bugs on Bugzilla. I'm > asking because I've seen bugs tackled on the mailing list quite quickly, > but two fully reproducible reports I've filed on Bugzilla haven't > triggered any reaction in several weeks (for the older one). > > FWIW, these

hi, the text file that prompts the segfault is 4gb but only 80,937 lines > file.info( "S:/temp/crash.txt") size isdir mode mtime ctime atime exe S:/temp/crash.txt 4078192743 FALSE 666 2017-07-15 17:24:35 2017-07-15 17:19:47 2017-07-15 17:19:47 no On Sun, Jul 16, 2017 at 6:34 AM, Duncan Murdoch <murdoch.duncan at

Thank you very much. now, i call mle(minuslogl=loglik, start=start, method <<- method, fixed=list()) in the mle.wrap() function, and the profile.mle() worked. however, it created a variable named "method" in user workspace. if there had been a variable with same name, then the value of that variable would be destroyed. Is there a way to avoid that happen? Thanks again.

Hello, I would like to implement the feature request described here: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=13287. I think this is a very worthwhile feature. However, I need just a little push in the right direction. When I added either a new command or change the old one to use eqnarray as proposed, the "\\" newline characters were not properly passed to latex - even

Michael: I don't see any comments on Bug 17432 ( https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17432) later than June 1, 2018. Would you please supply a link pointing to the followup to this discussion on bugzilla? Thanks. Jen. > On Thu Sep 13 14:14:46 CEST 2018 Michael Lawrence wrote: > > Thanks, I responded to this on bugzilla. > On Wed, Sep 12, 2018 at 9:04 AM Chris

As described in <https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17242>, R base functions are currently inconsistent in asking interactive "yes/no" type questions. One solution to this is to have a function to do it, and to use it consistently. Rather than just writing such a function and possibly missing some desirable feature, I'd like to ask if anyone can point

On 15/07/2017 11:33 AM, Anthony Damico wrote: > hi, i realized that the segfault happens on the text file in a new R > session. so, creating the segfault-generating text file requires a > contributed package, but prompting the actual segfault does not -- > pretty sure that means this is a base R bug? submitted here: > https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17311

Simon, can you take a look, please? Best, Uwe On 26.01.2018 01:41, Ben Bolker wrote: > > tl;dr is the R bug tracker down or am I being an idiot? Help please ... > > ---- > I decided I would follow up on > > https://stat.ethz.ch/pipermail/r-devel/2018-January/075410.html > > (reporting/suggesting a patch for an issue in stats::mantelhaen.test() > with

Attached is a patch to fix https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17256 'possible bug in writeForeignSAS in the foreign library when string is NA' The patch 1. fixing the case where there were NA within a character column, and the case where all values are strings of length 0 2. general replacement of calls to `sapply` with `vapply` (and replacing any(is.na()) with

thank you for taking the time to write this. i set it running last night and it's still going -- if it doesn't finish by tomorrow, i will try to find a site to host the problem file and add that link to the bug report so the archive package can be avoided at least. i'm sorry for the bother On Sat, Jul 15, 2017 at 4:14 PM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote:

Hi Duncan, Martin Here's a small patch that fixes bug 15199 reported at: https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=15199 I was able to reproduce the bug as Duncan had outlined just fine, but I did notice that when we debug(f), the problem went away. I later realized that f(1,,3) behaved correctly the first time it was executed, but misbehaved as documented on subsequent calls.

Greetings, I have submitted a bug report / wish to the R Bug tracker (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14939), but I'd like to make this request here as well. Essentially, I was wondering if it would be possible to add another c routine to be called by as.TclObj for raw vectors. Right now, as.raw() is supported for objects of type "tclObj" (IIRC this change was