[PR #10201] [CLOSED] server: do not attempt to parse offset file as gguf #18448

Closed
opened 2026-04-16 06:35:17 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/10201
Author: @BruceMacD
Created: 4/9/2025
Status: Closed

Base: mainHead: brucemacd/create-no-loop


📝 Commits (1)

  • 0495014 server: do not attempt to parse offset file as gguf

📊 Changes

1 file changed (+24 additions, -30 deletions)

View changed files

📝 server/create.go (+24 -30)

📄 Description

This logic was causing issues for me when importing a gguf that had some padding at the end of the file. The valid gguf would be read, but then it would try to read the offset as a different gguf file. This does not seem right.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/10201 **Author:** [@BruceMacD](https://github.com/BruceMacD) **Created:** 4/9/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `brucemacd/create-no-loop` --- ### 📝 Commits (1) - [`0495014`](https://github.com/ollama/ollama/commit/04950140ec1c62ea48450845354a9a28f905425e) server: do not attempt to parse offset file as gguf ### 📊 Changes **1 file changed** (+24 additions, -30 deletions) <details> <summary>View changed files</summary> 📝 `server/create.go` (+24 -30) </details> ### 📄 Description This logic was causing issues for me when importing a gguf that had some padding at the end of the file. The valid gguf would be read, but then it would try to read the offset as a different gguf file. This does not seem right. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-16 06:35:17 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#18448