mirror of
https://github.com/fleetdm/fleet
synced 2026-04-21 21:47:20 +00:00
cfbc9d8829
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #33520 Recent changes to the users query accidentally introduced an ambiguous column error with the vscode extensions query. Fixed the SELECT statement in vscode_extensions to properly account for this No changes file added since this is an unreleased bug and the feature has a changes file # Checklist for submitter If some of the following don't apply, delete the relevant line. - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing No automated tests in this area so no tests to update/add - [x] Added/updated automated tests - [x] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [x] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - [x] Confirmed that the fix is not expected to adversely impact load test results |
||
|---|---|---|
| .. | ||
| gen_queries_doc.go | ||
| queries.go | ||
| queries_test.go | ||
| utils.go | ||