Skip to content

fix: log checkpoint and rolling-state load failures instead of printing - #9635

Open
VenishPaneliya wants to merge 1 commit into
OpenMined:devfrom
VenishPaneliya:log-checkpoint-load-failures
Open

VenishPaneliya wants to merge 1 commit into
OpenMined:devfrom
VenishPaneliya:log-checkpoint-load-failures

Conversation

@VenishPaneliya

Copy link
Copy Markdown

Three recovery paths in ConnectionRouter print a hand-prefixed "Warning: ..." to stdout:

  • get_latest_checkpoint (line 492)
  • get_all_incremental_checkpoints (line 535)
  • get_rolling_state (line 572)

Each catches an exception, tells the user, and continues — but via print, so the message cannot be silenced, captured or routed, and in a notebook it lands in the cell output.

The module already imports logging, defines logger = logging.getLogger(__name__), and uses logger.warning for the same kind of recoverable problem (unknown peer protocol schema, unknown peer state). These were the only three print calls in the file. The "Warning: " prefix goes away with the switch, since the level carries it.

ruff check, ruff format and black report no change against dev on this file.

Three recovery paths in ConnectionRouter print a hand-prefixed
"Warning: ..." to stdout, so a caller cannot silence, capture or route
the message. The module already imports logging, defines a module
logger and uses logger.warning for the same kind of recoverable
problem elsewhere in the file.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant