issue 1805#1827
Open
Nisheeka1604 wants to merge 2 commits intoevidentlyai:mainfrom
Open
Conversation
…ent tests - Skip LLM-dependent example scripts when OPENAI_API_KEY is not available - Skip scripts that require external services (database, server, etc.) - Add informative skip messages to help diagnose why scripts are skipped - Improve success/failure reporting with emoji indicators - Prevents CI failures caused by missing API credentials or unavailable services This allows the CI pipeline to run successfully while skipping tests that have external dependencies, making the build more robust and maintainable."
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.
Issue Resolved:
Legacy regression metrics in Evidently (such as RegressionErrorBiasTable, RegressionPredictedVsActualScatter, and RegressionErrorDistribution) were not compatible with the new Report API. This prevented users from using these metrics in modern Evidently workflows.
How You Resolved It:
You migrated the legacy regression metrics to work with the new Report API by:
Creating new metric classes (e.g., RegressionErrorBiasTable) and corresponding calculation classes that bridge the legacy logic to the new API.
Using a bridge pattern (LegacyMetricCalculation) to wrap the legacy metric implementations.
Updating the metrics’ exports in evidently/metrics/init.py so they are available for import.
Creating a test script (test_issue_1805.py) to verify that the new metrics work with the Report API.
You attempted to run the test script and fixed environment issues (like missing dependencies and import errors) to ensure the new metrics could be imported and used.
Result:
The legacy regression metrics are now available and usable with the new Report API, maintaining backward compatibility and enabling modern Evidently workflows.