search for: percolate

What is the likelyhood that major inexpensive webhosts like godaddy, bluehost, etc. will upgrade to RoR 1.1? Is this going to be like PHP 5 where it has to percolate for a year or more before it becomes widly available? Your thoughts? Along the same lines... is it possible to adopt some of the new improved Ajax / javascript capabilities without actually upgrading the ruby installation? Thanks in advance. -- Posted via http://www.ruby-forum.com/.

I installed a debian squeeze desktop client today and a squeeze, with xen 4, on one of our servers. I had problems getting libvirt on the client to create virtual machines on the server. The fix was to create a symbolic link called xen to /usr/lib64/xen-4.0 on the server as libvirt was looking for files in that path. Is there anything else I should be aware of/issues regarding this setup? I

...s from everything else is back in, > there are actually error logging messages now which no-one else seems > to think are important. No, let's all crap on NTPsec because it's > easier. > If, ntpsec is now working again with Samba AD, then great, but it doesn't seem to have percolated down to Debian. Rowland

Hello All. This is purely from a particular VLIW target back-end perspective. There it is possible to schedule an MI on to one of multiple execution pipes. This leads to a different instruction encoding per the pipe it is bound to, and need to percolate this information down. Would it be advisable to extend and use the "MachineInstr.Flags" field for this purpose? Right now this flag seems to consume 2bits space out of total 8 (uint8_t). Could we extend this field to say 32bit or better yet to 64bits like MCInstrDesc.TSFlags? Any suggesti...

...controller to do the same for you. I am going to > play with similar on one of my machine, but it sounds like my controller > is different: in my case lspci gives me: <snip> Yeah, I know. Thanks - unfortunately, their hot-swap drive bays are full. However, after I posted it, it finally percolated through my brain that they were still under warranty (5 yrs is what we buy), so I just called Dell, and am told they'll do 4TBs. Now, that, I assume, means they'll take larger, but he's researching it for me to be sure. mark

I am able to start kick off windows/linux installs on a new vm but then find the installation can''t read from the dvd-rom....xe cd-list reports the dvd-rom as scsi? I am using xcp 1 beta and xencenter fp1. Any help would be appreciated. Thanks, Chris _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...routines in survival5 should update their version. A bug has been fixed in the S package: in coxph() models with penalised likelihood and strata it was possible in some circumstances to get an infinite loop or perhaps an incorrect answer. The new version (2.3) is on cran.r-project.org and will percolate through CRAN in the next few days. -thomas Thomas Lumley Asst. Professor, Biostatistics tlumley at u.washington.edu University of Washington, Seattle -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-announce mailing list -- Read http://www.ci.tuwien.ac.at/~hor...

Version 3.18 of the survey package is now percolating through CRAN. Since the last announcement on this list, in February, the main additions are - standard errors for survival curves (both Kaplan-Meier and Cox model) - svyciprop() for confidence intervals on proportions, especially in small samples or near 0 or 1. - predictive margins by direct standardization, with marginpred() -

Version 3.18 of the survey package is now percolating through CRAN. Since the last announcement on this list, in February, the main additions are - standard errors for survival curves (both Kaplan-Meier and Cox model) - svyciprop() for confidence intervals on proportions, especially in small samples or near 0 or 1. - predictive margins by direct standardization, with marginpred() -

...routines in survival5 should update their version. A bug has been fixed in the S package: in coxph() models with penalised likelihood and strata it was possible in some circumstances to get an infinite loop or perhaps an incorrect answer. The new version (2.3) is on cran.r-project.org and will percolate through CRAN in the next few days. -thomas Thomas Lumley Asst. Professor, Biostatistics tlumley at u.washington.edu University of Washington, Seattle -.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.- r-announce mailing list -- Read http://www.ci.tuwien.ac.at/~hor...

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

...y my use of f2c. > > suggestion: would it be possible to add a code snippet that tests > whether the user is trying to compile with f2c---and if so, bombs the > installation? (if "f77 --version == f2c" then die) I know the > problems are not R's fault, but it can percolate into R and it can > protect people like myself. The thing is, it does work on some platforms -- I do test i686 RH8.0 (updated with gcc 3.4.1) from time to time and it looks like I tested 1.9.0 during beta test. So `make check' is the only reliable test. (I've just run the current R-de...

...tic with g77, which forces us to use f2c. And despite your fears, that is working swimmingly for R as well as the by now 40 or so CRAN packages that are in the distro too, incl the ones like VR, Hmisc/Design, tseries, ... that contain Fortran code. > problems are not R's fault, but it can percolate into R and it can > protect people like myself. I'd argue that it wasn't f2c's fault, but maybe an unlucky mix of parts of your toolchain (gcc, binutils, libc, ...).

A guess (treat accordingly): Different BLAS versions are in use on the two different machines/versions. In one, near singularities are handled, and in the other they are not, percolating up to warnings at the R level. You can check this by seeing whether the estimated fit is the same on the 2 machines. If so, ignore the above. -- Bert Bert Gunter "The trouble with having an open mind

...gt;device.release = channel_subsystem_release; > > > + /* some cio DMA memory needs to be 31 bit addressable */ > > > + css->device.coherent_dma_mask = DMA_BIT_MASK(31), > > > + css->device.dma_mask = &css_dev_dma_mask; > > > > Question: Does this percolate down to the child devices eventually? > > E.g., you have a ccw_device getting the mask from its parent > > subchannel, which gets it from its parent css? If so, does that clash > > with the the mask you used for the virtio_ccw_device in a previous > > patch? Or are they two...

...e f2c. > > And despite your fears, that is working swimmingly for R as well as the by > now 40 or so CRAN packages that are in the distro too, incl the ones like > VR, Hmisc/Design, tseries, ... that contain Fortran code. > > > problems are not R's fault, but it can percolate into R and it can > > protect people like myself. > > I'd argue that it wasn't f2c's fault, but maybe an unlucky mix of parts of > your toolchain (gcc, binutils, libc, ...). > > ______________________________________________ > R-devel at stat.math.ethz.ch...

I am helping a student with some logistic regression analyses and we are getting some strange inconsistencies regarding a warning about factor levels being dropped when running predict.glm(, newdata = ournewdata) on the logistic regression model object. We have checked multiple times that the factor levels have been defined similarly on both data sets (one used to estimate model and the newdata)

On Wed, Nov 21, 2018 at 10:33 PM Eric Blake <eblake@redhat.com> wrote: > On 11/21/18 4:39 AM, Richard W.M. Jones wrote: > > On Wed, Nov 21, 2018 at 09:25:05AM +0000, Richard W.M. Jones wrote: > >> nbdkit: file.2: error: invalid request: offset and count are out of > range: offset=196608 count=512 > > > > Actually what happens even more precisely is that the

On Wed, 2 Jan 2019 09:54:24 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 Jan 2019 09:45:56 +0000 > Kristján Valur Jónsson <kristjan at rvx.is> wrote: > > > Any thoughts? Have code, will debug. The error itself is > > meaningless to me and I am deeply and utterly unfamiliar with samba > > code, but if you have any thought or

...; > mode" and qemu doesn't see any of it. So who can set the flag here ? > > The user should set it. You just tell user "to be able to use with > feature X, enable IOMMU". That's completely backwards. The user has no idea what that stuff is. And it would have to percolate all the way up the management stack, libvirt, kimchi, whatever else ... that's just nonsense. Especially since, as I explained in my other email, this is *not* a qemu problem and thus the solution shouldn't be messing around with qemu. > > > - Second, when using VIRTIO_F_IOMMU_P...