"Runtime measurement" leads to timed out errors

Created on 24 September 2024, 3 months ago

Problem/Motivation

If "Runtime measurement" is leaved checked, the default timeout is 1s, which could lead to a lot of error logs if the called endpoint is slower than that duration.

Steps to reproduce

  1. Create an http purger that called a slow endpoint, leave "Runtime measurement" checked.
  2. Change content and process queue.
  3. Watch the logs, the following error should pops: purger_httpbundled_xxxx: item failed due GuzzleHttp\Exception\ConnectException, details (JSON): {"msg":"cURL error 28: Resolving timed out after 1000 milliseconds (see https:\/\/curl.haxx.se\/libcurl\/c\/libcurl-errors.html)

Proposed resolution

Helper text $form['performance']['runtime_measurement_help'] should always be visible, its text should provide more details about default timeout (1s) and the possibility of heavy logs generation.

Additionally, ignore the errors linked to client timeout (by default or set by a new option)?

Data model changes

🐛 Bug report
Status

Active

Version

1.0

Component

Code

Created by

🇫🇷France O'Briat Nantes

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024