Displaying 20 results from an estimated 345 matches for "runnably".
Did you mean:
runnable
2007 Aug 10
2
jinfo, jboss and ExtendedDTraceProbes
Hi,
I would like to use dtrace to observe some behaviour in my J2EE app
running in JBoss. I start JBoss normally in a 1.6 VM. When I try to
enable set the ExtendedDTraceProbes flag using jinfo, I get a thread
dump in the JBoss console and the message: "Unable to open door: target
process not responding or HotSpot VM not loaded" in the jinfo console.
I have tried this with both
2014 Jun 11
1
Recent (6.02) PXELINUX on Soekris net4501
* Ady, 2014-06-11 :
> Perhaps it would be worth testing with official pre-built binaries of
> Syslinux 6.03-pre14 using the following config:
Different behaviour.
* pxelinux.0:
After TFTP load of pxelinus.0, spits out gibberish for ~1 minute
(as though it had set an incorrect default serial port speed),
then loads config and switches back to correct baud rate.
"Hello
2014 Jun 11
3
Recent (6.02) PXELINUX on Soekris net4501
* 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
2019 Jan 07
0
Runnable R packages
Dear David, sharing some related (subjective) thoughts below.
On Mon, Jan 7, 2019 at 9:53 PM David Lindelof <lindelof at ieee.org> wrote:
>
> Dear all,
>
> I?m working as a data scientist in a major tech company. I have been using
> R for almost 20 years now and there?s one issue that?s been bugging me of
> late. I apologize in advance if this has been discussed before.
2019 Jan 31
0
Runnable R packages
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
2019 Jan 31
0
Runnable R packages
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
2019 Feb 01
0
Runnable R packages
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:
>
>
2019 Feb 01
0
Runnable R packages
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
2019 Feb 02
0
Runnable R packages
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]]
2019 Feb 02
0
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
> code (potentially as a package) and which when run will install its
> package code (which is contained in
2019 Feb 02
0
Runnable R packages
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
2019 Feb 07
1
Runnable R packages
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
2012 May 07
2
how to deduplicate records, e.g. using melt() and cast()
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
2006 Apr 18
4
Chime Clarification: Buildable on only nv_35 or Runnable?
Would Studio 10, or Studio 11 be preferable to build?
This message posted from opensolaris.org
2010 Aug 01
3
xm list vs. xl list: more differences?
I see that "xl list" shows a domain waiting idly for console
input as "r", whereas "xm list" shows the same domain as "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
2018 Sep 26
2
OptBisect implementation for new pass manager
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
2019 Feb 08
0
Runnable R packages
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
2019 Feb 02
1
Runnable R packages
I see some value in Duncan?s proposal to implement this as an extra package
instead of a change to base R, if only to see if the idea has legs. I?m
minded to do so myself using your suggestion, but is there a particular
reason why you recommend using the remotes package instead of devtools? The
latter seems to have the same functions I would need, and I believe it is
more widely installed that
2008 Sep 17
4
Supermicro PDSMI failed to boot on fresh RELENG_7/amd64
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 =
2019 Jan 07
2
Runnable R packages
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