Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • aurweb aurweb
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 89
    • Issues 89
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

Admin message

Due to an influx of spam, we have had to temporarily disable account registrations. Please write an email to accountsupport@archlinux.org, with your desired username, if you want to get access. Sorry for the inconvenience.

Admin message

Merge requests and Issues are disabled on Packages for non Arch Linux staff - we plan to open these to all registered Gitlab users in the foreseeable future.

  • Arch LinuxArch Linux
  • aurwebaurweb
  • Issues
  • #387

Requests query excludes requests no longer owned by a user

Checklist

  • I confirm that this is an issue with aurweb's code and not a user-uploaded package.
  • I have described the bug in complete detail in the Description section.
  • I have specified steps in the Reproduction section.
  • I have included the versions which are affected in the Version(s) section.

Description

When viewing package requests as an elevated user (a TU or above), package requests which do not have a valid User association are excluded from the list. This can occur when a user previously files a package request, then their account is deleted in some way.

Package requests which have been filed should remain valid until dealt with.

Reported by @artafinde

Reproduction

  1. As a normal user, file a package request
  2. Login as a TU, view Requests, where you can see the package request which was just created
  3. Delete the account manually: DELETE FROM Users WHERE Users.Username == '<the_normal_users_name>';
  4. Login as a TU, view requests, where you can no longer see the package request which was just created.

Version(s)

v6.1.2

Edited Sep 05, 2022 by Kevin Morris
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking