-
Notifications
You must be signed in to change notification settings - Fork 185
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: dstackai/dstack
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 0.19.17
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: dstackai/dstack
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 0.19.18
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 103 files changed
- 6 contributors
Commits on Jul 2, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 7d999e1 - Browse repository at this point
Copy the full SHA 7d999e1View commit details
Commits on Jul 3, 2025
-
Ignore SSH keys when calculating fleet conf diff (#2869)
Since `/api/project/{project_name}/fleets/get_plan` returns the plan with sensitive info (SSH keys) removed, the configurations are never equal. To work around this issue, we exclude (strictly speaking, not exclude but reset to the default values, `None` in this case) fields containing SSH key content when calculating the fleet configurations diff. Fixes: #2222
Configuration menu - View commit details
-
Copy full SHA for a6dbb3f - Browse repository at this point
Copy the full SHA a6dbb3fView commit details -
* [Docs] Refactoring - [x] Replaced `Blog` in the top menu with `Benchmarks` and `Case studies` - [x] Refactored blog categories - [x] Minor edits
Configuration menu - View commit details
-
Copy full SHA for 66d8a52 - Browse repository at this point
Copy the full SHA 66d8a52View commit details -
Configuration menu - View commit details
-
Copy full SHA for 17a8e22 - Browse repository at this point
Copy the full SHA 17a8e22View commit details
Commits on Jul 4, 2025
-
Support processing more resources per replica (#2871)
* Process fleets in batches * Increase offers_cache * Cache redundant AWS API calls * Set MIN_PROCESSING_INTERVAL * Prevent concurrent quotas requests * Increase MIN_PROCESSING_INTERVAL * Make runs stopping async * Introduce SERVER_BACKGROUND_PROCESSING_RATE * Use dummy locking on Postgres * Process submitted jobs in one steps if no instance lock * Fix missing cache lock * Configure custom executor * Fix typo * Increase process_submitted_jobs max_instances * Implement offers cache warm up trick * Replace DSTACK_SERVER_BACKGROUND_PROCESSING_RATE with DSTACK_SERVER_BACKGROUND_PROCESSING_FACTOR * Document DSTACK_SERVER_BACKGROUND_PROCESSING_FACTOR * Do not create clusters from burstable AWS instances Fixes #2872 * Set MIN_PROCESSING_INTERVAL for process_fleets * Add TODO
Configuration menu - View commit details
-
Copy full SHA for 2a89dff - Browse repository at this point
Copy the full SHA 2a89dffView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0ddaa13 - Browse repository at this point
Copy the full SHA 0ddaa13View commit details -
Configuration menu - View commit details
-
Copy full SHA for f5c8fcf - Browse repository at this point
Copy the full SHA f5c8fcfView commit details
Commits on Jul 7, 2025
-
Fix NVIDIA container toolkit bug in all backends (#2877)
Use cgroupfs as a Docker cgroup driver on all backends by default to work around an NVIDIA container toolkit bug where the container looses access to the GPU. The patch to `/etc/docker/daemon.json` is automatically applied in all VM-based backends if `/etc/docker/daemon.json` exists, has the NVIDIA runtime, does not explicitly set another cgroup driver, and `jq` is installed. This is not the case in Nebius. Lambda, and CUDO, so they still need custom code to apply the workaround - either installing `jq` or just writing a hardcoded `/etc/docker/daemon.json` that is known to work on this backend.
Configuration menu - View commit details
-
Copy full SHA for 66ffdd1 - Browse repository at this point
Copy the full SHA 66ffdd1View commit details
Commits on Jul 8, 2025
-
Allow configuring private GCP gateways without TLS certificates. ```yaml type: gateway name: example domain: gateway.example.com backend: gcp region: europe-west9 public_ip: false certificate: null ```
Configuration menu - View commit details
-
Copy full SHA for faab7aa - Browse repository at this point
Copy the full SHA faab7aaView commit details
Commits on Jul 9, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 2cf10cc - Browse repository at this point
Copy the full SHA 2cf10ccView commit details -
Switch to
e2-medium
for GCP gateways (#2886)Switching from `e2-small` to `e2-medium` decreases provisioning time from about 5 minutes to about 2 minutes. The bottleneck is the snap, apt, and pip package installation, which takes too long on `e2-small`, likely because of the burstable CPU - `e2-small` comes with 0.5-2 vCPU, while `e2-medium` comes with 1-2 vCPU, depending on the burst.
Configuration menu - View commit details
-
Copy full SHA for 7435ecf - Browse repository at this point
Copy the full SHA 7435ecfView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 0.19.17...0.19.18