New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error array_combine(): Argument #1 ($keys) and argument #2 ($values) must have the same number of elements in PivotByDimension #19806
Comments
This happened again |
This happened again. |
This happened again today. |
Happened here too
so there is no This is the backtrace when it happended:
I just patched to also handle this input. public function getBrandList(): array
{
if (\count($this->fullVersionList)) {
if (is_array(current($this->fullVersionList)) && array_key_exists('brand', current($this->fullVersionList))) {
return \array_combine(
\array_column($this->fullVersionList, 'brand'),
\array_column($this->fullVersionList, 'version')
) ?: [];
} else {
return @\array_combine(
@\array_column($this->fullVersionList, ''),
@\array_column($this->fullVersionList, 'version')
) ?: [];
}
}
return [];
} That's of course not the right fix – that would be to figure out why there is no |
@d--j the error your are having seems to be fully unrelated to the initial issue here. Even though the error message is the same. |
I got a bug like this with the same stack trace and it has the following params:
|
This happened again.
|
I get the same again yesterday and a few times over the last few months - despite the update with 4.14.1 However the error that jams-up the queue is caused by ClientHints.php as in the log below. Uncaught exception in ..../vendor/matomo/device-detector/ClientHints.php line 193: Since we have so much traffic I'm unable to ascertain what the actual entry is.. all i can do to get it working again is to delete the item or items at the front of the queue. and process manually. Is it the Queued Tracking Plugin that is causing the issue or does it have to do with something in the device-detector? Either way is causing our queues to sieze and buildup endlessly |
@achangjvi22 You particular error is unrelated to the one reported in this issue. |
This issue happened for us again |
stack trace:
The text was updated successfully, but these errors were encountered: