aider icon indicating copy to clipboard operation
aider copied to clipboard

Uncaught NoConsoleScreenBufferError in win32.py line 219

Open jishua9 opened this issue 1 year ago • 1 comments

Aider version: 0.55.0 Python version: 3.12.4 Platform: Windows-11-10.0.22631-SP0 Python implementation: CPython Virtual environment: No OS: Windows 11 (64bit) Git version: git version 2.45.2.windows.1

An uncaught exception occurred:

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "main.py", line 694, in main
    coder.run()
  File "base_coder.py", line 729, in run
    user_message = self.get_input()
                   ^^^^^^^^^^^^^^^^
  File "base_coder.py", line 742, in get_input
    return self.io.get_input(
           ^^^^^^^^^^^^^^^^^^
  File "io.py", line 345, in get_input
    session = PromptSession(
              ^^^^^^^^^^^^^^
  File "prompt.py", line 476, in __init__
    self.app = self._create_application(editing_mode, erase_when_done)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "prompt.py", line 727, in _create_application
    application: Application[_T] = Application(
                                   ^^^^^^^^^^^^
  File "application.py", line 267, in __init__
    self.output = output or session.output
                            ^^^^^^^^^^^^^^
  File "current.py", line 67, in output
    self._output = create_output()
                   ^^^^^^^^^^^^^^^
  File "defaults.py", line 87, in create_output
    return Win32Output(stdout, default_color_depth=color_depth_from_env)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "win32.py", line 115, in __init__
    info = self.get_win32_screen_buffer_info()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "win32.py", line 219, in get_win32_screen_buffer_info
    raise NoConsoleScreenBufferError
prompt_toolkit.output.win32.NoConsoleScreenBufferError: No Windows console found. Are you running cmd.exe?

jishua9 avatar Sep 16 '24 05:09 jishua9

Regression Detector

Regression Detector Results

Run ID: 1598bc01-e8cb-449a-8262-909c366205b1 Metrics dashboard Target profiles

Baseline: 6e8be0f4c7c62466c91d3f5ff22ed5092fea8945 Comparison: 169c096244301586ea2b70f919142a939f3cab32

Performance changes are noted in the perf column of each table:

  • ✅ = significantly better comparison variant performance
  • ❌ = significantly worse comparison variant performance
  • ➖ = no significant change in performance

No significant changes in experiment optimization goals

Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%

There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
file_tree memory utilization +1.24 [+1.11, +1.37] 1 Logs
otel_to_otel_logs ingress throughput +0.89 [+0.08, +1.70] 1 Logs
idle memory utilization +0.58 [+0.52, +0.63] 1 Logs
idle_all_features memory utilization +0.55 [+0.42, +0.67] 1 Logs
tcp_syslog_to_blackhole ingress throughput +0.23 [+0.19, +0.28] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.02 [-0.07, +0.10] 1 Logs
tcp_dd_logs_filter_exclude ingress throughput -0.00 [-0.01, +0.01] 1 Logs
pycheck_lots_of_tags % cpu utilization -1.71 [-4.22, +0.79] 1 Logs
basic_py_check % cpu utilization -1.91 [-4.65, +0.83] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -1.99 [-2.72, -1.27] 1 Logs

Bounds Checks

perf experiment bounds_check_name replicates_passed
idle memory_usage 10/10

Explanation

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

  3. Its configuration does not mark it "erratic".

pr-commenter[bot] avatar Sep 09 '24 21:09 pr-commenter[bot]

[Fast Unit Tests Report]

On pipeline 45508672 (CI Visibility). The following jobs did not run any unit tests:

Jobs:
  • tests_windows-x64

If you modified Go files and expected unit tests to run in these jobs, please double check the job logs. If you think tests should have been executed reach out to #agent-devx-help

Looks like golang.org/x/sys is up-to-date now, so this is no longer needed.

dependabot[bot] avatar Oct 04 '24 13:10 dependabot[bot]