Skip to content

Conversation

@edward-ly
Copy link
Contributor

@edward-ly edward-ly commented May 5, 2025

Summary

It is currently 4 weeks. It could be raised to 4 months.

There a bit of a compromise to find. Designers want the tasks to be kept forever and engineers want to cleanup soon to save storage space and DB.

Checklist

Signed-off-by: Edward Ly <contact@edward.ly>
@edward-ly edward-ly requested a review from a team as a code owner May 5, 2025 18:30
@edward-ly edward-ly requested review from come-nc, icewind1991 and provokateurin and removed request for a team May 5, 2025 18:30
@edward-ly
Copy link
Contributor Author

/backport to stable31

@edward-ly
Copy link
Contributor Author

/backport to stable30

Copy link
Member

@provokateurin provokateurin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤷‍♀️

@provokateurin provokateurin merged commit 5cf799b into master May 6, 2025
195 of 197 checks passed
@provokateurin provokateurin deleted the fix/task-cleanup-delay branch May 6, 2025 09:56
Copy link
Member

@jancborchardt jancborchardt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@julien-nc @edward-ly if it’s still limited, could we have a notice in the interface somewhere about this? E.g. in the same place as the "This is AI-generated, please double check" notice we also need?
(Just for the record, as said in the topic also, I’d rather have it not limited.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 🎉 Done

Development

Successfully merging this pull request may close these issues.

Increase task cleanup delay

5 participants