Skip to content

Wrong returned status code (successful vs unsuccessful results) #637

Description

@Thanatermesis

Issue

I think that I reported this before but cecli still have wrongly returned status code, for example see this case / test:

/t/test git:master ❯❯❯ if cecli testfile.txt --no-suggest-shell-commands --message="change foo to wombat"  ; then echo yes ; else echo noooooooooooooooooooooooooooooooooo ; fi                                                                                                                                               modified
─────────────────────────────────────────────────────────────────────────────────────────────────
litellm.MidStreamFallbackError: litellm.ServiceUnavailableError: Vertex_ai_betaException -
{
  "error": {
    "code": 503,
    "message": "This model is currently experiencing high demand. Spikes in demand are usually temporary. Please try again later.",
    "status": "UNAVAILABLE"
  }
}
 Original exception: ServiceUnavailableError: litellm.ServiceUnavailableError: Vertex_ai_betaException -
{
  "error": {
    "code": 503,
    "message": "This model is currently experiencing high demand. Spikes in demand are usually temporary. Please try again later.",
    "status": "UNAVAILABLE"
  }
}

Response parsing error.
yes
/t/test git:master ❯❯❯

The model failed and so cecli was not able to run my request, this should have returned a status 1 which should have resulted in the "noooooooo" answer in the end (and not the "yes" one).

Seems like there's multiple cases on cecli that returns "success" where clearly was not success, I recommend to run cecli against cecli to search for these cases and fix the issues

Version and model info

cecli 1.0.0rc13

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions