Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix goose configure to only write to config if chat completion check succeeds #1081

Closed
wants to merge 1 commit into from

Conversation

jasonkneen
Copy link

@jasonkneen jasonkneen commented Feb 5, 2025

Fixes #997

Update goose configure to only write OLLAMA_HOST to config if chat completion check succeeds.

  • Perform chat completion check before setting OLLAMA_HOST in the config.
  • Only set OLLAMA_HOST in the config if the chat completion check succeeds.
  • Update the configure_provider_dialog function to reflect these changes.

For more details, open the Copilot Workspace session.

…succeeds

Fixes block#997

Update `goose configure` to only write `OLLAMA_HOST` to config if chat completion check succeeds.

* Perform chat completion check before setting `OLLAMA_HOST` in the config.
* Only set `OLLAMA_HOST` in the config if the chat completion check succeeds.
* Update the `configure_provider_dialog` function to reflect these changes.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/block/goose/issues/997?shareId=XXXX-XXXX-XXXX-XXXX).
Copy link
Collaborator

@salman1993 salman1993 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for contributing! the linter is failing due to parentheses around (!config.exists()) . running cargo fmt should fix it

@michaelneale
Copy link
Collaborator

autogenerated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

goose configure writes to config even if chat completion check fails
3 participants