search for: _signed_

Hi all, Perhaps a stupid question, but I just need pieces of audio from a file. I know I have to use vorbisfile, and the example compiles, but I don't know how to read the buffer. In fact, it's not even documented (or I'm looking at the wrong place). I assumed it was a interleaved buffer containing unsigned shorts, but that didn't work. I also tried the normal decode example,

Hi, Ok. I'm stumped, so I'm finally going to ask for help. I'm testing a brand new setup of Samba4 as an AD DC with Bind9 for DNS. The problem I'm having is when I create a new A record using the Windows DNS tools. I tick the box to create a corresponding PTR record, but it never does. I've created the reverse zone. I've tried using the Windows DNS tools to create

...osure below was publically accessible on [date] : ______ and 2) mailing back this ENTIRE message (possibly quoted in any way), _GPG/PGP-SIGNED_, to this address: priorart@opensourcepartners.nl Note that you do not have to actually read the rest of this message, mailing back a _signed_ copy is enough. We will NOT publish anything we receive, only store it in a safe place to use it in the courts should the need arise. Thanks in advance for your help, Anne Bezemer ----------------------------------------------------------------------------- DISCLOSURE: METHOD FOR PIECEW...

...osure below was publically accessible on [date] : ______ and 2) mailing back this ENTIRE message (possibly quoted in any way), _GPG/PGP-SIGNED_, to this address: priorart@opensourcepartners.nl Note that you do not have to actually read the rest of this message, mailing back a _signed_ copy is enough. We will NOT publish anything we receive, only store it in a safe place to use it in the courts should the need arise. Thanks in advance for your help, Anne Bezemer ----------------------------------------------------------------------------- DISCLOSURE: METHOD FOR PIECEW...

...> + bool coalesce_below, coalesce_above; > + struct extent new_extent; > + > + /* This might be considered an error, but be flexible for badly > + * written plugins. > + */ > + if (length == 0) > + return 0; > + > + /* Don't allow extents to exceeed the _signed_ 64 bit limit that is exceed > + * used in the rest of nbdkit. > + */ > + if (offset > INT64_MAX || > + offset + length < offset || > + offset + length > INT64_MAX) { > + nbdkit_error ("nbdkit_extent_add: " > + "extent...

...64_t length, uint32_t type) +{ + ssize_t lo, hi; + bool coalesce_below, coalesce_above; + struct extent new_extent; + + /* This might be considered an error, but be flexible for badly + * written plugins. + */ + if (length == 0) + return 0; + + /* Don't allow extents to exceeed the _signed_ 64 bit limit that is + * used in the rest of nbdkit. + */ + if (offset > INT64_MAX || + offset + length < offset || + offset + length > INT64_MAX) { + nbdkit_error ("nbdkit_extent_add: " + "extent cannot exceed signed 64 bit limit: " +...

I want to post this but mainly for discussion and early review. It's not safe for these patches to all go upstream yet (because not all filters have been checked/adjusted), but if any patches were to go upstream then probably 1 & 2 only are safe. File, VDDK, memory and data plugins all work, although I have only done minimal testing on them. The current tests, such as they are, all