similar to: problem submitting R bug; bug plotting in tiling window manager

On 05/02/2016 7:26 PM, frederik at ofb.net wrote: > Dear Dirk Eddelbuettel and Duncan Murdoch, > > Thank you for your work on the wonderful R project! > > I recently attempted to submit a bug with your Bugzilla interface: > > https://bugs.r-project.org/bugzilla/enter_bug.cgi > > I created an account, typed in all my information, first checking > details with another

Unfortunately, the spammers in question appear to be human (of sorts). We're not sure what they're up to, but a common pattern is to post random text, or something copied from a generic bug report (like "able to add 6 item"), later followed by a comment containing a link or a file attachment. Presumably, it is some sort of click-bait scheme, but it could also be a covert

In case you still care, see https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16726 which even our very human spam detector hasn't decided to label as spam (yet). -pd > On 08 Feb 2016, at 18:34 , frederik at ofb.net wrote: > > Ah, thank you for that explanation. I somehow didn't catch that my > Bugzilla account had been disabled by a human. > > "Common

No problem. Another suggestion would be to simply validate user input like most websites, and reject invalid submissions immediately, rather than blocking the user's account. I don't know what kind of spambots you are up against, but unless they are very intelligent I doubt they'll be able to understand a message like "You submitted a bug with no body text, please enter something

Ah, thank you for that explanation. I somehow didn't catch that my Bugzilla account had been disabled by a human. "Common pattern is to post ... something copied from a generic bug report" - that sounds very annoying. Frederick On Sun, Feb 07, 2016 at 11:54:11AM +0100, peter dalgaard wrote: > Unfortunately, the spammers in question appear to be human (of sorts). > >

Hi Sorry, I can't offer an explanation for the commented-out line. However, regarding your final question of avoiding the R-core bottleneck, you do have the option of creating a third-party graphics device package. See, for example, the 'tikzDevice' and 'svglite' packages on CRAN. Does that provide you with a way forward ? Paul On 20/04/2019 5:27 p.m., frederik at

I had a look at the current code, and AFAICT it has essentially the same structure as it did back then. I think it may have finally dawned upon me what the issue really is: The logic is that in Rf_addX11Device, we have if (!X11DeviceDriver(dev, display, width, height, ps, gamma, colormodel, maxcubesize, bgcolor, canvascolor,

OK, this is now in R-devel, but only superficially tested (b/c this is a Mac). Please check it out. -pd > On 30 Apr 2019, at 23:09 , Paul Murrell <paul at stat.auckland.ac.nz> wrote: > > Hi Peter > > Yes, that looks roughly right to me. I would be in favour of your option (b), partly because it is probably easiest and partly because that retains the basic graphics device

Hi Paul, No problem. Is it best if I post examples to the bug report 16951? Kind regards, Mark -- Mark O'Connell, PhD student Department of Mathematics & Statistics 231 Top Logic National University of Ireland, Maynooth ----- Paul Murrell <paul at stat.auckland.ac.nz> wrote: > > Thanks Frederick. > > Mark, if you have any examples to share, they would also be

I tried to submit a bug to bugzilla using the link from the "Deus Ex" AppDB page. When I click on the link I get taken to a page that says : Invalid Product Name The product name 'wine' is invalid or does not exist. Please press Back and try again. I'm using the latest version of mozilla-firefox that is in debian unstable (1.0+dfsg.1-1). The link I'm using

Agreed regarding read line-- absent mindedly using C-c to exit a search and then accidentally running garbage because the prompt looks blank but isn't continues to be a problem. On 17 May 2016 2:41 a.m., <frederik at ofb.net> wrote: Dear R Devel, Sorry for sending so many emails, but I haven't heard that anyone is working on the patches I created. A few weeks ago I wanted to do

Thanks, Mark - I'm taking up your invitation to forward your message to the list just because it gives us some valuable data on (1) how long the behavior has been around, and (2) how many other people (don't) understand the behavior, and (3) how we might fix or work around it. I notice some other people also seem to be diffident about posting on R-devel; perhaps I should conclude that

Hi Paul, Thanks for keeping me posted and letting me know what I should do. Are there regression tests for other graphics functions in R? To me that sounds a bit unnecessary. I think you get more testing from people who use R; and having a good turnaround for applying patches (some have been waiting 5 years) would invite better participation. Thank you, Frederick On Fri, Dec 09, 2016 at

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-devel/2016-December/thread.html <https://stat.ethz.ch/pipermail/r-devel/2016-December/thread.html>

https://bugzilla.mindrot.org/show_bug.cgi?id=3176 Bug ID: 3176 Summary: can't figure out how to test StrictHostKeyChecking accept-new Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh

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 least not on the side of the list, since any of the subscribers may be a spammer, who can know... All

Dear R Devel, Sorry for sending so many emails, but I haven't heard that anyone is working on the patches I created. A few weeks ago I wanted to do something to contribute to R because I use it a lot. I picked the most annoying bugs I could find, and created two of the simplest patches I could create, but all I've had in response from the R core team (aside from briefly banning my

>>>>> <frederik at ofb.net> >>>>> on Tue, 24 May 2016 15:15:17 -0700 writes: > Thank you, Martin. I linked to your message in a comment here so maybe > other people will know about that useful technique: > http://singmann.org/installing-r-devel-on-linux/#comment-161 > However, when I try it, I get an error: > $ make

OK, so I did the archaeology anyway.... This was the story, R-core November 29, 2001. Part of thread "X11 still segfaults". ------------>> ..... Gah. I've been too tired today. Why did that take me so long? The culprit seems to be R_ProcessEvents((void*) NULL) in newX11DeviceDriver This gets called *before* this stuff at the end of Rf_addX11Device dd =

Thanks Frederick. Mark, if you have any examples to share, they would also be gratefully received. Paul On 14/11/16 14:53, frederik at ofb.net wrote: > Hi Paul, > > OK I tried not to make the examples too fancy. > > Please let me know what you think. They should probably be amended to > support the Windows platform, but I think that task would be much > easier for someone