Add optional progress logging for DSL query execution steps #964
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.
Adds
progress=Trueparameter to DSL query execution for debugging and monitoring query execution flow.Changes
Executor (
py3plex/dsl/executor.py)progressparameter toexecute_ast(),_execute_select(), and_execute_windowed_query()Builder API (
py3plex/dsl/builder.py)progressparameter toQueryBuilder.execute()methodTests (
tests/test_dsl_progress_logging.py)Example (
examples/network_analysis/example_dsl_progress_logging.py)Documentation (
py3plex/dsl/__init__.py)Usage
Progress messages use Python's standard logging at INFO level. Sub-query progress is suppressed in windowed queries to reduce clutter.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.