0.9 release

.github/workflows/docker.yml

@@ -10,8 +10,8 @@ on:
       - '!*-dev'
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }} 
-  
+  group: ${{ github.workflow }}-${{ github.head_ref || github.ref_name }}
+
   # If this is enabled it will cancel current running and start latest
   cancel-in-progress: true
 
@@ -28,6 +28,15 @@ jobs:
       # with sigstore/fulcio when running outside of PRs.
       id-token: write
 
+    strategy:
+      matrix:
+        device-type: [cuda, rocm]
+        include:
+          - device-type: cuda
+            image-suffix: ''
+          - device-type: rocm
+            image-suffix: '-rocm'
+
     steps:
       - name: Free Disk Space (Ubuntu)
         uses: jlumbroso/free-disk-space@main
@@ -69,8 +78,10 @@ jobs:
           password: ${{ secrets.DOCKERHUB_TOKEN }}
 
       - name: Generate image name
+        env:
+          IMAGE_SUFFIX: ${{ matrix.image-suffix }}
         run: |
-          echo "IMAGE_NAME=${GITHUB_REPOSITORY,,}" >>${GITHUB_ENV}
+          echo "IMAGE_NAME=${GITHUB_REPOSITORY,,}${IMAGE_SUFFIX}" >>${GITHUB_ENV}
 
       - uses: int128/docker-build-cache-config-action@v1
         id: cache
@@ -98,7 +109,7 @@ jobs:
         id: build-and-push
         uses: docker/[email protected]
         with:
-          file: Dockerfile
+          file: docker/Dockerfile.${{ matrix.device-type }}
           push: true
           context: .
           tags: ${{ steps.meta.outputs.tags }}
@@ -113,4 +124,3 @@ jobs:
           username: ${{ secrets.DOCKERHUB_USERNAME }}
           password: ${{ secrets.DOCKERHUB_TOKEN }}
           repository: tabbyml/tabby
-

.github/workflows/release.yml

@@ -27,11 +27,12 @@ jobs:
     container: ${{ matrix.container }}
     strategy:
       matrix:
-        binary: [aarch64-apple-darwin, x86_64-manylinux2014, x86_64-windows-msvc, x86_64-manylinux2014-cuda117, x86_64-manylinux2014-cuda122, x86_64-windows-msvc-cuda117, x86_64-windows-msvc-cuda122, x86_64-manylinux2014-rocm57]
+        binary: [aarch64-apple-darwin, x86_64-manylinux2014, x86_64-windows-msvc, x86_64-manylinux2014-cuda117, x86_64-manylinux2014-cuda122, x86_64-windows-msvc-cuda117, x86_64-windows-msvc-cuda122]
         include:
           - os: macos-latest
             target: aarch64-apple-darwin
             binary: aarch64-apple-darwin
+            build_args: --features prod-db
           - os: dimerun-k3-ubuntu2204
             target: x86_64-unknown-linux-gnu
             binary: x86_64-manylinux2014
@@ -63,11 +64,6 @@ jobs:
             ext: .exe
             build_args: --features cuda,prod-db
             windows_cuda: '12.2.0'
-          - os: dimerun-k3-ubuntu2204
-            target: x86_64-unknown-linux-gnu
-            binary: x86_64-manylinux2014-rocm57
-            container: ghcr.io/cromefire/hipblas-manylinux/2014/5.7:latest
-            build_args: --features static-ssl,rocm,prod-db
 
     env:
       SCCACHE_GHA_ENABLED: true

.github/workflows/test-rust.yml

@@ -28,7 +28,7 @@ concurrency:
   cancel-in-progress: true
 
 env:
-  RUST_TOOLCHAIN: 1.73.0
+  RUST_TOOLCHAIN: 1.76.0
 
 jobs:
   tests:

.gitignore

@@ -3,4 +3,5 @@ node_modules
 .idea/
 .DS_Store
 .vscode/
+local/
 __pycache__

CONTRIBUTING.md

@@ -29,16 +29,22 @@ apt-get install protobuf-compiler libopenblas-dev
 choco install protoc
 ```
 
+Some of the tests require mailtutan SMTP server which you can install with:
+
+```bash
+cargo install mailtutan
+```
+
 Before proceeding, ensure that all tests are passing locally:
 
 ```
 cargo test -- --skip golden
 ```
 
-Golden tests should be skipped on all platforms except Apple silicon (M1/M2), because they have not been created for other platforms yet.
-
 This will help ensure everything is working correctly and avoid surprises with local breakages.
 
+Golden tests, which run models and check their outputs against previous "golden snapshots", should be skipped for most development purposes, as they take a very long time to run (especially the tests running the models on CPU). You may still want to run them if your changes relate to the functioning of or integration with the generative models, but skipping them is recommended otherwise.
+
 ## Building and Running
 
 Tabby can be run through `cargo` in much the same manner as docker:
@@ -78,6 +84,7 @@ By default, Tabby will start on `localhost:8080` and serve requests.
 Tabby is broken up into several crates, each responsible for a different part of the functionality. These crates fall into two categories: Fully open source features, and enterprise features. All open-source feature crates are located in the `/crates` folder in the repository root, and all enterprise feature crates are located in `/ee`.
 
 ### Crates
+
 - `crates/tabby` - The core tabby application, this is the main binary crate defining CLI behavior and driving the API
 - `crates/tabby-common` - Interfaces and type definitions shared across most other tabby crates, especially types used for serialization
 - `crates/tabby-download` - Very small crate, responsible for downloading models at runtime

Makefile

@@ -1,7 +1,7 @@
 fix:
 	cargo machete --fix || true
 	cargo +nightly fmt
-	cargo +nightly clippy --fix --allow-dirty --allow-staged
+	cargo clippy --fix --allow-dirty --allow-staged
 
 fix-ui:
 	cd ee/tabby-ui && yarn format:write && yarn lint:fix