Conversation
The gems list was truncating the last 2 gems (#61-#62) because: 1. Offset calculation used hardcoded FixedChrome=3 assuming statusbar=1 line 2. But statusbar can grow to 2-3 lines during health/update checks 3. This mismatch caused gems to be unreachable by scrolling 4. Overflow trimming was too aggressive, cutting gem rows Fix: - Use dynamic statusBarTotalHeight() in offset/cursor calculations - Improve overflow trimming to only trim >1 line excess - Keep 1 extra line to preserve access to last gems Now all 62 first-level gems are accessible and displayable. Fixes #32 Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
The TestAnalyze_ListopiaGemfile test uses a hardcoded path that only exists on the developer's machine. Skip the test gracefully in CI/other environments instead of failing. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Configure CodeQL with CODEQL_ACTION_FILE_COVERAGE_ON_PRS=true to keep computing file coverage information on pull requests, avoiding the deprecation warning from GitHub. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Default CodeQL setup is already enabled on GitHub. Remove custom workflow to avoid conflict. The deprecation warning about file coverage on PRs can be addressed in GitHub repository settings if needed. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Configure CodeQL with FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to upgrade from deprecated Node.js 20 to Node.js 24 actions. Also enable CODEQL_ACTION_FILE_COVERAGE_ON_PRS to maintain file coverage information on pull requests. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Default CodeQL setup is already enabled on GitHub, which conflicts with custom advanced setup. The default setup will be automatically updated by GitHub to use Node.js 24. To control CodeQL configuration (including file coverage), disable the default setup in GitHub repository settings and re-enable this workflow. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The gems list was truncating the last 2 gems (#61-#62) because:
Fix:
Now all 62 first-level gems are accessible and displayable.
Fixes #32