search for: runnabl

...TING (sleeping) at java.lang.Thread.sleep(Native Method) at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1546) at java.lang.Thread.run(Thread.java:619) "PooledInvokerAcceptor#0-4445" prio=10 tid=0x0035ac00 nid=0x2c runnable [0xed37f000..0xed37fb70] java.lang.Thread.State: RUNNABLE at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) - locked <0xfb518080> (a java.net.SocksSocketImpl) at java.net.ServerSocket....

...s in the other direction. (With my previous Clonezilla menu it seemed to still not receive anything). * lpxelinux.0: Interesting, does not freeze anymore apparently. Gibberish after loading; if I switch to 115200 bps then I see it's actually in an endless loop of: Thread 0x003a0010 (idle) runnable priority 2147483647 Thread 0x00122034 (root) runnable priority 0 Schedule Thread 0x003a4050 (pxe receive) runnable priority -20 Thread 0x003a0010 (idle) runnable priority 2147483647 Thread 0x00122034 (root) runnable priority 0 Schedule Thread 0x003a4050 (pxe receive) runnable priority -20 Thread 0...

* Gene Cumm, 2014-06-10 : > If 4.05 or 3.86 acted nicely, this would mean a bug. OK, so, with unpatched official binaries: 3.86 ---- pxelinux.0 Loads fine, assumes terminal width 15, displays menu, but then freezes (I suspect it does not process any input from the serial port) gpxelinux.0 Displays: PXE->EB: !PXE at 9E64:0060, entry point at 9E64:00F6 UNDI code segment

...-friendly script as well. Of course, this requires Docker to be installed, but if that's a problem, probably better to "ship" the app as a web application and share a URL with the user, eg backed by shinyproxy.io > > Other languages let the developer package their code in "runnable" > artefacts, and let the developer specify the main entry point. The > mechanics depend on the language but are remarkably similar, and suggest a > way to implement this in R. Through declarations in some file, the > developer can often specify dependencies and declare where the...

Belated thanks to all who replied to my initial query. In summary, three approaches have been mentioned to run R code "in production": 1) ShinyProxy, mentioned by Tobias, for deploying Shiny applications; 2) Docker-like solutions, mentioned by Gergely and I?aki; and 3) Solutions based on Rscript or littler, mentioned by Dirk. I can't speak to 1) because I don't currently use

On Thu, Jan 31, 2019 at 3:14 PM David Lindelof <lindelof at ieee.org> wrote: > > In summary, I'm convinced R would benefit from something similar to Java's > `Main-Class` header or Python's `__main__()` function. A new R CMD command > would take a package, install its dependencies, and run its "main" > function. I just created and built a very

Ummm oops. Magic pixies? It assumed all of CRAN was installed? Maybe I'll write something that could go in /usr/lib/R/bin/RUN that checks and gets deps, installs the package, and runs package::main, which I think is what the OP wants - you could do R CMD RUN foo_1.0.0.tar.gz and away it goes... B On Thu, Jan 31, 2019 at 3:56 PM David Lindelof <lindelof at ieee.org> wrote: > >

To download a package with all its dependencies and install it, use the install.packages() functions instead of 'R CMD INSTALL'. E.g., in bash: mkdir /tmp/libJunk env R_LIBS_SITE=libJunk R --quiet -e 'if (!requireNamespace("purrr",quietly=TRUE)) install.packages("purrr")' For corporate "production use" you probably want to set up your own repository

Further to my previous post, it would be possible to create an .exe file, say: my_r_application.exe That starts R, loads your R package(s), calls the R function of your choice and does whatever else you want. However, I don't think that it would add much value. But feel free to correct me if you think that I'm wrong. [[alternative HTML version deleted]]

On 02/02/2019 8:27 a.m., Barry Rowlingson wrote: > I don't think anyone denies that you *could* make an EXE to do all > that. The discussion is on *how easy* it should be to create a single > file that contains an initial "main" function plus a set of bundled > code (potentially as a package) and which when run will install its > package code (which is contained in

Creating an .exe file isn't necessarily difficult. The main problems are that you have to write and compile the C (or other) files. Otherwise, the complexity depends on the level of Inter Process Communication that's required. Simply starting R with some initial conditions, is easy. Even if you want to prompt the user to install missing packages, it isn't necessarily difficult. It

Doesn't Rtools provide everything needed to build R packages and R on Windows - including gcc? Am Sa., 2. Feb. 2019 um 22:29 Uhr schrieb Abs Spurdle <spurdle.a at gmail.com>: > Creating an .exe file isn't necessarily difficult. > The main problems are that you have to write and compile the C (or other) > files. > Otherwise, the complexity depends on the level of Inter

Esteemed UseRs, This must be embarrassingly trivial to achieve with e.g., melt() and cast(): deduplicating records ("pw.X" in example) for a given set of responses ("cond.Y" in example). Hopefully the runnable example shows clearly what i have and what i'm trying to convert it to. But i'm just not getting it, ?cast that is! So i'd really appreciate some ones patience to clarify this, using the reshape package, or any other approach. With sincere thanks in advance, Karl ## Runnable exa...

Would Studio 10, or Studio 11 be preferable to build? This message posted from opensolaris.org

...;b". I also see that the State field for "xl list" contains only three characters (e.g. "r--"), whereas "xm list" shows six (e.g. "-b----"). Is this expected/intended (e.g. "r" in xm list means "running" and in xl list it means "runnable:), or is it a bug? For intended differences between xm and xl, is there any documentation? Thanks, Dan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Philip, It kinda depends on user expectations. What do you really expect as a result of your compilation when you set -opt-bisect-limit=X? Do you just get a resulting IR and scan for the bad pattern? Then you dont care about pass sequences and do brute-force bisect. Do you expect to get a runnable code at the end and check for buggy run-time behavior? Then you need to keep the passes that are required to produce runnable code. In our Java JIT compiler we have quite a number of passes where we lower the semantics to C level and those lowerings are absolutely required for the code to be ru...

Sounds interesting. Do you have it on GitHub or similar? Rainer > On 8 Feb 2019, at 09:09, David Lindelof <lindelof at ieee.org> wrote: > > Yesterday I wrote and submitted to CRAN a package `run`, which implements > the ideas discussed in this thread. Given a package tarball > foo_0.1.0.tar.gz, users will be able to run > > Rscript -e

...February 2019 at 15:37:16 To: Barry Rowlingson <b.rowlingson at lancaster.ac.uk> <b.rowlingson at lancaster.ac.uk>, Abs Spurdle <spurdle.a at gmail.com> <spurdle.a at gmail.com> Cc: r-devel <r-devel at r-project.org> <r-devel at r-project.org> Subject: Re: [Rd] Runnable R packages On 02/02/2019 8:27 a.m., Barry Rowlingson wrote: > I don't think anyone denies that you *could* make an EXE to do all > that. The discussion is on *how easy* it should be to create a single > file that contains an initial "main" function plus a set of bundled &gt...

Colleagues, 3 of 4 times this machine failed to boot, panicing somewhere in late kernel initialization phase (before /sbin/init is executed) I have serial console and KDB enabled, so can do experiments. Last two crashes: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x8 fault code = supervisor read data, page not present instruction pointer =

On Mon, 7 Jan 2019 at 22:09, Gergely Dar?czi <daroczig at rapporter.net> wrote: > > Dear David, sharing some related (subjective) thoughts below. > > You can provide your app as a Docker image, so that the end-user > simply calls a "docker pull" and then "docker run" -- that can be done > from a user-friendly script as well. > Of course, this requires