Skip to content
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

connecting issue #5142

Closed
LCGaoZzz opened this issue Feb 28, 2025 · 1 comment
Closed

connecting issue #5142

LCGaoZzz opened this issue Feb 28, 2025 · 1 comment
Labels

Comments

@LCGaoZzz
Copy link

Description

I am using the R session runtime in Colab, and after running some code for a while, the runtime starts showing "connecting". I can still access the files on the runtime, but I am unable to continue running the code because it always stays in the "connecting" state.

I frequently encounter this issue when using the R session runtime, but I have never experienced it while using Python.

Even after attempting to reconnect, I am still unable to continue running the code.

Steps to Reproduce

  1. Open a Colab notebook with an R session runtime.
  2. Run some code for a while.
  3. Observe that the session starts showing "connecting".
  4. Attempt to reconnect or run additional code, but it remains stuck in the "connecting" state.

Additional Information

  • The issue only occurs with the R session runtime, not Python.
  • The file system is still accessible, but no code execution happens after the "connecting" state starts.
  • I have tried reconnecting multiple times without success.

Environment

  • Colab R session runtime
  • Version: [v2-8 TPU]
@LCGaoZzz LCGaoZzz added the bug label Feb 28, 2025
@spencersgoogle
Copy link

Please submit feedback in product within Colab at Help > Send feedback and include this Github issue ID to help us troubleshoot further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants