-
Notifications
You must be signed in to change notification settings - Fork 0
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
base: ponder-on-modin-0-19-0
Are you sure you want to change the base?
Conversation
Signed-off-by: Devin Petersohn <[email protected]>
@@ -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__}" |
There was a problem hiding this comment.
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__}" |
There was a problem hiding this comment.
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.
There was a problem hiding this 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.
What do these changes do?
flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
git commit -s
docs/development/architecture.rst
is up-to-date