25523: Adds suite of tools to provide a more unified progress experience - MINOR#692
Open
mkoistinen wants to merge 7 commits into
Open
25523: Adds suite of tools to provide a more unified progress experience - MINOR#692mkoistinen wants to merge 7 commits into
mkoistinen wants to merge 7 commits into
Conversation
mkoistinen
changed the title
jdbeel
reviewed
Jul 10, 2026
jackx111
reviewed
Jul 10, 2026
jackx111
reviewed
Jul 10, 2026
dmaze
reviewed
Jul 10, 2026
mkoistinen
force-pushed
the
25523-adds-task_id_to-relevant-methods
branch
from
July 14, 2026 03:17
c64e67b to
ed0a06f
Compare
jackx111
approved these changes
Jul 14, 2026
mkoistinen
force-pushed
the
25523-adds-task_id_to-relevant-methods
branch
from
July 14, 2026 16:03
b71ef23 to
d99157f
Compare
Mechanical, no-behavior-change refactor split out from the task_id/progress feature so that feature diff stays reviewable: - Remove `import typing as t`; convert `t.Optional[X]` -> `X | None`, `t.Any` -> `Any`, `t.Union[...]` -> `... | None`, `t.overload`/`t.Protocol`/ `t.TypeVar` -> direct imports across client/base.py, engine/trainee.py, and utilities/internals.py. - Assorted lint/style cleanup (import ordering, signature formatting, ConsoleFeedback stop-event check, trailing newline). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…ework Adds a `task_id` keyword to the long-running client/engine operations and a transparent-progress framework (howso/utilities/progress.py) that surfaces engine + batch progress via an `@auto_progress` decorator, with `AbstractHowsoClient.get_progress()` for concurrent progress polling. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mkoistinen
force-pushed
the
25523-adds-task_id_to-relevant-methods
branch
from
July 24, 2026 13:57
6b56adc to
c31c525
Compare
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
4 participants
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 PR is all about providing transparent progress reporting and a suite of facilities for instrumenting code within this repo and things downstream from it to provide and display progress:
The HSE-based progress is automatically applied to:
train,analyze,react,react_series,react_series_stationary,impute,react_group,react_into_features,react_aggregate, andreduce_datawhere the engine provides support.The progress reporting degrades gracefully in less capable environments. Part of this is provided by
rich, with aRichProgressReporterbut also by a separateSimpleProgressReporterwhich was designed for use in notebooks. This PR tries to be smart about detecting the run-time environment to decided which reported to use.For manual control over the automatic progress, we have these in the public API: