luanti-org / luanti-org/contentdb

Immediate release deletion can result in 404s

Open
#574 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

+ Releases Bug
Dominant language
Python
Stars
115
Forks
62
Avg merge
19h 7m
Merged PRs (30d)
5

Description

Releases should be soft deleted then hard deleted after an hour

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the release deletion endpoint and the code that serves release requests. Trace how deletion currently affects release lookups, then identify the existing tests for release deletion or missing releases. Done means deletion first hides the release without causing 404s, and permanent removal occurs after an hour.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.