search for: pernicious

I've come across a curious and pernicious problem in llvm-rc. absolute.test checks that llvm-rc can accept a filename that is an absolute path. And it works just fine. Until you run it with a file that starts with "/c." These will fail: llvm-rc /crawl/through/some/path/to/my.rc llvm-rc /c/some/path/to/my.rc The option parser...

...hrough several iterations, I guess I've stumbled upon a Chesterton Fence and would appreciate some input on whether this is still needed. I see the original commit was Windows only, and was then updated to use `getenv` as a way to support this behaviour cross-platform. It's more weird than pernicious given that nothing is done with the result, but to me it feels dirty and confusing to query the process environment in this way. As such, I wonder 3 things: 1. Is this still needed? I don't know enough about the original toolchains affected to know if the problem still exists, but m...

...org <samba at lists.samba.org> Subject: Re: [Samba] Rocky linux 9 - Samba AD Morning, Metin: If you need current releases of Samba for RHEL 8 or RHEL 9 equivalent systems, I publish RPM building toolkits at: https://github.com/nkadel/samba4repo/ For a while, it got weird. Red Hat was perniciously refusing to publish the "devel" parts of certain RPMs, even though used in house to build Samba RPMs. Someone changed policy, and now they're in the "Code Ready Builder" channel or even in EPEL. It also has gotten weird for Samba 4.18, which has dependencies on updated li...

nbd_connect_unix|tcp had a tricky failure case. This is a consequence of allowing callers to mix synchronous and asynchronous calls, with multi-conn thrown into the mix. I think the new behaviour proposed here is better. We could do with a better way of classifying the state of connections, such as are they connectING. Rich.

...ection was connected. However this is a > problem if you are using them as a convenient way to set up a > multi-threaded main loop, because it can be that some of them have not > finished connecting, but then you issue commands on those connections > and that will fail. The failure is pernicious because most of the > time you won't see it, only if one connection is slow. So it's > (probably) better that the synchronous ‘nbd_connect_unix’ and > ‘nbd_connect_tcp’ should connect every connection object before > returning. Should this be a bool parameter for the caller to...

...ine that file could be NULL. Is there a way to annotate these macros so that the analyzer doesn't flag the code? I realize that's not strictly correct, since the macros don't exit, but, for better or for worse, the code is checked, and the numerous warnings potentially hide other, more pernicious ones. Thanks! -- Rick

My customer has dropdowns like this: Year Month Day If you submit with month selected and year blank, it subs in a year arbitrarily. Worse still, it subs in the year 5. I have no idea why. It seems a pernicious default. Anyway, they''re developing an app, they''re a designer turned coder, turning to a real programmer (me, allegedly) to make sense of the madness they''ve created. Obviously I could write something in JavaScript to handle it. What I want to know is, what is the most...

...ch= argument to plot, it is just recycled as necessary: plot(1:10,1:10,pch=1:2) gives alternating circles and triangles. The nasty bits come up especially with plot.formula: x<-1:10;y<-1:10 plot(y~x,subset=x%%2==1,pch=x%%2) - and the plotting symbols are *not* all the same. Even more pernicious, if missing values are involved: > y[x%%2==1]<-NA > plot(y~x,pch=x%%2) gives you the wrong symbols (in practice, this messes up things like plot(height~age,pch=sex) rather badly!). It would help to get a warning that the lengths don't match, but are there any good uses of the recyc...

...ection was connected. However this is a > problem if you are using them as a convenient way to set up a > multi-threaded main loop, because it can be that some of them have not > finished connecting, but then you issue commands on those connections > and that will fail. The failure is pernicious because most of the > time you won't see it, only if one connection is slow. So it's > (probably) better that the synchronous ‘nbd_connect_unix’ and > ‘nbd_connect_tcp’ should connect every connection object before > returning. > > For ‘nbd_connect_command’, it essential...

.... However this is a > > problem if you are using them as a convenient way to set up a > > multi-threaded main loop, because it can be that some of them have not > > finished connecting, but then you issue commands on those connections > > and that will fail. The failure is pernicious because most of the > > time you won't see it, only if one connection is slow. So it's > > (probably) better that the synchronous ‘nbd_connect_unix’ and > > ‘nbd_connect_tcp’ should connect every connection object before > > returning. > > Should this be a bo...

...ed, and r194073 for the kind of long-term a broken test has on code quality. Looking at the SVN log for test/ in clang, and to a lesser extent LLVM core, I've been doing nearly all the no-op test fixes in the last few months. Not all of them are related to trailing \ but those are the most pernicious kinds. It's a bad idea to gamble that I or someone else will always be around taking the time to manually verify old tests to see if they do what they're meant to do. > * Removing trailing \ will introduce the neat property that one > RUN line corresponds precisely...

...gt; upon a Chesterton Fence and would appreciate some input on whether this > > is still needed. I see the original commit was Windows only, and was > > then updated to use `getenv` as a way to support this behaviour > > cross-platform. > > > > It's more weird than pernicious given that nothing is done with the > > result, but to me it feels dirty and confusing to query the process > > environment in this way. As such, I wonder 3 things: > > > > 1. Is this still needed? I don't know enough about the original > > toolchains af...

...as at least one connection was connected. However this is a problem if you are using them as a convenient way to set up a multi-threaded main loop, because it can be that some of them have not finished connecting, but then you issue commands on those connections and that will fail. The failure is pernicious because most of the time you won't see it, only if one connection is slow. So it's (probably) better that the synchronous ‘nbd_connect_unix’ and ‘nbd_connect_tcp’ should connect every connection object before returning. For ‘nbd_connect_command’, it essentially ignored multi-conn anyway,...

...as at least one connection was connected. However this is a problem if you are using them as a convenient way to set up a multi-threaded main loop, because it can be that some of them have not finished connecting, but then you issue commands on those connections and that will fail. The failure is pernicious because most of the time you won't see it, only if one connection is slow. So it's (probably) better that the synchronous ‘nbd_connect_unix’ and ‘nbd_connect_tcp’ should connect every connection object before returning. For ‘nbd_connect_command’, it essentially ignored multi-conn anyway,...

Hello R friends, I'm wondering why I get funny qqnorm() results. It seems that they should all be reflected in the normal qqline(). For instance: if I qqnorm() bimodal or uniform data I get a sigmoidal in which the qqnorm() points lie above the qqline() at -ve theoretical quantiles, and the qqnorm() points lie below the qqline() at +ve theoretical quantiles. Yet I expect such platykurtic

...the kind of long-term a broken test has on code quality. > > Looking at the SVN log for test/ in clang, and to a lesser extent LLVM > core, I've been doing nearly all the no-op test fixes in the last few > months. Not all of them are related to trailing \ but those are the most > pernicious kinds. > > It's a bad idea to gamble that I or someone else will always be around > taking the time to manually verify old tests to see if they do what they're > meant to do. > This mostly seems to address the challenge of fixing existing tests, which certainly is hard, but...

Patch 1/6 was posted before and I didn't change it: https://www.redhat.com/archives/libguestfs/2019-May/thread.html#00134 That doesn't necessarily mean I shouldn't change it, I'm posting it again because the other patches depend on it. The main change in this series is we add three new API functions: nbd_aio_is_created - connection has just been created

...d r194073 for the kind of long-term a broken test has on code quality. > > Looking at the SVN log for test/ in clang, and to a lesser extent LLVM core, I've been doing nearly all the no-op test fixes in the last few months. Not all of them are related to trailing \ but those are the most pernicious kinds. > > It's a bad idea to gamble that I or someone else will always be around taking the time to manually verify old tests to see if they do what they're meant to do. > > >> >> Removing trailing \ will introduce the neat property that one RUN line correspond...

On Sun, Dec 8, 2013 at 2:11 AM, Alp Toker <alp at nuanti.com> wrote: > I'd like to propose deprecating and shortly thereafter removing the lit > test runner feature that concatenates RUN lines ending in a trailing \ > I'm really opposed to this. Especially for the Clang test suite where run lines are often *very* long and hard to organize, read, and edit without this

So after I updated all my gems, I started getting: /Library/Ruby/Gems/1.8/gems/activesupport-2.3.4/lib/active_support/ dependencies.rb:105:in `const_missing'': uninitialized constant Test::Unit::TestResult::TestResultFailureSupport (NameError) from /Library/Ruby/Gems/1.8/gems/test-unit-2.0.3/lib/test/unit/ testresult.rb:28 from /Library/Ruby/Site/1.8/rubygems/custom_require.rb:31:in