Ivan Dagelic
Ivan Dagelic
**Describe the bug** The Daytona API should return correct HTTP status codes depending on what caused the issue. Right now it defaults to 500 for most of the calls. This...
**Describe the bug** When `daytona create`-ing a repository for which a project config hasn't yet been defined, there is an error in the server logs implying that something went wrong...
**Describe the bug** **To Reproduce** Steps to reproduce the behavior: 1. Run `daytona serve` 2. Run `daytona create` and input a regular non-devcontainer repo 4. Enter advanced config, select Devcontainer...
**Is your feature request related to a problem? Please describe.** Daytona uses the "~/.config" folder (on Linux based systems) for storing all important data, starting from config files but all...
**Is your feature request related to a problem? Please describe.** When a user runs `daytona create` with a registered Git provider and selects it - when choosing a namespace there...
**Describe the bug** Running `daytona create https://github.com/metcalfc/simple-astro` displays the daytona info command containing the "(9 uncommited changes) warning. Checking the git status inside the container shows no changes. **To Reproduce**...
**Is your feature request related to a problem? Please describe.** Daytona's commands use many different aliases for some command verbs - for example `daytona target set` has aliases `"s", "add",...
**Is your feature request related to a problem? Please describe.** We should document / alert the user about the requirements to have JetBrains IDEs work properly with Daytona. This is...
# Build logs UX ## Description Adds a polling function to stop reading logs once the build is published or has errored Adds `--continue-on-completed` flag to continue reading logs and...
**Is your feature request related to a problem? Please describe.** As mentioned in #859 people might try to intuitively use daytona code for creating or expect it to default to...