3d5ddcccf0
Previously we were guessing the context window size here:8c3f09e31e/crates/ollama/src/ollama.rs (L22)This is inaccurate and must be updated manually. This PR ensures that we extract the context window size from the request in the same way that the Ollama CLI does when running `ollama show <model-name>` (Relevant code is [here](3d32249c74/cmd/cmd.go (L860))) The format looks like this: ```json { "model_info": { "general.architecture": "llama", "llama.context_length": 132000 } } ``` Once this PR is merged we could technically remove the old code8c3f09e31e/crates/ollama/src/ollama.rs (L22)I decided to keep it for now, as it is unclear if the necessary fields are available via the API on older Ollama versions. Release Notes: - Fixed an issue where Ollama models would use the wrong context window size
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS and Linux you can download Zed directly or install Zed via your local package manager.
Other platforms are not yet available:
- Windows (tracking issue)
- Web (tracking issue)
Developing Zed
- Building Zed for macOS
- Building Zed for Linux
- Building Zed for Windows
- Running Collaboration Locally
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.