Skip to content
Limestone-CI

feat(wal_sync): implement WAL history management with append and reco… #1443

Sign in to view logs

feat(wal_sync): implement WAL history management with append and reco…

feat(wal_sync): implement WAL history management with append and reco… #1443

Triggered via push August 12, 2025 13:07
@umeganeumegane
pushed e7685f4
wip/wal_sync
Status Failure
Total duration 1m 37s
Artifacts –

ci-build.yml

on: push
Test
53s
Test
Analysis
1m 34s
Analysis
Fit to window
Zoom out
Zoom in

Annotations

1 error and 20 warnings
Analysis
readability-redundant-declaration: src/limestone/wal_sync/wal_history.cpp#L41
redundant 'record_size' declaration
cppcoreguidelines-avoid-c-arrays,hicpp-avoid-c-arrays,modernize-avoid-c-arrays: src/limestone/wal_sync/wal_history.cpp#L44
do not declare C-style arrays, use std::array<> instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L46
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L47
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-pointer-arithmetic: src/limestone/wal_sync/wal_history.cpp#L47
do not use pointer arithmetic
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L47
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L49
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-pointer-arithmetic: src/limestone/wal_sync/wal_history.cpp#L49
do not use pointer arithmetic
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L50
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L62
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-pointer-arithmetic: src/limestone/wal_sync/wal_history.cpp#L62
do not use pointer arithmetic
cppcoreguidelines-pro-bounds-pointer-arithmetic: src/limestone/wal_sync/wal_history.cpp#L64
do not use pointer arithmetic
llvm-else-after-return,readability-else-after-return: src/limestone/wal_sync/wal_history.cpp#L76
do not use 'else' after 'return'
cppcoreguidelines-avoid-c-arrays,hicpp-avoid-c-arrays,modernize-avoid-c-arrays: src/limestone/wal_sync/wal_history.cpp#L88
do not declare C-style arrays, use std::array<> instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L90
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
cppcoreguidelines-pro-bounds-array-to-pointer-decay: src/limestone/wal_sync/wal_history.cpp#L98
do not implicitly decay an array into a pointer; consider using gsl::array_view or an explicit cast instead
modernize-pass-by-value: src/limestone/wal_sync/wal_history.cpp#L108
pass by value and use std::move
hicpp-use-auto,modernize-use-auto: src/limestone/wal_sync/wal_history.cpp#L118
use auto when initializing with a cast to avoid duplicating the type name
modernize-use-nodiscard: src/limestone/wal_sync/wal_history.h#L42
function 'list' should be marked [[nodiscard]]
modernize-use-nodiscard: src/limestone/wal_sync/wal_history.h#L54
function 'read_all_records' should be marked [[nodiscard]]