Creation process exists if a log read error occurs.
Describe the bug If the websocket connection breaks while reading workspace/project logs in the creation process, the process exists. This is not ideal since the process actually continues on the server but the user is not aware of it.
To Reproduce Steps to reproduce the behavior:
-
daytona create(while connected to a remote server) - Wait a bit
- Break your internet connection
To connect to a remote server you can do the following:
-
daytona api-key new - Paste the copied command from the output into your terminal
- This will remotely connect you to your local server
Expected behavior The logs should have a retry mechanism in order for the logs to continue even if the websocket connection breaks.
Desktop (please complete the following information):
- OS: any
- Daytona Version: v0.25.2
Additional context Related to #808
- To successfully implement this, we should consider adding an option to read logs from a certain point. This would allow the client to continue where they left of.
@quest-bot stash 50
New Quest!
A new Quest has been launched in @daytonaio’s repo. Merge a PR that solves this issue to loot the Quest and earn your reward.
Loot of 50 USD has been stashed in this issue to reward the solver!
🗡 Comment @quest-bot embark to check-in for this Quest and start solving the issue. Other solvers will be notified!
⚔️ When you submit a PR, comment @quest-bot loot #953 to link your PR to this Quest.
Questions? Check out the docs.
👉 If no one is assigned to the issue, you are welcome to embark on the quest and tackle it without confirmation from us. In the event that multiple PRs are made from different people, we will generally accept those with the cleanest code.
@quest-bot embark
@naineel1209 has embarked on their Quest. 🗡
- @naineel1209 has been on GitHub since 2022.
- They have merged 27 public PRs in that time.
- Their swords are blessed with
DockerfileandShellmagic ✨ - They haven't contributed to this repo before.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
@quest-bot embark
@ARYPROGRAMMER has embarked on their Quest. 🗡
- @ARYPROGRAMMER has been on GitHub since 2020.
- They have merged 32 public PRs in that time.
- Their swords are blessed with
KotlinandJavaScriptmagic ✨ - They haven't contributed to this repo before.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
@quest-bot embark
@naaa760 has embarked on their Quest. 🗡
- @naaa760 has been on GitHub since 2024.
- They have merged 4 public PRs in that time.
- Their swords are blessed with
JavaScriptandTypeScriptmagic ✨ - They haven't contributed to this repo before.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
@quest-bot embark
@Ximax80 has embarked on their Quest. 🗡
- @Ximax80 has been on GitHub since 2024.
- They have merged 0 public PRs in that time.
- Their swords are blessed with
GoandShellmagic ✨ - They have contributed to this repo before.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
🧚 @Ximax80 has submitted PR https://github.com/daytonaio/daytona/issues/1387 and is claiming the loot.
Keep up the pace, or you'll be left in the shadows.
cc @naaa760 @naineel1209 @ARYPROGRAMMER
Questions? Check out the docs.
Thank you for bringing up this important issue. The retry mechanism for reading logs after a websocket disconnection is crucial for user experience and transparency during long-running operations.
Here are a few additional considerations:
Implementing a log checkpoint system to allow the client to resume reading logs from the last successful point. Including an error notification system on the client side to inform users of connection issues, along with a reconnection attempt status. Adding a persistent log storage mechanism that ensures all logs are accessible even if the client connection is interrupted. Looking forward to seeing how this is resolved! Happy to assist in testing if needed.
@quest-bot embark
@AnkitAnandMastery17 has embarked on their Quest. 🗡
- @AnkitAnandMastery17 has been on GitHub since 2022.
- They have merged 15 public PRs in that time.
- Their swords are blessed with
HTMLandCSSmagic ✨ - They haven't contributed to this repo before.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
🧚 @ARYPROGRAMMER has submitted PR https://github.com/daytonaio/daytona/issues/1485 and is claiming the loot.
Keep up the pace, or you'll be left in the shadows.
cc @AnkitAnandMastery17 @naaa760 @naineel1209 @Ximax80
Questions? Check out the docs.
@quest-bot embark
@rajanarahul93 has embarked on their Quest. 🗡
- @rajanarahul93 has been on GitHub since 2023.
- They have merged 69 public PRs in that time.
- Their swords are blessed with
JavaScriptandCSSmagic ✨ - They haven't contributed to this repo before.
- They are currently embarked on 1 quests for @daytonaio, with a maximum of 3 allowed.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
@quest-bot embark
@Mayank77maruti has embarked on their Quest. 🗡
- @Mayank77maruti has been on GitHub since 2023.
- They have merged 76 public PRs in that time.
- Their swords are blessed with
JavaScriptandShellmagic ✨ - They haven't contributed to this repo before.
- They are currently embarked on 2 quests for @daytonaio, with a maximum of 3 allowed.
This is not an assignment to the issue. Please check the repo’s contribution guidelines before submitting a PR.
Questions? Check out the docs.
Daytona is now an AI sandbox platform delivering lightning-fast, secure infrastructure for running and testing AI-generated code https://www.daytona.io/
Closing this issue as it relates to the legacy development environment management product.
Swords down 🗡
❌ Issue #953 and it's Quest have been closed by @daytonaio
Head over to https://quine.sh/quests/solver to find other active Quests ⚔️
Questions? Check out the docs