Skip to content

Feature: Please Expose TIMEOUT as Configurable #1

@daryltucker

Description

@daryltucker

Hey, digging deepshell so far. Thanks for creating it.

I am facing a problem where deepshell is clearly interacting with Ollama (I can determine this from the logs and seeing deepshell hit the server), but times out.

While I think a TIMEOUT is great, for one, I think it should be configurable, and for two, it should likely default to not use a timeout/at least provide that functionality. I'd also suggest separating this out into two timeouts:

  1. Query Timeout
    • The server was reachable, but we aren't willing to wait longer than this duration
    • Abort Request if this duration is exceeded
    • Configurable
    • Disableable
    • Returns an error stating we connected, but Query Timeout exceeded.
  2. HTTP Timeout / Timeout
    • The server was unreachable
    • Sane value (ie: 5-10s)
    • Returns an error stating we could not connect to the backend.

Ultimately, treating HTTP Timeout as an error, while allowing people to also set their own Query Timeout, even if the backend is connectable.

Thanks for your efforts and consideration of this request.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions