## Proposal In https://gitlab.com/gitlab-org/gitlab/-/issues/324206 we added an error status to the package model to allow us to display when a package was in an "error" state after failing background processing and also a "pending" state during background processing. We should add a `status_message` column to the package model to capture the actual error that occurred so we can give the user more information about why a package upload has failed. ### Benefits Users will see if the failure was due to an internal error (500), or if it was due to something like some data being invalid such as the name or version of the package. Users will be able to debug their problems more quickly with this information. ### Implementation plan - [x] Add new `status_message` column to the package model. (Done in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122299) - [x] Update the [extraction workers](https://gitlab.com/gitlab-org/gitlab/-/blob/1b85b853b0498ea2e68fcaee091427acea5a3e22/app/workers/packages/nuget/extraction_worker.rb#L24) to add the message to this column: `package_file.package.update_column(:status_message, e.message)`. (Done in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/122299) - [x] Add the column to the GraphQL payload (https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134183+) - [x] Display the message on the frontend (may require some UX input) #### Package formats Those package formats have all background jobs that process uploaded packages. They potentially need an update to use the `status_message` column: * NuGet * Debian * Helm * Rubygems