Closed cole-miller closed 6 months ago
This change breaks compatibility with all extant libraft releases, so as part of the same PR we need to disable the "external libraft" CI job and remove the option from the build system bits of it will need to be guarded by DQLITE_NEXT.
Marking as draft while I resolve the reports from ASan (which I wasn't seeing locally...)
Failing tests on Jammy are due to https://github.com/microsoft/linux-package-repositories/issues/130.
Attention: Patch coverage is 89.18919%
with 8 lines
in your changes are missing coverage. Please review.
Project coverage is 77.43%. Comparing base (
cb65db7
) to head (960b9e2
). Report is 5 commits behind head on master.
Files | Patch % | Lines |
---|---|---|
src/raft/uv_encoding.c | 81.48% | 2 Missing and 3 partials :warning: |
src/raft/uv_segment.c | 84.21% | 1 Missing and 2 partials :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Marking this as draft until #642 merges and it can be retargeted to master
The local_data field stores data that is persisted locally (and stored in the in-memory log) but not send in AppendEntries messages. This will be used to store the vfs2_wal_slice when we introduce vfs2.
The is_local field is not persisted nor sent in AppendEntries. It exists only in the in-memory log and is true when the entry in question originated on the current node when it was leader, as opposed to being loaded from disk or received in AppendEntries. This will be used during vfs2 integration to determine whether to use vfs2_unhide or vfs2_commit when a COMMAND entry is applied.
Signed-off-by: Cole Miller cole.miller@canonical.com