search for: subtly

On 4/8/2015 8:18 AM, John Perry wrote: > I found the developer's page: > > http://johannes.sipsolutions.net/Projects/dovecot-antispam > That project forked, and there are two versions now. They have subtly different configuration parameters, which trips folks up. See also: http://wiki2.dovecot.org/Plugins/Antispam/ where it mentions: >> Introduction >> >> The antispam plugin allows you to retrain the spam filter by simply >> moving emails in and out of the Spam folder....

...<daniel at zuster.org> Date: Wed Aug 14 23:15:39 2013 +0000 [llvm-build] Make Py3 compatible. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 188424 91177308-0d34-0410-b5e6-96231b3b80d8 Specifically, the problem is that configparser and ConfigParser apparently expose subtly different interfaces. Indeed, the attached patch fixes the problem for me (with python 2.7.4). I haven't yet investigated how the two modules are different, and obviously this isn't the right patch. More investigation coming up. Geoffrey -------------- next part -------------- A non-tex...

...to replace the memory model with something that supports backtracking -- this is doable (fairly) straightforwardly with the interpreter, but it would require some very complicated transformations to the code in order to do this within the JIT environment, and it would be quite tricky to avoid subtly breaking the semantics. That kind of approach is possible, probably, but not really something I want to attack right now. Thanks, Sarah

...control=NULL) trace("fact",tracer=tracefnc,print=FALSE) but I couldn't figure out how to access the return value of the function in the 'exit' parameter. The above also doesn't work for "..." arguments. (More subtly, it forces the evaluation of promises even if they are otherwise unused -- but that is, I suppose, a weird and obscure case.) Surely someone has solved this already? What I'm looking for is something very simple, along the lines of old-fashioned Lisp trace: > defun fact (i) (if (< i 1)...

...control=NULL) trace("fact",tracer=tracefnc,print=FALSE) but I couldn't figure out how to access the return value of the function in the 'exit' parameter. The above also doesn't work for "..." arguments. (More subtly, it forces the evaluation of promises even if they are otherwise unused -- but that is, I suppose, a weird and obscure case.) Surely someone has solved this already? What I'm looking for is something very simple, along the lines of old-fashioned Lisp trace: > defun fact (i) (if (< i 1)...

...llvm-dev wrote: > In contrast, the padding between fields in non-packed structs > disappears as soon as SROA runs. This can lead to violations of C > semantics, where padding fields should not change (because C defines > bitwise comparisons on structs using memcmp). This can lead to subtly > different behaviour in C code depending on the target ABI (we’ve seen > cases where trailing padding is copied in one ABI but not in another, > depending solely on pointer size). The IR type of an alloca isn't supposed to affect the semantics; it's just a sizeof(type) block...

...have no side-effect-free consumers. In contrast, the padding between fields in non-packed structs disappears as soon as SROA runs. This can lead to violations of C semantics, where padding fields should not change (because C defines bitwise comparisons on structs using memcmp). This can lead to subtly different behaviour in C code depending on the target ABI (we’ve seen cases where trailing padding is copied in one ABI but not in another, depending solely on pointer size). David

...Wed Aug 14 23:15:39 2013 +0000 > > [llvm-build] Make Py3 compatible. > > git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk at 188424 > 91177308-0d34-0410-b5e6-96231b3b80d8 > > Specifically, the problem is that configparser and ConfigParser > apparently expose subtly different interfaces. Indeed, the attached > patch fixes the problem for me (with python 2.7.4). I haven't yet > investigated how the two modules are different, and obviously this > isn't the right patch. > > More investigation coming up. > > Geoffrey -------------- n...

...) > > lgtm&pushed. I'm also happy with them (but it is late here and so I didn't want to give that as a formal review till I woke up tomorrow :-). It took a moment to get why the 'unsorted' links were sorted, at this time of night every GUID looks the same, but they are subtly altered to cause a specific re-sort order. Thank you very much! Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba

...TA=cor method=principal rotate=varimax proportion=0.9 scree where 'cor' is a correlation matrix (as in the R 'cor' function) This should get you a list of eigen values as well as a factor pattern matrix. Also why when I use the 'eigen' function in R does it seem to give a subtly different answer to the eigen values generated by the above program? Many thanks for any help Mark Strivens ----------------------- Dept. Molecular and Human Genetics Baylor College of Medicine Houston, USA strivens@bcm.edu [[alternative HTML version deleted]]

Hi, everybody. I have a list obj L, sth like $`aaa` [1] "5753" if the string 'aaa' is a returned value of a function foo(). what is the right syntax form of L$foo() I'm new to R, thanks in advance.

...th something that supports backtracking -- this is >> doable (fairly) straightforwardly with the interpreter, but it would >> require some very complicated transformations to the code in order to do >> this within the JIT environment, and it would be quite tricky to avoid >> subtly breaking the semantics. That kind of approach is possible, >> probably, but not really something I want to attack right now. >> > > Ok. The easiest (in some senses) approach would be to do what you say > above. However, you could probably arrange for a mixed approach to...

...memory model with something that supports backtracking -- this is > doable (fairly) straightforwardly with the interpreter, but it would > require some very complicated transformations to the code in order to do > this within the JIT environment, and it would be quite tricky to avoid > subtly breaking the semantics. That kind of approach is possible, > probably, but not really something I want to attack right now. Ok. The easiest (in some senses) approach would be to do what you say above. However, you could probably arrange for a mixed approach to work. in particular, you could...

...0b100111, sra>; > > > > Is this correct? > > Yes. IMHO, this is a poor way to do this kind of thing. It eventually leads to confusion where someone things SRA means "sra" and someone else thinks it meas "mysra." It gets worse as "mysra" acquires subtly different semantics than "sra." Better to write a separate pattern and use AddedComplexity to prefer it. Just a nugget of wisdom from personal experience. :) -Dave

...here any sort of package tracking system for CentOS? I'm used to Debian where I can view a changelog for each *Debian* specific package. This is great because I can see specifically what has been fixed and what known issues remain from release to release in the Debian package, which is subtly different from the upstream release. For instance, I can see what's changed from "apache2.1-debian.deb" to "apache2.2-debian.deb" by using the Debian Package Tracking System. (I'm fudging the package names, but you get the idea). Is there anything like that in Cen...

Hi, I am currently having the following problem with R 1.9.0. Any package that contains C or Fortran code hangs after I have built it and load it into R. I've tried this with RMySQL and udunits, originally I thought I had done something subtly wrong in configuring these packages; but I just had the same problem with a simple example R package that I wrote. I was able to build and load the package on a Linux system at school so I figure I've, hopefully, ruled out a programming problem on my part. The system I'm having the problem...

...ich has historically been a design goal of LLVM. The approach taken in WHIRL, which has a lot of advantages, is exactly to lower the IR. It seems strange that in the back end we have Machine* classes that correspond very closely to IR equivalents, but which don't share any code and often have subtly different interfaces. The approach taken in WHIRL is to progressively replace machine-independent bits of the IR with machine-dependent ones, with abstract instructions being replaced with machine instructions, abstract registers with machine registers, and so on. I would be interested to know...

...silon NFS exports were failing randomly among the nodes. Routing was fine. Network connectivity was fine. The short answer is that the default in 7.4, and I think in the nfs-utils-1.3.0-0.48.el7 package in particular, has changed. While NFS v4.0 was the default up to 7.3, the 7.4 protocols are subtly different: 1. Try NFS v4.1 first 2. Fail down to NFS v3 3. Fail down to NFS v2 The problem is that our Isilon works with NFS v4.0, not 4.1, but 4.0 is not in the fail-down path. The short-term answer is to specify nfsvers=4.0 in our autofs configuration files, which works like a charm. Like...

..., Ian, while I was working on the recent batch of security updates I noticed that the obvious backport of the related patch caused an HVM guest to be crashed as soon as a user inside that guest tried to ptrace a child process. While talking to Jan, I realized that in 4.2 the inject exception code subtly changed in a way that treats TRAP_debug as a HW event (that is triggered by no opcode) while before it was always treated as SW event. I believe Debian might be affected by the same as you also have a 4.1.x version in some stable, so I thought I share the backport I did. Jan was suggesting a sligh...

If libmagic isn't installed then the guestfs_file_architecture API doesn't work. This means that inspection will always return <arch>unknown</arch> for every guest. This subtly breaks a few features. In particular it was reported that the virt-builder/virt-customize --install option did not work because the "unknown" architecture of the guest was not compatible with the host. libmagic is a small, widely available C library, so the easiest fix is just to make i...