Skip to content

Is there a reason to keep timeouts hardcoded? #5944

@thbighead

Description

@thbighead

I'm using WP-CLI to maintain WordPress environments, and sometimes I get an issue about timeout (each one with a different milliseconds value to trigger it) like that:

Error: Ocorreu um erro inesperado. Pode estar algo errado com o WordPress.org ou com a configuração deste servidor. Se continuar com problemas, por favor tente pedir ajuda no fórum de suporte. "cURL error 28: Connection timed out after 3002 milliseconds"

This one I got while executing the following command: wp language plugin install pt_PT --all

After months trying to change those timeout settings, search in documentations and hacking your code, I finally found some comments of others saying those timeout values are hard-coded for each request with a different value (which explains why the timeout values were different sometimes into the error messages) without any way to override it.

My questions are:

  • Am I missing something, or I really can't change those timeout values?
  • Why you keep all those timeouts hard-coded and impossible to override?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions