You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
text = ",".join([f"node_{i}" for i in range(100)])
logger.info(f"A very long log message - {text}")
I started with a pandas-iris starter and add this into one of the node. Copying and paste it into terminal produce this result. This
conflicts with some feature such as resume pipeline (kedro will produce a log suggestion how to recover from a fail pipeline). This is common with medium size project.
Context
Steps to Reproduce
Expected Result
Actual Result
-- If you received an error, place it here.
-- Separate them if you have more than one.
Your Environment
Kedro version used (pip show kedro or kedro -V):
Python version used (python -V):
Operating system and version:
The text was updated successfully, but these errors were encountered:
I'm not sure it's possible to keep the rich logging while solving this issue. Probably we should push for making rich optional #2928. Voting to close this issue.
Relevant code from logging.py for restarting a failed pipeline is:
self._logger.warning(
"There are %d nodes that have not run.\n"
"You can resume the pipeline run from the nearest nodes with "
"persisted inputs by adding the following "
"argument to your previous command:\n%s",
len(remaining_nodes),
postfix,
)
Can this not be altered to have a copy-pasteable form of the postfix, which contains the CLI element, printed to terminal using the out method from rich (https://rich.readthedocs.io/en/stable/console.html#low-level-output)? Either (a) as duplicate to follow the current logging call, or (b) as a replacement for removing the postfix from the current logging call?
Description
I started with a
pandas-iris
starter and add this into one of the node. Copying and paste it into terminal produce this result. Thisconflicts with some feature such as resume pipeline (kedro will produce a log suggestion how to recover from a fail pipeline). This is common with medium size project.
Context
Steps to Reproduce
Expected Result
Actual Result
Your Environment
pip show kedro
orkedro -V
):python -V
):The text was updated successfully, but these errors were encountered: