Error
- mwversion: 1.44.0-wmf.25
- reqId: 9bf6a331-4d51-42ea-8205-62bc50be4312
- Find reqId in Logstash
normalized_message
[{reqId}] {exception_url} PHP Warning: Undefined array key 27Impact
Notes
There were a spew of these for different array keys...
| Reedy | |
| Apr 16 2025, 1:24 PM |
| F59266546: Screenshot 2025-04-16 at 14.24.45.png | |
| Apr 16 2025, 1:25 PM |
[{reqId}] {exception_url} PHP Warning: Undefined array key 27There were a spew of these for different array keys...
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | Feature | None | T72077 Order of named parameters passed to parser functions is lost | ||
| Open | None | T204307 Parser Functions should support named parameters | |||
| Open | PRODUCTION ERROR | cscott | T392085 PHP Warning: Undefined array key 27 |
Same stacktrace as T391439: WikifunctionsPFragmentHandler: Make extractWikifunctionCallArguments ignore named arguments but that other one is triggered on https://www.wikifunctions.org/ by WikiLambda, while this very T392085 is on test.wikipedia.org
Re-triggered logstash link looking at https://test.wikipedia.org/wiki/MavetunaTest. The page is filled with Wikifunctions client calls and simple wikitext. Are we accidentally triggering the wrong path here?
Yeah, I think this is caused by using named parameters with wikifunctions. I'm working on that in T204307 and one that lands these should go away.