Ollama branch name generation doesn't work

[sersorrel]

Version

Version 0.14.4 (20241213.093904)

Operating System

macOS

Distribution Method

dmg (Apple Silicon)

Describe the issue

Hitting "Generate branch name" with the Ollama backend configured (default settings – endpoint http://127.0.0.1:11434, model llama3) results in the error "Failed to generate branch name: The string did not match the expected pattern".

I do not really understand the network requests I'm seeing in devtools, but there's a request to plugin:http|fetch_send with a strange-looking response:

{
    "status": 403,
    "statusText": "Forbidden",
    "headers": [
        [
            "date",
            "Fri, 20 Dec 2024 11:31:26 GMT"
        ],
        [
            "content-length",
            "0"
        ]
    ],
    "url": "http://127.0.0.1:11434/api/chat",
    "rid": 3377205724
}

I've checked that Ollama is actually installed and running:

$ http POST http://127.0.0.1:11434/api/chat model=llama3
HTTP/1.1 200 OK
Content-Length: 137
Content-Type: application/json; charset=utf-8
Date: Fri, 20 Dec 2024 11:31:59 GMT

{
    "created_at": "2024-12-20T11:31:59.41741Z",
    "done": true,
    "done_reason": "load",
    "message": {
        "content": "",
        "role": "assistant"
    },
    "model": "llama3"
}

How to reproduce

Configure GitButler to use Ollama, and try to generate a branch name.

Expected behavior

Ollama should be able to generate a branch name (like e.g. OpenAI).

Relevant log output

No response

[Caleb-T-Owens]

Hi! I believe you might be running into an issue related to our app permissions. Tauri has strong sandboxing around what the frontend can access.

Could you try 0.0.0.0 or localhost because I believe we have those whitelist.

[sersorrel]

localhost gives the same error; 0.0.0.0 produces a different error: "url not allowed on the configured scope: http://0.0.0.0:11434/api/chat"

[Caleb-T-Owens]

Sorry for the trouble! I'll spin up ollama and try it out this afternoon.

[Caleb-T-Owens]

I've had a go running it, and it seems to work in development mode 😬. I'm currently on holiday and debugging differences between development and production builds does not sound super enjoyable, so I'm going to put this onto my todolist for new year.

Sorry for any inconvenience.

[ivanglushko]

+1 Experiencing the same error

[ikitozen]

+1 same error :)

[mietl]

error + 1

[mtsgrd]

Auto-closed when I merged the likely fix, so re-opening until it has been verified.

[Caleb-T-Owens]

I'll have a go now 👍

[Caleb-T-Owens]

By "now" I mean, in 30 minutes time when a nightly build has finished chugging away

[Caleb-T-Owens]

I'm getting these strange "string did not match the expected pattern" errors 🤔

[mtsgrd]

I made a mistake in the previous pr: #5885

[ivanglushko]

Didn't work for me

[mtsgrd]

Can you try pointing gitbutler at localhost or 127.0.0.1?

[ivanglushko]

Can you try pointing gitbutler at localhost or 127.0.0.1?

[mtsgrd]

Argh. Let me properly debug this later today.