-
Notifications
You must be signed in to change notification settings - Fork 0
Stability & Testing Refinement #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
28 commits
Select commit
Hold shift + click to select a range
9860aea
fix(storage): ensure BufferPoolManager flushes all dirty pages on des…
poyrazK 3e8ac2a
fix(storage): resolve 1024-row bug by simplifying page space validati…
poyrazK 62cd6a2
test(e2e): enhance Python client robustness and fix binary name in or…
poyrazK 8255d84
docs: add Stability & Testing Refinement to the roadmap
poyrazK b3cc142
chore: cleanup reproduction test and revert build changes
poyrazK 5ef2128
chore: ignore heap files and remove them from index
poyrazK 349af8e
style: automated clang-format fixes
poyrazK d69635c
fix(storage): harden BufferPoolManager destructor with exception safety
poyrazK f409e85
chore(storage): remove debug logging and dead code from HeapTable
poyrazK 5bfe0ae
test(e2e): improve client reliability and ensure background process c…
poyrazK c6b8eb2
docs: formalize Phase 9 roadmap and reorganize gitignore categories
poyrazK b474388
style: automated clang-format fixes
poyrazK 4f35ce6
feat(parser,executor): implement HAVING clause and expand test coverage
poyrazK 355e4ea
style: automated clang-format fixes
poyrazK 878d551
test: expand operator and parser coverage with advanced test cases
poyrazK bd6f8df
style: automated clang-format fixes
poyrazK 88872b4
test: refine MVCC visibility and expand vectorized operator tests
poyrazK 821ffa6
style: automated clang-format fixes
poyrazK e2388b2
test: major coverage boost for network, recovery, and executor compon…
poyrazK 2991320
style: automated clang-format fixes
poyrazK a1f186a
test: achieve significant coverage boost for network and recovery
poyrazK 51b82e4
style: automated clang-format fixes
poyrazK a5b64a8
test: reach for 70% coverage with exhaustive parser and network edge …
poyrazK 17447c9
parser: implement CreateIndexStatement AST and parse_create_index
poyrazK 5f5eb18
tests: harden cloudSQL execution and visibility tests
poyrazK b09bdce
tests: resolve raft simulation and networking race conditions
poyrazK a77dc20
tests: enhance recovery log validation and server handshake reliability
poyrazK 5cd90ae
style: automated clang-format fixes
poyrazK File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 42
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 131
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 993
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 1239
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 5020
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 1513
🏁 Script executed:
Repository: poyrazK/cloudSQL
Length of output: 174
Callers cannot detect I/O failures—both EOF and actual read errors result in zero-filled pages returned as success.
StorageManager::read_pagecorrectly distinguishes EOF (returnstruewith zero-fill) from I/O errors (returnsfalse). However,BufferPoolManager::fetch_pagemasks this distinction by:read_pagefailurePage*pointer (nevernullptr)Since
HeapTable::read_pageandBTreeIndex::read_pageonly check fornullptr, they cannot differentiate successful reads from I/O failures. A disk read error becomes indistinguishable from a legitimate EOF case—both appear as success with zero-filled data to callers.This is appropriate for new pages beyond file EOF, but actual I/O errors (disk failures, corruption) are silently masked, potentially causing silent data corruption.
The storage layer should propagate read failures so callers can handle them appropriately, or the buffer pool should use an out-parameter or status code to signal failures separately from the page pointer.
🤖 Prompt for AI Agents