Pantograph doesn't work when a debugger is one eg vscode debugger

[brando90]

I get this error:

Exception has occurred: AssertionError
Server failed to emit ready signal: 9.14s - pydevd: Sending message related to process being replaced timed-out after 5 seconds
; Maybe the project needs to be rebuilt
  File "/lfs/skampere1/0/brando9/PyPantograph/pantograph/server.py", line 161, in restart_async
    assert ready.rstrip() == "ready.", f"Server failed to emit ready signal: {ready}; Maybe the project needs to be rebuilt"
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lfs/skampere1/0/brando9/PyPantograph/pantograph/utils.py", line 16, in wrapper
    return asyncio.run(func(*args, **kwargs))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/lfs/skampere1/0/brando9/PyPantograph/pantograph/server.py", line 78, in __init__
    self.restart()
  File "/lfs/skampere1/0/brando9/ZIP-FIT/zip_fit/lean_pass_k_unbiased.py", line 211, in main
    server = Server()
             ^^^^^^^^
  File "/lfs/skampere1/0/brando9/ZIP-FIT/zip_fit/lean_pass_k_unbiased.py", line 228, in <module>
    main()
AssertionError: Server failed to emit ready signal: 9.14s - pydevd: Sending message related to process being replaced timed-out after 5 seconds
; Maybe the project needs to be rebuilt

I think this is the reason:

Debugger or IDE Interference

Sometimes, when stepping through code with pydevd or other debuggers, the server’s stdout can be wrapped or redirected, or the Lean process gets confused. Pantograph never sees “ready.”
Try running your script outside of a step debugger (e.g., from the terminal) to see if that solves it.
...
C) Disable or Avoid Debugger Interference
If you see mention of “pydevd: Sending message related to process being replaced timed-out after 5 seconds,” it might be your Python debugger is interfering with the sub-process’s stdout.
Try running the script directly from the terminal (e.g. python my_script.py) with no breakpoints or debugger.
If that solves the problem, you know the debugger was messing with sub-process I/O.

This is essential for python dev and vscode is the standard interface for lean anyway. I recommend to support this.

[brando90]

quick fix it run the code with a direct pyton cmd eg

(zip_fit) brando9@skampere1~ $ python /lfs/skampere1/0/brando9/ZIP-FIT/zip_fit/lean_pass_k_unbiased.py

/lfs/skampere1/0/brando9/miniconda/envs/zip_fit/lib/python3.11/site-packages/transformers/utils/hub.py:128: FutureWarning: Using `TRANSFORMERS_CACHE` is deprecated and will be removed in v5 of Transformers. Use `HF_HOME` instead.
  warnings.warn(
Setting random seed = 42
Device set to use cuda:0
Truncation was not explicitly activated but `max_length` is provided a specific value, please use `truncation=True` to explicitly truncate examples to max length. Defaulting to 'longest_first' truncation strategy. If you encode pairs of sequences (GLUE-style) with the tokenizer you can select this strategy more precisely by providing a specific strategy to `truncation`.
Setting `pad_token_id` to `eos_token_id`:50256 for open-end generation.

[1/2] Problem: 'theorem lemma1 : 2 + 1 = 1 + 2 := by'
  #Generated=5, #Correct=5, pass@1=1.000
Device set to use cuda:0
Truncation was not explicitly activated but `max_length` is provided a specific value, please use `truncation=True` to explicitly truncate examples to max length. Defaulting to 'longest_first' truncation strategy. If you encode pairs of sequences (GLUE-style) with the tokenizer you can select this strategy more precisely by providing a specific strategy to `truncation`.
Setting `pad_token_id` to `eos_token_id`:50256 for open-end generation.

[2/2] Problem: 'theorem lemma2 : 2 + 2 = 2 + 2 := by'
  #Generated=5, #Correct=5, pass@1=1.000

==== Final Average Pass@1 across N=2 tasks: 1.000 ====

Runs my compilation check with gpt2

[brando90]

note, code is public: https://github.com/stair-lab/ZIP-FIT/blob/bm_dev/zip_fit/lean_pass_k_unbiased.py

[lenianiva]

This problem might be unfix-able since it originates in Python's subprocess IO system

[lenianiva]

Since we dropped pexpect, does debugging work now?

[brando90]

<!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Aptos; panose-1:2 11 0 4 2 2 2 2 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; font-size:12.0pt; font-family:"Aptos",sans-serif;} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt; mso-ligatures:none;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} -->Ah! I will check this! Thanks for letting me know. From: Leni Aniva ***@***.***>Date: Friday, May 30, 2025 at 8:29 AMTo: stanford-centaur/PyPantograph ***@***.***>Cc: Brando Miranda ***@***.***>, Author ***@***.***>Subject: Re: [stanford-centaur/PyPantograph] Pantograph doesn't work when a debugger is one eg vscode debugger (Issue #70)lenianiva left a comment (stanford-centaur/PyPantograph#70)Since we dropped pexpect, does debugging work now?—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>