Changes between Initial Version and Version 1 of Ticket #33282, comment 3


Ignore:
Timestamp:
Nov 12, 2021, 9:22:19 AM (3 years ago)
Author:
Simon Charette

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #33282, comment 3

    initial v1  
    11The issue seems related an attempt at doing a `GROUP BY` by a subquery that returns more than one row. See the `GROUP BY V0."hostname", (SELECT U0."name" FROM "lava_scheduler_app_devicetype" ...)` part.
    22
    3 The `Q(actual_device__isnull=False, actual_device__in=accessible_devices)` lookup in `RestrictedTestJobQuerySet.accessible_by_user` is causing that somehow, and I assume `Device.objects.accessible_by_user` is the culprit as it must do a subquery annotation somehow that is not limited to one row.
     3The `Q(actual_device__isnull=False, actual_device__in=accessible_devices)` lookup in `RestrictedTestJobQuerySet.accessible_by_user` is causing that somehow, and I assume `Device.objects.accessible_by_user` is the culprit as it must do a subquery annotation somehow that is not limited to one row or maybe your manual backport of 136ff592ad8aa8b7fa1e61435e5501cc98ce8573 is to blame? In call cases you'll want to debug `get_group_by_cols`.
    44
    55By giving a cursory look at your code base I couldn't identify the origin of the subquery annotation so I'll close with ''needsinfo'' for now but please re-open if you can create a minimal test case as I'll be monitoring this issue.
Back to Top