Displaying 7 results from an estimated 7 matches for "str_begins".
Did you mean:
str_begin
2019 Apr 02
4
sieve scripts not synching for 2.3.5.1 pre-built
On 2 Apr 2019, at 22.37, Timo Sirainen via dovecot <dovecot at dovecot.org> wrote:
>
> On 2 Apr 2019, at 17.03, Jan-Pieter Cornet via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote:
>>
>> Hi,
>>
>> We're synching mailboxes, changing format from maildir to mdbox, using doveadm backup/doveadm sync.
>>
>> When
2019 Apr 14
0
[PATCH] Re: Solr connection timeout hardwired to 60s
...lr/fts-solr-plugin.c 2019-04-14 14:37:46.059433864 +0200
@@ -10,6 +10,8 @@
#include "fts-solr-plugin.h"
+#define DEFAULT_SOLR_BATCH_SIZE 1000
+
const char *fts_solr_plugin_version = DOVECOT_ABI_VERSION;
struct http_client *solr_http_client = NULL;
@@ -37,6 +39,10 @@
} else if (str_begins(*tmp, "default_ns=")) {
set->default_ns_prefix =
p_strdup(user->pool, *tmp + 11);
+ } else if (str_begins(*tmp, "batch_size=")) {
+ set->batch_size = atoi(*tmp + 11);
+ } else if (str_begins(*tmp, "no_soft_commit")) {
+ set->no_soft_commit =...
2019 Apr 13
3
Solr connection timeout hardwired to 60s
On 4/13/2019 4:29 AM, John Fawcett via dovecot wrote:
> If this value was made configurable people could set it to what they
> want. However the underlying problem is likely on solr configuration.
The Jetty that is included in Solr has its idle timeout set to 50
seconds. But in practice, I have not seen this timeout trigger ... and
if the OP is seeing a 60 second timeout, then the 50
2018 Oct 18
1
[dovecot quota-status] error "Invalid character in path"
Hello,
I'm using using:
- dovecot 2.3.3 (dcead646b)
- postfix 3.3.1
- dovecot "quota = maildir:User quota"
I'm facing the error:
"quota-status: Error: quota-status: Client sent
invalid recipient address: Invalid character in path"
This occurred with this e-mail address:
"John Smith"@keit.eu
Well I know it is not a conventional address but it is normally
2009 May 20
2
[LLVMdev] Getting exceptions to work?
Duncan Sands wrote:
> I would just use the C personality function, __gcc_personality_v0, if
> I were you. It should know where to jump to because the code generators
> record the invoke unwind target in the dwarf exception handling info in
> the object file.
>
>
So I tried what you suggested, and it just gives me a bus error:
define i32 @main(i32, i8**) nounwind {
2009 May 19
0
[LLVMdev] Getting exceptions to work?
Talin wrote:
> Nicolas Geoffray wrote:
>> Hi Talin,
>>
>> You're not using the llvm intrinsics for exception handling, so your
>> code won't work. Using _Unwind_RaiseException should be OK, but your
>> main function must at least use llvm.eh.exception,
>> llvm.eh.selector.i32/64 and probably __cxa_begin_catch and __cxa_end_catch.
>>
>
2009 May 19
5
[LLVMdev] Getting exceptions to work?
Nicolas Geoffray wrote:
> Hi Talin,
>
> You're not using the llvm intrinsics for exception handling, so your
> code won't work. Using _Unwind_RaiseException should be OK, but your
> main function must at least use llvm.eh.exception,
> llvm.eh.selector.i32/64 and probably __cxa_begin_catch and __cxa_end_catch.
>
Let me ask a follow-up question then - if the