Skip to content

Conversation

@Oaphi
Copy link
Member

@Oaphi Oaphi commented Jan 11, 2026

closes #1891

The error is likely not reproducible outside of very specific circumstances, but it doesn't mean we shouldn't gracefully handle it instead of outright failing with a server error 500:

Screenshot from 2026-01-11 03-41-49

Repro is handled by the added test case, so the only part to test here manually if one wants to do that is that normal post creation still works.

@Oaphi Oaphi requested review from a team and ArtOfCode- January 11, 2026 00:51
@codecov
Copy link

codecov bot commented Jan 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.65%. Comparing base (a93b782) to head (e8a8c1a).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files
Components Coverage Δ
controllers 74.70% <100.00%> (+0.04%) ⬆️
helpers 84.91% <ø> (ø)
jobs 80.59% <ø> (ø)
models 90.09% <ø> (ø)
tasks 61.11% <ø> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ArtOfCode- ArtOfCode- merged commit a552309 into develop Jan 11, 2026
21 of 27 checks passed
@ArtOfCode- ArtOfCode- deleted the 0valt/1891/post-500-fix branch January 11, 2026 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

500 while trying to post answer (tracking issue)

3 participants