Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve the logging of errors and use JSON #39

Open
wants to merge 1 commit into
base: ponder-on-modin-0-19-0
Choose a base branch
from

Conversation

devin-petersohn
Copy link

What do these changes do?

  • first commit message and PR title follow format outlined here

    NOTE: If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

  • passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
  • passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
  • signed commit with git commit -s
  • Resolves #?
  • tests added and passing
  • module layout described at docs/development/architecture.rst is up-to-date

@@ -105,8 +105,8 @@ def decorator(obj: Any) -> Any:

assert isinstance(modin_layer, str), "modin_layer is somehow not a string!"

start_line = f"START::{modin_layer.upper()}::{name or obj.__name__}"
stop_line = f"STOP::{modin_layer.upper()}::{name or obj.__name__}"
start_line = f"STAGE: START, METHOD: {name or obj.__name__}"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why drop the layer for pushdown? I thought it was useful, especially to distinguish methods in different layers that have the same name, e.g. query compiler apply vs dataframe apply vs base apply.

Also, is it ok to drop the modin_layer in open source?

@@ -105,8 +105,8 @@ def decorator(obj: Any) -> Any:

assert isinstance(modin_layer, str), "modin_layer is somehow not a string!"

start_line = f"START::{modin_layer.upper()}::{name or obj.__name__}"
stop_line = f"STOP::{modin_layer.upper()}::{name or obj.__name__}"
start_line = f"STAGE: START, METHOD: {name or obj.__name__}"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good for now but I would if we collapse START/STOP we should try to include duration.

Copy link

@jkew jkew left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mainly I'm in favor of incremental improvements to this over time as we begin to ask more concrete questions... so while I think I might try to include a few other things this looks good for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants