search for: check_

Hi all, I'm looking for an easy way to lookup numbers from the database so I can fork calls from my daughters friends onto her IP phone/answering system. I'm looking for something very similar to LookupBlacklist, but I'm already using LookupBlackist to filter out telemarketers. What I'm doing now is adding multiple exten=> lines to my extensions.conf file to match those

...test for it, > I actually had no idea how to trigger this codepath and have never used R. I see. But note that you misunderstood (probably my bad English): I did *NOT* find a test for it (and showed a case that did not work as test, as it does not trigger an error [remember the macro is CHECK_..() and actually shouled produce a useful error message in a -- yet to find -- test case. > If you are curious, the upstream check for clang-tidy is > http://reviews.llvm.org/D18766 > You may consider running some of the other clang-tidy checks on your source > base, t...

...ers, Matt On Thu, Apr 7, 2016 at 6:46 AM, Martin Maechler <maechler at stat.math.ethz.ch> wrote: > >>>>> Matthew Fowles Kulukundis <matt.fowles at gmail.com> > >>>>> on Tue, 5 Apr 2016 11:17:30 -0400 writes: > > > All~ > > CHECK_this_length macro expands to multiple statements making it > unsafe to > > use in a single line `if` statement (as is happening near line > 335). This > > fixes the macro using the standard `do { } while (0)` macro trick. > > yes, but you forgot the closing '}...

...ake for runtimes (i.e. where path/to/my/llvm-project/llvm/runtimes/CMakeLists.txt is the top-level one), you may not have a fully working toolchain yet. For example, in case of Fuchsia, our sysroot contains only libc, so when we're doing the runtimes build, and one of the runtimes tries to use check_cxx_compiler_flag, which behind the scenes tries to compile and link a small C++ binary, that check is going to fail not because the flag isn't supported, but because we don't have libc++ yet (that's what we're trying to build right now). So we need to be really careful and avoid int...

As far as I can tell, the "replace" parameter is all or nothing. What I am looking for is something like the exec/onlyif parameter that I can use to conditionally replace a file. Any thoughts ? “Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.” Bill Waterson (Calvin & Hobbes) -- You received this

...) pairs, also un-quoting the value. It would not map 1:1 the C implementations, but in OCaml it would be so much easier than in C (and that is basically what I'd have liked to do in the first place when implementing parse_os_release, but it'd have been so much memory waste). > +let rec check_linux_root mountable data = > + let os_type = OS_TYPE_LINUX in > + data.os_type <- Some os_type; > + > + let rec loop = function > + | (release_file, parse_fun) :: tests -> > + if verbose () then > + eprintf "check_linux_root: checking %s\n%!"...

...581]: <= bdb_equality_candidates: (gidNumber) not indexed Mar 6 00:22:29 sam3dc slapd[5581]: <= bdb_equality_candidates: (uid) not indexed [2018/03/06 00:22:29.101185, 1] auth/server_info.c:447(samu_to_SamInfo3) Failed to get groups from sam account. [2018/03/06 00:22:29.101275, 0] auth/check_samsec.c:492(check_sam_security) check_sam_security: make_server_info_sam() failed with 'NT_STATUS_INTERNAL_DB_CORRUPTION' [2018/03/06 00:22:29.101322, 5] auth/auth.c:271(check_ntlm_password) check_ntlm_password: sam authentication for user [sundata] FAILED with error NT_STATUS_INTERNAL...

We run around 5 dovecot (debian etch 1.0.rc15) POP/IMAP 'nodes' using the LVS load balancer and an NFS based SAN. it works pretty well. I love the robustness of load balancing POP/IMAP. We do a reasonable amount of throughput through these especially at peak times pushing our SAN to around 1.5k IOP/s We currently have two issues with this setup. One of which is NFS index corruption

...----------------------+ | netpbm | | O | Render icons from guests. | diff --git a/builder/Makefile.am b/builder/Makefile.am index a2509d7..ab27442 100644 --- a/builder/Makefile.am +++ b/builder/Makefile.am @@ -286,9 +286,7 @@ TESTS = \ test-virt-index-validate.sh check_PROGRAMS = -if HAVE_YAJL TESTS += test-virt-builder-list-simplestreams.sh -endif if ENABLE_APPLIANCE TESTS += test-virt-builder.sh diff --git a/builder/sources.ml b/builder/sources.ml index 149db6f..37027d6 100644 --- a/builder/sources.ml +++ b/builder/sources.ml @@ -83,14 +83,7 @@ let parse_...

...o the fact that Gentoo's GCC has _FORTIFY_SOURCE always enabled, which causes a ton of superfluous redefinition warnings when adding this flag to CPPFLAGS. Finally, I forgot to add one patch from our repo, namely that noinst_ is the wrong prefix for test programs. These should be prefixed with check_, which causes them only to be compiled when 'make check' is run, making the overall build faster. Regards David

[Cross-post to llvm-dev to make sure everybody relevant sees this] Hi, I'm currently trying to simplify the libc++/libc++abi/libunwind build systems and testing setup. In doing so, I am encountering issues related to "unusual" ways of building them. By unusual, I just mean "not the usual monorepo build with LLVM_ENABLE_PROJECTS". I would like to pin down what the set of

...(3): po: Update German translation. po: Update German translation. ntprint/tests: Fix some typos. J?zef Kucia (9): d3dx9/tests: Add tests for D3DXCreateRenderToEnvMap. d3dx9: Add ID3DXRenderToEnvMap interface stub. d3dx9/tests: Improve test failure messages for check_{ref, release}. d3dx9/tests: Use inline functions instead of check_pixel_{1bpp, 2bpp, 4bpp} macros. d3dx9: Get rid of ID3DXFontImpl. d3dx9/tests: Add tests for ID3DXFont::PreloadText. d3dx9/tests: Add tests for ID3DXFont::GetGlyphData. d3dx9: Recognize X8B8G8R8 pixel fo...

Inspired by libvirt's virCommand* internal mini-library, this adds some internal APIs for running commands. The first patch contains the new APIs. The subsequent patches change various parts of the library over to use it. Rich.

v10: https://www.redhat.com/archives/libguestfs/2017-July/msg00245.html No actual change here, but I rebased and retested. Also this series now does not depend on any other patch series since everything else needed is upstream. Rich.