search for: extraarg

...he idea is to produce "safe" predictions from a model using this function. As I have seen, to do this I need to use makepredictcall(). Consider the following toy example: myns <- function (x, df = NULL, knots = NULL, intercept = FALSE, Boundary.knots = range(x), extraArg = 0) { ns.x <- if (is.null(knots)) { ns(x, df = df, intercept = intercept, Boundary.knots = Boundary.knots) } else { ns(x, knots = knots, intercept = intercept, Boundary.knots = Boundary.knots) } out <- ns.x + extraArg attr(out, "class")...

...t something confusing > happens to the arguments: according to the method, the dots contain > what I would expect them to contain (only the numbers to sum), but when > calling NextMethod() to compute the actual sum, extra arguments get > processed: > > sum.foo <- function(..., ExtraArg = 999, na.rm = FALSE) { > print(ExtraArg) > str(...) > NextMethod(generic = 'sum', ..., na.rm = na.rm) > } > sum(structure(100, class = 'foo')) > # [1] 999 > # 'foo' num 100 > # [1] 100 > sum(structure(100, class = 'foo'), ExtraArg =...

...generator/actions.ml | 14 ++++++++++++++ 2 files changed, 34 insertions(+), 10 deletions(-) diff --git a/daemon/blockdev.c b/daemon/blockdev.c index 8a7b1a8..6e8821d 100644 --- a/daemon/blockdev.c +++ b/daemon/blockdev.c @@ -62,7 +62,7 @@ call_blockdev (const char *device, const char *switc, int extraarg, int prints) */ udev_settle (); - if (extraarg > 0) { + if (extraarg >= 0) { snprintf (buf, sizeof buf, "%d", extraarg); argv[2] = buf; argv[3] = device; @@ -89,33 +89,43 @@ call_blockdev (const char *device, const char *switc, int extraarg, int prints) }...

...ently, they are dispatched, but something confusing happens to the arguments: according to the method, the dots contain what I would expect them to contain (only the numbers to sum), but when calling NextMethod() to compute the actual sum, extra arguments get processed: sum.foo <- function(..., ExtraArg = 999, na.rm = FALSE) { print(ExtraArg) str(...) NextMethod(generic = 'sum', ..., na.rm = na.rm) } sum(structure(100, class = 'foo')) # [1] 999 # 'foo' num 100 # [1] 100 sum(structure(100, class = 'foo'), ExtraArg = -1) # [1] -1 # 'foo' num 100 # <--...

See http://rwmj.wordpress.com/2014/11/23/mapping-files-to-disk/

Does *not* incorporate changes suggested by Pino yet. Rich.

From: "Richard W.M. Jones" <rjones at redhat.com> This reverts commit a9c8123c72db47bcab8dd738e8d5256a9ae87f11. --- daemon/file.c | 18 +++--------------- daemon/parted.c | 3 +-- 2 files changed, 4 insertions(+), 17 deletions(-) diff --git a/daemon/file.c b/daemon/file.c index 057e15d..91746e0 100644 --- a/daemon/file.c +++ b/daemon/file.c @@ -525,7 +525,7 @@

...disk path=/var/lib/libvirt/images/"$vmname".qcow2,device=disk,bus=virtio,format=qcow2 --mac= --cpu host --vcpus="$numcpus" --graphics none --noautoconsole --import But cannot seem to find a way to enable bios useserial=yes without issuing a virsh edit $vmname I've tried --extraargs= but that appears to be for kernel command lines, which is not what I want to achieve here. I'm looking for a way to enable serial BIOS from the point the VM is created. The current solution I am using is to do virsh destroy $vmname ; virsh edit $vm_name ; virsh start $vm_name which is not g...

...nlessHasModule(mod): + if not isModuleInstalled(mod): + return unittest.skip("%s not available" % mod) + return lambda func: func + + +def iterload(stream): + dec = json.JSONDecoder() + for line in stream: + yield dec.raw_decode(line) + + +def loadJsonFromCommand(extraargs): + r, w = os.pipe() + set_fd_inheritable(r) + r = fdopen(r, "r") + set_fd_inheritable(w) + w = fdopen(w, "w") + pid = os.fork() + if pid: + w.close() + l = list(iterload(r)) + l = [o[0] for o in l] + r.close() + return l...

This version of the patch includes feedback from jboggs at redhat.com, including fixes to the BuildRequires and Requires in the spec file.

This patch obsoletes any previous ones. This is an upstream candidate, so I'm looking for feedback so we can push this and start using it.

This version fixes a few bugs found by jboggs. It also includes some logging facilities that need to be fleshed out more.

This patch is ready for pushing upstream.

The previous patch was missing this file. Resending.

Enhance the output in machine parseable mode, by outputting all the messages of OCaml tools as JSON to the machine parseable stream. Related, although not strictly needed for this (and thus can be split if requested), is the addition of the fd format for the machine readable stream. Changes from v1: - use Obj.magic to convert int -> Unix.file_descr - add tests Pino Toscano (4):

The warnings in daemon were aggravating and risky for development (too easy to miss new ones) so I spent some time last week and today working on removing them. The first patch gets us down to almost no warnings with the original -Wall setting. That was by far the hardest part. Once I'd done that, I enabled nearly all of gcc's warnings via gnulib's warnings and manywarnings modules

I ran the Coverity static analyzer[1] on libguestfs, and fixed many errors as a result. Coverity found some errors in gnulib, but it doesn't seem to be worth following those up since the version of gnulib we are using is so old. There are a couple more errors (possibly 1 false-positive) which I'm going to send in a separate email. BTW all the errors found by Coverity were in the daemon

...just looking for some feedback on the direction I'm going. The code won't get all the way to the define stage since I'm in the middle of retrofitting it to use virtinst instead of a home spun node definition.

This started as a simple warning-elimination change. I'll get back to that series shortly ;-) It turned into a factorization and constification exercise during which I got a taste of ocaml. Thanks to Rich Jones for help with a few snippets in generator.ml. The overall result is that many previously-manually-maintained bits from daemon/*.c functions are now hoisted into the automatically-

If we want to permit more than 255 drives to be added, then we will have to add the disks to the same virtio-scsi target using different unit (LUN) numbers. Unfortunately SCSI LUN enumeration in the Linux is not deterministic (eg. two disks with target=0, lun=[0,1] can be enumerated as /dev/sda or /dev/sdb randomly). Dealing with that will require some very complex device name translation on the