To allow future upgrades of Waypipe's wire protocol, the connection
header version field is no longer strictly checked; instead, any version
increase will require an acknowledgement message. Because the first
message from the client is always simple (a protocol message containing
registry and callback requests) freezing its structure is an acceptable
constraint on future versions.

This may slightly improve performance when applying the fill operation.

The protocol requires sending file descriptors which Waypipe
cannot currently replicate.

To collect a core dump, users should Ctrl+\ for SIGQUIT instead.

Once the zwp_linux_buffer_params_v1 object is used to create a
wl_buffer, it no longer needs to hold on to the associated
shadow_fd structs.

Versions of Waypipe >= 0.8.2 always send the compression type in
ssh mode. When using <0.8.2 versions of Waypipe to connect to
versions following this commit, one should use either the -c lz4
or the -c zstd option when in ssh mode. Waypipe >= 0.8.2 will also
provide an error if the client and server use different
compression types.

Sergei Trofimovich authored Nov 03, 2023 and M. Stoeckl committed Dec 01, 2023

`gcc-14` added a new `-Walloc-size` warning that makes sure that size of
an individual element matches size of a pointed type:

    https://gcc.gnu.org/PR71219

`waypipe` triggers it on `calloc()` calls where member size is used as
`1` (instead of member count):

    test/protocol_control.c: In function 'make_filled_pattern':
    test/protocol_control.c:71:25: error: allocation of insufficient size '1'
     for type 'uint32_t' {aka 'unsigned int'} with size '4' [-Werror=alloc-size]
       71 |         uint32_t *mem = calloc(size, 1);
          |                         ^~~~~~

This commit was inspired by, although not directly based off of,
a similar patch by Jakob Ruediger.

src/util.c:742:7: error: no newline at end of file [-Werror,-Wnewline-eof]
  742 | #endif
      |       ^

Note: the version with updated shm formats has not yet been
released, but as updates to the wl_shm format list just pull
values from libdrm, it is very unlikely that libwayland will
conflict.

This was introduced by a0f6bfa1
incorrectly checking when to increase the value of
cxs->last_confirmed_msgno. As a result, one of the two Waypipe
processes would leak all the messages sent to the other process.