op public repos

Commits

Commit:: 6426034367784b59e8ad9c12f37e97eecd284cfa
From:: cage <cage@invalid>
Date:: Mon May 23 18:11:11 2022 UTC

- [regress] added test to write a file using a big buffer (msize).

diff | patch | tree

Commit:: ec5d75ef0eb4b9bfe701449ba0d58b281229f7c9
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:32:01 2022 UTC

simplify check in handle_message

diff | patch | tree

Commit:: f9d8661b68f61636701e3320cafaf5853db70123
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:30:14 2022 UTC

report the correct write length

diff | patch | tree

Commit:: c234caae8bdf0b2be5ee26fee87f0fcbf0d95488
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:29:57 2022 UTC

limit IMSG_BUF_CONT size by the maximum allowed by imsg

diff | patch | tree

Commit:: 02d5b425514494dff976f6ddedb6bf5514213cc1
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:24:50 2022 UTC

do optimal (i.e. maximum) reads and writes

diff | patch | tree

Commit:: 1610d4872387cb3e06ec718fc70ddab17fa23bc8
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:23:45 2022 UTC

cmd_ls: fix read size don't use a constant: msize may be lower than that. Instead, use `msize - 4' which is guaranteed to be the maximum transferreable size. (it's not possible for msize to be lower than 4 since we reject ridiculously small msizes, so that difference can't underflow.)

diff | patch | tree

Commit:: 315eafe8807c0b6bf7a0a3d2ae072cbb6fa6392a
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 13:20:37 2022 UTC

reject ridiculously small msizes

diff | patch | tree

Commit:: 72d6dda035661e415f012a516efcfdc26e108c51
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 11:00:48 2022 UTC

fflush stdout in hexdump

diff | patch | tree

Commit:: 66926cfc3a240fee6da318457f40e62cc246fdc9
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 10:57:40 2022 UTC

allow jumbo reads

diff | patch | tree

Commit:: 23fbe390bd2006b2da54d7ed1fdd5e9615e58d4b
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 10:56:01 2022 UTC

allow Tread to fill a message a message of `msize' len is valid, we just need to make sure to _not_ overflow it.

diff | patch | tree

Commit:: a9eb1af3d081c65f002dfa7e3cde71e3cc23e963
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 10:55:06 2022 UTC

allow jumbo Twrites for real

diff | patch | tree

Commit:: bc8e3a24b7f12ac92c95e9f098986e15c7198918
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 09:44:11 2022 UTC

typo

diff | patch | tree

Commit:: aced1a379c025362ec03b54b013ea950603ebc92
From:: Omar Polo <op@omarpolo.com>
Date:: Mon May 23 09:44:06 2022 UTC

sync changelog

diff | patch | tree

Commit:: fbeaf87b54479383a77dc1fc41318bb788267154
From:: Omar Polo <op@omarpolo.com>
Date:: Sun May 22 18:55:41 2022 UTC

fail on "jumbo" requests (except for Twrite) except for Twrite, all other requests are passed via a single imsg. We don't handle "jumbo" request for anything outside Twrite, nor it does make sense actually, so let's drop it. (well, for Twstat an argument can be made, maybe)

diff | patch | tree

Commit:: 182b48dc821a0a4cf7bbcfcdf5f9d376136fd7e6
From:: Omar Polo <op@omarpolo.com>
Date:: Sun May 22 18:55:41 2022 UTC

proper err handling for parse_message

diff | patch | tree

More ↓