Repository navigation
Reject ambiguous PIT facts and separate announcement and report windows - #44
Merged
Merged
Conversation
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.
Same-key, same-availability conflicting facts previously depended on input order. Reject conflicts and deduplicate identical selected facts. Earnings forecasts now query report quarters independently of the requested announcement window and filter announcements inclusively, including early-year prior/future report periods. Explicit report_periods covers older revisions. The weekday effective-date approximation is documented and is not full PIT certification.
Validation: Windows Python 3.12.14, isolated environment installed from this repository's committed requirements.lock, pip check, repository Ruff check/format and complete test suite: 1026 passed, 8 skipped in 222.02s (0:03:42). Relevant repository coverage gates passed.
Hosted CI is tracked separately from these local results. No workflow, billing setting, protection rule or dependency pin was changed.