fix: bug in raft snapshot application

Summary

• fix: bug in raft snapshot application

There was a hard-to-reproduce bug in our snapshot application code. We always compact the raft log before applying the snapshot, because the snapshot replaces the entries and some of the logic in raft-rs seems to rely on this. The problem was, that our compact_log function would not remove any unapplied entries, which makes sense for compaction triggered automatically by raft log size, but doesn't make sense for raft snapshot, as the snapshot contains the state corresponding to the newer entries. The fix is simple: don't guard from unapplied entry compaction in case the compaction is for raft snapshot.

We don't add any regression tests for this, because the implementation would be too difficult and would need us to pollute the code with error injection logic, which is not a worthy trade off in this case. But also the logic will still be tested, because this bug was responsible for a large amount of flaky tests, so we should see a significant reduction in flakiness from now on in tests concerning raft snapshots.

• test: reduce test_large_snapshot flakiness

---

• Close #1167 (closed), #779 (closed)
• Cherry-pick to: none
• Docs follow-up: not necessary

test/conftest.py

@@ -2184,15 +2184,7 @@ class PgClient:
 
 
 def build_profile() -> str:
-    from_env = os.environ.get("BUILD_PROFILE")
-
-    if "CI" in os.environ:
-        # When running in CI BUILD_PROFILE must always be specified, we rely
-        # this in a couple of tests
-        assert from_env is not None, "BUILD_PROFILE must always be set in CI"
-
-    # When running on a developers machine, priorities the usability
-    return from_env or "dev"
+    return os.environ.get("BUILD_PROFILE", "dev")
 
 
 def get_test_dir():