Deleted Actions artifacts remain counted against quota #2969

New issue

Open

opened 2026-08-01 18:14:16 +02:00 by gigahertz5288 · 0 comments

gigahertz5288 commented

2026-08-01 18:14:16 +02:00

Description

Deleted Forgejo Actions artifacts remain counted against my account quota even though the repository Actions-artifact API is empty. New artifact uploads fail with Quota exceeded.

Current authoritative API state

Instance version: 16.0.0-dev-668-1bdb1938+gitea-1.22.0
GET /api/v1/user/quota: artifact usage 1,621,485,448 bytes
size:assets:all limit: 1,572,864,000 bytes
GET /api/v1/user/quota/artifacts: 16 retained accounting entries totaling exactly 1,621,485,448 bytes
Repository GET /actions/artifacts: zero artifacts
All listed repository artifacts were deleted through DELETE /actions/artifacts/{id} and returned HTTP 204
Three rejected upload attempts remain represented in the quota inventory as zero-byte entries

The accounting remained unchanged for more than 15 hours after deletion. Multiple otherwise-successful CI jobs now fail only when forgejo/upload-artifact begins uploading, with ::error::Quota exceeded.

This appears related to Forgejo issue/PR forgejo/forgejo#7976, which changed quota calculation to ignore expired artifacts, but the current deployment is still counting deleted or inaccessible Actions artifact records.

Requested help

Could an administrator reconcile or purge the stale Actions-artifact quota records for my account, and confirm whether this is a deployment regression? I can provide affected repository/run IDs privately if needed.

## Description Deleted Forgejo Actions artifacts remain counted against my account quota even though the repository Actions-artifact API is empty. New artifact uploads fail with `Quota exceeded`. ## Current authoritative API state - Instance version: `16.0.0-dev-668-1bdb1938+gitea-1.22.0` - `GET /api/v1/user/quota`: artifact usage `1,621,485,448` bytes - `size:assets:all` limit: `1,572,864,000` bytes - `GET /api/v1/user/quota/artifacts`: 16 retained accounting entries totaling exactly `1,621,485,448` bytes - Repository `GET /actions/artifacts`: zero artifacts - All listed repository artifacts were deleted through `DELETE /actions/artifacts/{id}` and returned HTTP 204 - Three rejected upload attempts remain represented in the quota inventory as zero-byte entries The accounting remained unchanged for more than 15 hours after deletion. Multiple otherwise-successful CI jobs now fail only when `forgejo/upload-artifact` begins uploading, with `::error::Quota exceeded`. This appears related to Forgejo issue/PR [forgejo/forgejo#7976](https://codeberg.org/forgejo/forgejo/pulls/7976), which changed quota calculation to ignore expired artifacts, but the current deployment is still counting deleted or inaccessible Actions artifact records. ## Requested help Could an administrator reconcile or purge the stale Actions-artifact quota records for my account, and confirm whether this is a deployment regression? I can provide affected repository/run IDs privately if needed.

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

Codeberg/Community#2969

No description provided.

Rows
Columns