search for: unnotic

...the feeling that custom messages (Verbose(1,...)) do not stand out enough on the CLI? We're sending messages like "Extension 123 is unknown" to the output and that should tell the user why a call to 123 fails but users fre- quently crank up the verbosity to 3 or 10 so our messages go unnoticed in many cases. My idea was to use terminal escape sequences to make my messages bold and black on yellow background. apps/app_verbose.c: static int verbose_exec(struct ast_channel *chan, void *data) { ... switch (vsize) { case 0: - ast_verbose("%s...

...e with a domain group today (DC and DM w/ samba-4.6.8) Solution: net cache flush, recreate the group via samba-tool, and --gid-number before that the group had a gid of 3000013 and wasn't shown on the DM, even when the idmap range there was up to 9999999. Your reported bug still sits there unnoticed, right? Stefan

Hi. I noticed that when non-64bit variable is given as a second argument to atomic_add_64() function, the result is invalid. I found few places where such situation occurs. I wonder how this got unnoticed with ztest, which fails on me within a few seconds (after I started to use Solaris atomic operations) on assertions. Maybe this only doesn''t work when compiled with gcc? Not sure, but most of the time 64bit variables are used properly. Anyway, the patch is here: http://people.freebsd...

...ekRTL8111b. Because a) it does not work with the stock driver included in Centos 5.1 and b) I am very lazy and I do not like manually compiling modules each time a new kernel is installed (not to mention that I never forget anything, except for the important things which always go under the radar unnoticed) I ripped the r1000 rpm from rpmforge and created a dkms based rpm for the r8168 driver. Since others might find a use for it too, I have uploaded the rpm (and it's corresponding source) at http://wolfy.fedorapeople.org/dkms-r8168/. I am also thinking of linking to it from the above m...

...ar-evolution 2>&1 | grep > "Loop bb: 100 iterations" 2>&1 doesn't evoke the desired behavior; the RUN line is unfortunately interpreted by TCL rather than a regular shell. The llvm.exp bug has allowed this and a variety of other common bourne-shell-isms to slip by unnoticed. Dan -- Dan Gohman, Cray Inc.

Jim Grosbach wrote: > To say that another way, is the assembler correctly diagnosing a previously > unnoticed problem in the project source code, or is the assembler not > behaving correctly according the the documented Intel assembly mnemonics? Where are the authoritative instruction set pages? If such a thing were readily available, why are there gaps in the current implementation? A quick Googli...

Sorry to have to post this again - it was probably under the wrong subject and went unnoticed. Is there a standard for providing user documentation for methods that I expose through we services? The default documentation (method names and return types) that appears when the user visits http://localhost:3000/backend/invoke is concise and correct, but a bit terse. How can I give my users...

...nI.addRange(LR); } Should this actually extend from the load index to the def index since value intervals are exclusive at end? Otherwise, the interval for the spill doesn't include the use of the reloaded register, which doesn't make sense to me. I think this probably went unnoticed because nothing happens with intervals after spill code generation in the current codebase. -Dave

...> > Generally, a package can not be on CRAN if it has any warnings, so I > don't think this change would have any impact on CRAN packages. Isn't > this also true for bioconductor? Having a tests/warn.R file with: warning("boom") passes through R CMD check --as-cran unnoticed. Same with: if (sample(2) == 1) message("It's your lucky day today!") /Henrik PS. Does testthat signal that? > > Hadley > > -- > http://hadley.nz

R-help, I'm the primary developer for an increasingly large R package with over three thousand lines of code. Unfortunately, do the complexity of the code, I sometimes am required to change several interoperating parts of the package before testing for bugs and performance. And sometimes unnoticed syntax errors slip in that cause Rcmd check / INSTALL to fail with such messages as: Error in parse(file, n, text, prompt) : syntax error on line 223 Execution halted My question: what file should I be checking for line 223? When running Rcmd INSTALL, the previous version is restored on an inst...

A handful of files in compiler-rt/builtins use the macro "__SOFT_FP__". All the uses are along the same lines. Here's a representative example from compiler-rt/lib/builtins/fixdfdi.c: #ifndef __SOFT_FP__ // Support for systems that have hardware floating-point; can set the invalid // flag as a side-effect of computation. ... #else // Support for systems that don't have

...f forwarding anything, I did not set up any authentication methods. So anyone who tries fails to authenticate. With fail2ban in place I get 200-500 daily SASL "fail to authenticate" instances. In contrast, several months ago fail2ban either died or did not restart correctly. This went unnoticed for about a week. During that time I got 10000-32000 daily "failed to authenticate". Jon -- Jon H. LaBadie jon at jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)

Dear Users, I already posted this question: it either went unnoticed, or it is to basic (if this is so, please sent me a hint). I would like to know if there is a way to add a common legend to an arrangement of plots. In the example below, I get four plots in my device. each one has a density for 1995 and one for 2006. I have found that using legend or smartlegend...

...ueType in_vectype, ValueType out_vectype>: > def v4i32: XSHWVecInst<v4i32, v8i16>; > Is this pattern as intended, or did I find a real problem? Looks like a bug to me. xshw (extend signed half-word(16bits) to word(32bits)) takes a v8i16 and produces a v4i32. This has likely gone unnoticed as there is only one type of vector register class (i.e. VECREG) that is used for all vectors. Nice catch :) Are there more of these? kalle -- "Modern computing machines are very complex objects" -von Neumann introducing the NORC, 1954

Kalle Raiskila <kalle.raiskila at nokia.com> writes: > Looks like a bug to me. xshw (extend signed half-word(16bits) to > word(32bits)) takes a v8i16 and produces a v4i32. This has likely gone > unnoticed as there is only one type of vector register class (i.e. > VECREG) that is used for all vectors. > > Nice catch :) Are there more of these? I don't know. I stopped implementing the stricter typechecking when I saw this. I wanted to make sure there wasn't some official trickery...

Jim Grosbach wrote: > Also, please elaborate on why this is a good change. Because gas accepts it > isn’t sufficient reason in and of itself. That they're valid instructions isn't sufficient reason? Should I additionally say that linux.git uses them? I wrote: > The instructions btr and bts are perfectly valid, and have existed since > Intel 386.

...t >> isn’t sufficient reason in and of itself. > > That they're valid instructions isn't sufficient reason? Should I > additionally say that linux.git uses them? > Is the diagnostic incorrect? To say that another way, is the assembler correctly diagnosing a previously unnoticed problem in the project source code, or is the assembler not behaving correctly according the the documented Intel assembly mnemonics? If the former, the fix belongs in the project, not the assembler. If the latter, then we should absolutely fix the assembler. From your emails, it is unclear to me...

...#39;3000013', this is an xidNumber and isn't used anywhere except on a DC. It is also probably one of the Well Known SIDs, so you shouldn't remove and recreate one of these. Which leads us to the obvious question, what was the group name ? > > Your reported bug still sits there unnoticed, right? Not unnoticed, just not yet resolved ;-) Rowland

...oup-info="gfass" ARBEITSGRUPPE\gfass:x:10580: I chose 10850 just to make sure I am away from other IDs. Is there a simple way to read the (highest) used group-id? btw: ACLs work now for the specific folders/ groups, that is not the problem. >> Your reported bug still sits there unnoticed, right? > > Not unnoticed, just not yet resolved ;-) Ah, I see ;-) good.

The patch series looks generally fine, but it really needs a test ... We find that having tests prevents unnoticed regressions from happening later. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html