similar to: metadata plugin problems

Hi, I'm working on a Kolab related project and wanted to use dovecot on my dev machine. However I'm stuck with the metadata-plugin. I "solved" the permissions problems but now I get dict: Error: file dict commit: file_dotlock_open(~/Maildir/shared-metadata) failed: No such file or directory Before that, I had dict { metadata = file:/var/lib/dovecot/shared-metadata but

On 2016-04-22 09:07 PM, Timo Sirainen wrote: > On 22 Apr 2016, at 15:17, Giovanni S. Fois <giovanni at giovannisfois.net> wrote: >> In order to tell if a mailbox is enabled to send out the notification, the plugin >> looks out for the following mailbox metadata key: >> /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify >> >> If the

In Dovecot 2.2.4 metadata-plugin crach on setmetadata but worked on ascii folders? but not worked on utf7 (non ascii) folders. [13-Jul-2013 19:15:36 +0400]: [F537] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS

I also tried the following, with no compilation errors, but segfault, core dumped: *LLVMContext& C = is->getContext(); Value* values[size]; for(int gy=0;gy<size;gy++){ values[gy]=ConstantInt::getSigned(Type::getInt64Ty(C),array[gy]); } llvm::ArrayRef<Value*> bla = values[size]; is->setMetadata("path",MDNode::get(C,bla));* On Fri, May 3, 2013

On dovecot 2.2.12 compiled from source I use ActiveSync with kolab-syncroton. When running a test i have this imap log: [29-Mar-2014 22:58:25 +0200]: [F658] S: A0004 OK Getmetadata completed. [29-Mar-2014 22:58:25 +0200]: [F658] C: A0005 SETMETADATA INBOX (/private/vendor/kolab/activesync "{\"DEVICE\":{\"601099122\":{\"ID\":

Hello group, Per my posting on the Clang Newsgroup. I'm interested in doing some loop optimizations, towards this end I would like to add some custom Metadata to a Loop header. Loops in LLVM are represented using BasicBlocks, but unfortunately you can NOT add MetaData to a BasicBlock. Although you can add Metadata to an instruction. So I'm proposing to add the Metadata manipulation

Hello everyone, I want to pass a set of integers using metadata but I don't know how. I have tried: the integers are in array[] *1. * LLVMContext& C = is->getContext(); Value* values[size]; for(int gy=0;gy<size;gy++){ values[gy]=ConstantInt::getSigned(Type::getInt64Ty(C),array[gy]); } *is->setMetadata("path",MDNode::get(C,values));* failes when setMetadata(),

            Hello everyone, As i saw that is not possible to add metadata to a basic block, it is possible to add more metadata fields to an instruction? I saw that in the definition of setMetadata(), it updates/replaces the metadata if already existent. As far as I understand, updates=replaces, not updates OR replaces. I add metadata using :             LLVMContext& C =

Hello everyone! I just released dovecot-metadata-8, which is an implementation of RFC 5464 (IMAP METADATA), allowing to add comments/annotations/metadata to folders of an email account. The major feature is that it works with Akonadi, or more specifically the Kolab backend thereof, while being dovecot-2.0 compatible. The module consists of 3 plugins, two IMAP frontends and one backend: *

Hello! We are pleased to announce the availability of a new stable GnuPG-2 release: Version 2.0.15. The GNU Privacy Guard (GnuPG) is GNU's tool for secure communication and data storage. It can be used to encrypt data, create digital signatures, help authenticating using Secure Shell and to provide a framework for public key cryptography. It includes an advanced key management facility

Hi, an older thread about removing metadata says to use “setMetadata(Kind, nullptr)” to drop the metadata from the instruction. I have using this method without success. When I look at inside the IR code the metadata are still there, any idea why is that? Thanks. Best, Simone

Hi list, I found relevant documentation regarding DebugInfo creation in the LLVM IR bytecode. It can be done for compileunits, functions, and other constructs, with the help of DIBuilder class. However I can't save debug information related to individual llvm::Instructions. I tried DebugLoc, DILocation setting directly with setMetadata(). I tried other ways, for e.g.:

Debian Wheezy dovecot 2.2.4 (deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2.patched main) dovecot-metadata-plugin v14 /var/lib/dovecot 777 dovecot:dovecot /var/lib/dovecot/shared-metadata 700 dovecot:dovecot /var/run/dovecot 777 dovecot:dovecot /var/run/divecot/dict 666 mail:dovecot Test1 - create calendar UTF7 mailbox (no errors in

Ultra short version: Why cant I set the following mailbox metadata key? /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify Let me explain the context: I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22 The push-notification plugin is supposed to send out a notification whenever a mailbox get a new email message. In order to tell if a mailbox

----- Original Message ----- > From: "Pekka Jääskeläinen" <pekka.jaaskelainen at tut.fi> > To: "Paul Redmond" <paul.redmond at intel.com> > Cc: "Hal Finkel" <hfinkel at anl.gov>, "Tobias Grosser" <tobias at grosser.es>, "<llvmdev at cs.uiuc.edu>" > <llvmdev at cs.uiuc.edu> > Sent: Tuesday, March 5,

On 03/05/2013 07:12 PM, Redmond, Paul wrote: > Attached is my most recent patch for clang. Maybe someone wants to play with > it or has ideas on how to refine the llvm.mem metadata generation. + } else if (I->mayReadOrWriteMemory()) + I->setMetadata("llvm.mem.parallel_loop_access", + L.GetLoopID(I->getContext())); + } Here we want to not add

Dear llvm-ers, I am trying to attach a customized metadata to llvm instructions. Let's say, I want to attach some number to each instruction. I am trying to use void Instruction::setMetadata(unsigned KindID, MDNode* Node) but I am not sure how to create a brand new instance of an MDNode. Do you have any code samples demonstrating how to do that? Due to some tool dependencies, I am using

> Dear llvm-ers, > I am trying to attach a customized metadata to llvm instructions. > Let's say, I want to attach some number to each instruction. > I am trying to use > > void Instruction::setMetadata(unsigned KindID, MDNode* Node) > > but I am not sure how to create a brand new instance of an MDNode. > Do you have any code samples demonstrating how to do that?

On 12/21/11 11:24 PM, Oksana Tkachuk wrote: > Hello, > Thank you very much for the pointers. > I am are able to create new MDNodes, filled with some constants, and > attach them > to llvm instructions. However, the metadata map is not getting updated > as expected. > For example, instead of the expected new entry If you look at PoolMDPass::runOnModule(), you'll see that

Yes, it sounds good. I can try tomorrow. Thank you for your advice ! On Thu, May 2, 2013 at 5:43 PM, Logan Chien <tzuhsiang.chien at gmail.com>wrote: > I think the better solution should be: > > > LLVMContext& C = is->getContext(); > Value *values[] = { > ConstantInt::getSigned(Type::getInt64Ty(C), *scsr*), > MDString::get(C, *"path"*) > };