PyPy 3.11: rich.errors.LiveError: Only one live display may be active at once

[notxvilka]

This issue was met by me while using simple progress bar from a script runnning under PyPy 3.11. It worked just fine using CPython 3.10-3.13, but somehow triggers this error from the PyPy.

Also, it happened to other projects, after quick search, but it doesn't look directly related to using PyPy:

• rich.errors.LiveError: Only one live display may be active at once semgrep/semgrep#10562
• [Bug]: Rich LiveError - Only one live display may be active at once DLR-RM/stable-baselines3#1645
• rich.errors.LiveError: Only one live display may be active at once freqtrade/freqtrade#8959

/home/user/.local/lib/pypy3.11/site-packages/some.py:212: in init_analysis
    self.progress.start()
/home/user/.local/lib/pypy3.11/site-packages/rich/progress.py:1173: in start
    self.live.start(refresh=True)
/home/user/.local/lib/pypy3.11/site-packages/rich/live.py:113: in start
    self.console.set_live(self)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
self = <console width=80 None>
live = <rich.live.Live object at 0x000000000c71a1e0>
    def set_live(self, live: "Live") -> None:
        """Set Live instance. Used by Live context manager.
    
        Args:
            live (Live): Live instance using this Console.
    
        Raises:
            errors.LiveError: If this Console has a Live context currently active.
        """
        with self._lock:
            if self._live is not None:
>               raise errors.LiveError("Only one live display may be active at once")
E               rich.errors.LiveError: Only one live display may be active at once
/home/user/.local/lib/pypy3.11/site-packages/rich/console.py:835: LiveError

[github-actions]

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

[willmcgugan]

Do you have more than one progress bar / Live instance active?

[notxvilka]

Do you have more than one progress bar / Live instance active?

It runs from the CI, so it has at least two instances. While I can remove it as a workaround from my program, would be nice for rich to handle this situation gracefully. Also, for some reason it's triggered only on the PyPy environment but if the same program on the same CI runs from CPython environment - there is no error.

[willmcgugan]

It runs from the CI, so it has at least two instances. While I can remove it as a workaround from my program, would be nice for rich to handle this situation gracefully. Also, for some reason it's triggered only on the PyPy environment but if the same program on the same CI runs from CPython environment - there is no error.

This isn't related to processes, so CI should be irrelevant here. The error detects that your app is running two live instances, either from threads or you've created them recursively in the same thread.

to handle this situation gracefully.

What would you want to happen if you have two Lives running simultaneously?

[notxvilka]

It runs from the CI, so it has at least two instances. While I can remove it as a workaround from my program, would be nice for rich to handle this situation gracefully. Also, for some reason it's triggered only on the PyPy environment but if the same program on the same CI runs from CPython environment - there is no error.

This isn't related to processes, so CI should be irrelevant here. The error detects that your app is running two live instances, either from threads or you've created them recursively in the same thread.

to handle this situation gracefully.

What would you want to happen if you have two Lives running simultaneously?

Hmm, good question...
Maybe wait for the lock to be freed?

What I wonder, why it does happen only on PyPy but not in CPython. I didn't change the code, and it runs in exactly the same environment.

[willmcgugan]

Maybe wait for the lock to be freed?

Might work sometimes, but is more likely to introduce a deadlock.

What I wonder, why it does happen only on PyPy but not in CPython. I didn't change the code, and it runs in exactly the same environment.

Couldn't say, but there are differences between PyPy and CPython. I would investigate how / why your code has different behavior on the different runtimes.

[willmcgugan]

Closing for now, because I suspect an edge case in PyPy and your code. Feel free to re-open if you can narrow it down to Rich.

[github-actions]

I hope I helped!

Consider sponsoring my work on Rich. I give tech support for free, in addition to maintaining Rich and Textual.

If you like using Rich, you might also enjoy Textual.

Will McGugan