Enhance query performance analysis and dashboard styles#68
Merged
Conversation
- Introduced Welford's online algorithm for variance calculation in QueryAnalyzer. - Added schema versioning to QueryBaseline for backward compatibility. - Implemented outlier detection in QueryPerformanceService to improve statistical accuracy. - Enhanced degradation alert mechanism based on execution time variance. - Updated SSHService to allow custom client factory for stream creation. - Added integration tests for message handling in NotebookRendererFlow. - Improved ConnectionManager to fallback to .pgpass for passwords and surface SSH failures. - Expanded DatabaseTreeProvider tests to cover additional database elements. - Created unit tests for MessageHandlerRegistry and SSHService. - Added SessionRegistry tests for notebook session management and URI generation. - Enhanced SQL template tests to cover new SQL builders for aggregates, domains, partitions, sequences, and triggers. - Updated TransactionManager tests to cover transaction state management and error handling. - Modified chat scripts to update environment banner based on context messages.
…sights - Added styles for delta badges to indicate performance changes. - Introduced signal chips for warnings and critical alerts. - Created a performance insights layout with cards for better data presentation. - Updated top SQL item styles for improved readability. - Enhanced table row focus and added styles for locks chain summary. - Introduced new button and control styles for better user interaction. - Added responsive design adjustments for smaller screens.
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
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.
This pull request marks the v1.0.0 production-stable release of PgStudio, introducing major improvements in stability, security, documentation, and test coverage. It addresses all critical TypeScript compilation errors, completes a comprehensive security audit, expands user and developer documentation, and updates test and coverage tooling for production readiness. The release also documents known limitations and establishes API stability guarantees for the 1.x series.
Release and Documentation Updates:
README.mdandMARKETPLACE.mdwith a feature matrix, known limitations, and new links to release materials. [1] [2] [3] [4] [5]Security and Stability Improvements:
ServerLogPanel.ts, disposal state tracking inActivityMonitorPanel.ts, and type safety for data generation strategies inMockDataPanel.ts. Details and verification are documented inFIXES_APPLIED.md.Test Coverage and Quality Gates:
.nycrc,.c8rc.phase-handlers.json,.c8rc.phase-utils.json). [1] [2] [3]CI/CD and Workflow Updates:
workflow_dispatch(manual), removing automatic triggers on push, PR, and schedule forcodeql.yml,fortify.yml,publish-nightly.yml, andtest.yml. [1] [2] [3] [4]Tooling and Formatting:
.prettierignoreand.prettierrc.jsonfor consistent code formatting and to ignore build artifacts and coverage outputs. [1] [2]