Displaying 3 results from an estimated 3 matches for "l133".
Did you mean:
133
2023 Aug 31
1
[nbdkit PATCH] sh: Allow pwrite to not consume all data
...b.com/nbdkit/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/full/full.c#L128
https://gitlab.com/nbdkit/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/null/null.c#L125
https://gitlab.com/nbdkit/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/ones/ones.c#L133
> I agree consistency between sh and other plugins is good, but the
> "baseline" seems unfathomable to me. I probably don't understand it.
sh plugin is often used for testing where the data written doesn't
matter but we're interested in other metadata like what write c...
2023 Aug 31
1
[nbdkit PATCH] sh: Allow pwrite to not consume all data
...it/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/full/full.c#L128
> https://gitlab.com/nbdkit/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/null/null.c#L125
> https://gitlab.com/nbdkit/nbdkit/-/blob/c662932f2bc71b5879b6eb83c93478191e6efef2/plugins/ones/ones.c#L133
>
> > I agree consistency between sh and other plugins is good, but the
> > "baseline" seems unfathomable to me. I probably don't understand it.
>
> sh plugin is often used for testing where the data written doesn't
> matter but we're interested in ot...
2023 Aug 31
1
[nbdkit PATCH] sh: Allow pwrite to not consume all data
On 8/31/23 10:55, Richard W.M. Jones wrote:
> On Thu, Aug 31, 2023 at 10:40:53AM +0200, Laszlo Ersek wrote:
>> On 8/31/23 00:21, Eric Blake wrote:
>>> I hit another transient failure in libnbd CI when a poorly-written
>>> eval script did not consume all of stdin during .pwrite. As behaving
>>> as a data sink can be a somewhat reasonable feature of a