search for: querying

In current Xapian SVN HEAD, there is a bug in the query parser concerned with the handling of wildcard terms with a "+" prefix. Specifically, a query such as "+foo* bar" will be parsed by the query parser into Xapian::Query("bar") if there are no terms in the database which start "foo". Instead, since the "+" term cannot be matched, I believe

On 04/27/2017 04:31 PM, Stefano Ricci wrote: > Here is the backtrace of the libvirt process just started [Just a side note, you shouldn't top post on technical lists. Gmail sucks at this.] > > https://pastebin.com/R66myzFp Looks like libvirtd is trying to spawn /usr/bin/qemu-system-x86_64 but it takes ages to init. In the debug logs you might see the actual command line that

this is my named.log file. Have the dark line problem? best regards. May 10 08:11:08 samba named[752]: queries: info: client 127.0.0.1#54056 ( WPAD.test.com): query: WPAD.test.com IN A + (127.0.0.1) May 10 08:11:08 samba named[752]: queries: info: client 127.0.0.1#54056 ( WPAD.test.com): query: WPAD.test.com IN AAAA + (127.0.0.1) May 10 08:11:08 samba named[752]: queries: info: client

On 04/29/2017 04:38 AM, Stefano Ricci wrote: > 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>> Here is the backtrace of the libvirt process just started >> >> [Just a side note, you shouldn't top post on technical lists. Gmail >> sucks at this.] >> >>> >>>

What are these dns queries for? I'd like to disable them but I cant find any obvious reference to them in the asterisk source. I'm running Asterisk 1.4.21.2 I call voicemail and immediately hang up: I called from a sip client called line1, but I have no idea where 08c5b9e0 is coming from... 14-Jun-2009 12:37:07.926 queries: info: client 127.0.0.1#41105: query:

Tasty Planet loads, and then complains that a module is missing - WINMM.DLL I checked - wine DOES have this dll in it's system32 folder. Wine produces this log: Code: wine: Unhandled page fault on write access to 0x00650180 at address 0x7ee58a73 (thread 0021), starting debugger... Unhandled exception: page fault on write access to 0x00650180 in 32-bit code (0x7ee58a73). Register dump:

Hello, This is one problem at the time :) I have a data frame df that looks like this: time partitioning_mode workload runtime 1 1 sharding query 607 2 1 sharding query 85 3 1 sharding query 52 4 1 sharding query 79 5 1 sharding query 77 6 1 sharding query 67 7 1

2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/27/2017 04:31 PM, Stefano Ricci wrote: >> Here is the backtrace of the libvirt process just started > > [Just a side note, you shouldn't top post on technical lists. Gmail > sucks at this.] > >> >> https://pastebin.com/R66myzFp > > Looks like libvirtd is trying to spawn

2017-04-29 7:24 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: > On 04/29/2017 04:38 AM, Stefano Ricci wrote: >> 2017-04-28 14:33 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>: >>> On 04/27/2017 04:31 PM, Stefano Ricci wrote: >>>> Here is the backtrace of the libvirt process just started >>> >>> [Just a side note, you shouldn't

Hello all I finally caved in and decided I should build my own query instead of relying on QueryParser to do the job for me, but I''ve hit a strange problem.. Here''s how I build my query: #Main query query = Ferret::Search::BooleanQuery.new #Build query to match types typesquery = Ferret::Search::BooleanQuery.new @selected_types.each{|type| typesquery.add_query(

...y, forwarding to the NT boxes. Sendmail has > been configured to WorkAroundBrokenAAAA. The box is running > STABLE from about the end of February. When I query each NT > box directly with nslookup they give the appropriate responses > without fuss. > > Since something seems to be querying each root server in turn > repeatedly (and failing), I whittled down my root file to > two root servers and restarted named as an experiment. > It still queried every one of them, not just the two it knew about. > > I see the following almost constantly: > > 621.091795 bsdbox...

Hello, I used R a lot one year ago and now I am a bit rusty :) I have my raw data which correspond to the list of runtimes per minute (minute "1" "2" "3" in two database modes "sharding" and "query" and two workload types "query" and "refresh") and as a list of char arrays that looks like this: > str(data) List of 122 $ :

Today we noticed that keywords can't be searched as prefixed terms. Or that's what it looks like anyway. I tested and, or, and not. ╰─% NOTMUCH_DEBUG_QUERY=y notmuch search 'subject:"and"' Query string is: subject:"and" notmuch search: A Xapian exception occurred A Xapian exception occurred parsing query: Syntax: <expression> AND <expression> Query

On 11/05/15 18:56, bar?? tombul wrote: > What is your opinion about the cause and solution I thought I gave you the cause, your clients are trying to update their own dns records, they are denied and then the system you have set up to update dns carries out the update. The solution, stop the clients trying to update their own records, your clients are probably windows and if so, it is a

<earlier, David Rankin wrote to no avail:> Mates, I have been watching a developing problem over the past few weeks. Most likely a M$ patch to XP that has caused problems. What happens is that XP clients try to open the standard "File" -> "Open" dialog (like in word, or whatever) and the file open dialog hangs and stops responding for 15 seconds or so. I have

I probably should've used boolean terms in addition to numeric values when indexing, but currently I have a set of numeric values[1] and trying to avoid having to reindex ~250GB DBs (and asking numerous users to do the same). Say I have a bunch of values which I want to filter a query against. If I had boolean terms, it could just OP_OR against the whole set. IOW, this is what notmuch does

...e ip=10.92.50.72 bcast=10.92.50.255 nmask=255.255.255.0 TESTPARM ./testparm Load smb config files from /usr/local/samba/lib/smb.conf Processing section "[andyhome]" Processing section "[tmp]" Loaded services file OK. NMBLOOKUP /usr/local/samba/bin> nmblookup -B macdui _SAMBA_ querying _SAMBA_ on 10.92.50.72 name_query failed to find name _SAMBA_ ---------------------------------------------------------------------------- ----------------------------------------- nmblookup -B macdui '*' querying * on 10.92.50.72 10.92.50.72 *<00> ------------------------------------...

Parse the query string from URLs, and pass it as new add_drive optarg; use it when building the file= URL for qemu. Accept query string only for http and https protocols, for now. --- Possibly it looks like an ad-hoc solution for http(s), although I'm not sure how it could possibly be generalized somehow (maybe "extra params" which would be the query string for http(s)?).

*Hi all,* * * *The following is my general idea for the project. For a complete query parser I still need to consider more details. Please give me feedback because the description of this project is lack of detailed information, and I can submit my proposal without giant deviation.* * * design principle of query parsing: 1) better understanding user input. All search engine do is understanding

Hi all, Is there a way to have searches no use some indexed fields, when processing a query? context: I have a model Foo that holds some information in two languages : - text1_nl, text2_nl, text3_nl and - text1_en, text2_en, text3_en Some other fields are common to both languages and indexed as well - first_name, last_name Depending on the visitor language choice I need to exclude the