search for: report_errors

If an ESX guest has a snapshot, the path the libvirt driver gives us will look like: [yellow:storage1] RHEL4-X/RHEL4-X-000003.vmdk instead of: [yellow:storage1] RHEL4-X/RHEL4-X.vmdk The current path mangling code does take this into account. This change makes it use the current mechanism first, but try again after removing a '-\d+' suffix if it gets a 404. Trying twice should make it

We were seeing 100% failure rates transferring 10G disk images from ESX on a particular setup. We also weren't spotting the transfer failure, and dying with a strange error from libguestfs. These 2 patches fix the error check which should have made it obvious what was failing, and the underlying error.

Pyxml/xmlproc is being used in tools/xen/xm/xenapi_create.py but is unmaintained for several years now. xmlproc is used only for validating XML documents against a DTD file. This patch replaces the pyxml/xmlproc based XML validation with code based on lxml, which is actively maintained. Signed-off-by: Stephan Peijnik <spe@anexia.at> diff -r 6e0ffcd2d9e0 -r 7082ce86e492

...namespace. I'm trying to port from a Linuxconf virtual WU-IMAP type config. So - I compiled but then decided I wanted mysql so I tried to reconfigure and now getting compile errors. Looks like I'm missing something? /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0x25): In function `report_errors': : undefined reference to `ERR_get_error_line_data' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xa4): In function `vio_ssl_read': : undefined reference to `SSL_read' /usr/lib/mysql/libmysqlclient.a(viossl.o)(.text+0xc5): In function `vio_ssl_read': : undefined reference...

On 16 June 2011 09:27, Kostya Serebryany <kcc at google.com> wrote: > Question to the LLVM developers: would you consider adding > the AddressSanitizer code to the LLVM trunk? Do you have an idea how hard would it be to port to non-x86 platforms? I saw some Intel ASM in the C++ file... The run-time library being 1.5k loc is not encouraging, but it didn't look particularly

On Thu, Jun 16, 2011 at 11:10 PM, Renato Golin <rengolin at systemcall.org>wrote: > On 16 June 2011 09:27, Kostya Serebryany <kcc at google.com> wrote: > > Question to the LLVM developers: would you consider adding > > the AddressSanitizer code to the LLVM trunk? > > Do you have an idea how hard would it be to port to non-x86 platforms? > I saw some Intel ASM

...I would prefer a "not implemented" exception rather than letting the user think we have nothing about that subject... Would it be possible to add options to the query_parser so the user can choose if she wants a tolerant parser or not? Perhaps it could be a bitfield, something like qp.report_errors(UNMATCHED_BRACKETS | UNMATCHED_QUOTES | UNKNOWN_FIELDS | ...) with the default being no error report at all to keep intact the actual behavior (although it actually reports some errors like bad operators usage : a and and b). Your thoughts? 5. Names of operators, prefix names case sensitivity...

Hello again, The tool we announced 1.5 months ago has matured quite a bit. In addition to heap out-of-bound and use-after-free bugs it also finds stack overruns/underruns. AddressSanitizer is being actively used by the Chromium developers and already found over 20 bugs: http://blog.chromium.org/2011/06/testing-chromium-addresssanitizer-fast.html Question to the LLVM developers: would you

Hi, I''ve got a problem on which I''ve spent many hours, and I can''t get a clue on what is happening... I hope someone here will be able to help me. Here is the situation : my Rails app uses acts_as_commentable and acts_as_bookmarkable on a Diagram model. Everything''s working OK individually: I can create a comment on a Diagram, bookmark it, and so on. Now,

This is the next patch series for scrub userland tools. Change log v1->v2: - commands now reachable as "btrfs scrub ..." instead of "btrfs filesystem scrub ..." - ability to scrub a single device instead of a whole file system - superfluous command line options removed - resume is now a separate command ("scrub resume") instead of "scrub start -r" -

This patch refactors the data transfer code with several goals: * Have a common read(source)/write(target) loop so that common processing can happen in the middle of it, e.g. format change/progress bar * Provide volume metadata to transfers to allow smarter reading/writing, e.g. of sparse files * Simplify the data transfer code The patch *isn't* NFC because there are some minor behaviour