Skip to content

Resolve GuzzleHttp\Exception\RequestException error#1168

Open
dati18 wants to merge 9 commits into
mainfrom
fix-guzzelhttp-error
Open

Resolve GuzzleHttp\Exception\RequestException error#1168
dati18 wants to merge 9 commits into
mainfrom
fix-guzzelhttp-error

Conversation

@dati18

@dati18 dati18 commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

bumping guzzlehttp/guzzle from 7.10.5 to 7.12.0 triggered a bunch of error

The stack trace pointed to line 21 and 30 of PollForMediaWikiJob

The investigation is documented here.

Bug: T429593

@dati18 dati18 force-pushed the fix-guzzelhttp-error branch from c75d943 to db8eaba Compare June 18, 2026 11:55
@dati18 dati18 force-pushed the fix-guzzelhttp-error branch from db8eaba to e74a997 Compare June 18, 2026 12:02
@dati18 dati18 marked this pull request as draft June 18, 2026 12:25
@dati18 dati18 force-pushed the fix-guzzelhttp-error branch from 373a022 to 5287a4a Compare June 26, 2026 09:08
@dati18 dati18 marked this pull request as ready for review June 26, 2026 12:30
@tarrow

tarrow commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@dati18 Do you think there are any other places that we also need to ensure we've made this change?

From my quick looking I would expect us to need to think about at least our elasticsearch and queryservice hosts too. Do you agree?

For example:

Both of these get their host source from environment variables without a scheme:
https://github.com/wmde/wbaas-deploy/blob/328f6dcd3393a3d08fef5c33e655224c65e6d645/k8s/helmfile/env/production/api.values.yaml.gotmpl#L88-L89

An idea I had was to ensure that a scheme is specified when then config is parsed. If it's not we could then either add http:// or we could error. What do you think?

@tarrow tarrow left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@dati18 dati18 force-pushed the fix-guzzelhttp-error branch from 777f30d to ac2c9bb Compare June 29, 2026 15:56
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.

2 participants