Update nix build

release: prepare for 5.0.rc1

release: prepare for 5.0.rc0

release: prepare for 4.6.rc5

commitlog: Ensure we never have more than one new_segment call at a time

Refs scylladb#9896

Found by @eliransin. Call to new_segment was wrapped in with_timeout.
This means that if primary caller timed out, we would leave new_segment
calls running, but potentially issue new ones for next caller.

This could lead to reserve segment queue being read simultanously. And
it is not what we want.

Change to always use the shared_future wait, all callers, and clear it
only on result (exception or segment)

Closes scylladb#10001

(cherry picked from commit 445e1d3)

release: prepare for 4.6.rc2

Revert "cql3: Reject updates with NULL key values"

This reverts commit 44c784c. It
causes a regression without 6afdc60,
and it is too complicated to backport at this time.

Ref scylladb#9311.

Update Seastar module with additional backports

Backported an additional Seastar patch:

  > Merge 'metrics: Fix dtest->ulong conversion error' from Benny Halevy

Fixes scylladb#9794.

release: prepare for 4.6.rc1

cql: Fix missing data in indexed queries with base table short reads

Indexed queries are using paging over the materialized view
table. Results of the view read are then used to issue reads of the
base table. If base table reads are short reads, the page is returned
to the user and paging state is adjusted accordingly so that when
paging is resumed it will query the view starting from the row
corresponding to the next row in the base which was not yet
returned. However, paging state's "remaining" count was not reset, so
if the view read was exhausted the reading will stop even though the
base table read was short.

Fix by restoring the "remaining" count when adjusting the paging state
on short read.

Tests:

  - index_with_paging_test
  - secondary_index_test

Fixes scylladb#9198
Message-Id: <[email protected]>

(cherry picked from commit 1e4da2d)