search for: warningmessages

fxruby-users-bounces at rubyforge.org wrote: > Dear Philippe, > > thank you for responding. > I think I normally would have used FXMessageBox, but here, I > want to tell an impatient user to wait a while while an > external application is started. > I want the MessageBox to be shown, say 3 to 5 seconds, and > then disappear again, without further user action, like clicking

Hi, here is a warningmessage i got while i am testing my new puppet installation with .23.2 and storedconfig and reports and all the bell and whistle :) DEPRECATION WARNING: Calling .create on a has_many association without saving its owner will not work in rails 2.0, you probably want .build instead See http://www.rubyonrails.org/deprecation for details. (called from create at

When large calls cause errors R may stall for extended periods.? This is particularly likely to happen with `do.call`, as in this example with a 24 second stall: ??? x <- runif(1e7) ??? system.time(do.call(paste0, list(abs, x)))? # intentional error ??? ## Error in (function (..., collapse = NULL)? : ??? ##?? cannot coerce type 'builtin' to vector of type 'character' ??? ##

Hello, I'm a new user to R, and I was trying to install "packfor" in my R console and I always run into an error. I tried to search, in in the forum, someone that already might have made the same question, but all I could find was a general information how to install libraries in R. Pass through all that procedure (Package&Data->Package Installer->Local Source

Luke, thanks for considering the issue.? I would like to try to separate the problem into two parts, as I _think_ your comments address primarily part 2 below: 1. How can we avoid significant and possibly crippling ?? stalls on error with these non-standard calls. 2. What is the best way to view these non-standard calls. I agree that issue 2. requires further thought and discussion under a

We also have a few other suggestions and wishes about backtrace storage and display on the one hand, and display of constructed calls on the other hand. Perhaps it would be better to open a different wishlist item for traceback() to keep the discussions focused? FWIW I think deparsing backtraces lazily is a great idea. Displaying 1 line per call by default in interactive sessions, while being

This is probably best viewed in the context of other issue with displaying calls, such as issues arising from calls constructed in non-standard evaluation contexts. Might be good to move to a wishlist item in bugzilla. Best, luke On Sat, 13 Jul 2019, brodie gaslam via R-devel wrote: > When large calls cause errors R may stall for extended periods.? This > is particularly likely to happen

Better to add this to the wishlist item. This all needs to be looked at together, and nothing is likely to happen until after vacation/conference season. It will disappear from everyone's radar if it is just in R_devel. Best, luke On Sun, 14 Jul 2019, brodie gaslam wrote: > Luke, thanks for considering the issue.? I would like to > try to separate the problem into two parts, as I