Commits

The translation fix reaches production (v0.1.70)

The translation fix reaches production

The translation fix reaches production

For days, long articles went untranslated: the translation model is a reasoning model and spent part of the token budget thinking before responding. When the reasoning exceeded the budget, the response came back empty and the work was lost.

The solution has three parts: inspect the reason the response ended before examining the content (a truncation is no longer treated as a generic error), retry with twice the budget, and raise the translation limit. Verified with real calls to the provider: no truncation and no empty response.

A silent downgrade, plugged

Meanwhile, a loophole appeared that no one had noticed: the updater did not compare the manifest version with the installed version. If someone had clicked "Update" in the panel, it would have rolled back to the previous version without any warning, undoing the fix. The updater now rejects the downgrade with a clear message, and three tests guard against it.

Version 0.1.70, deployed

The tag failed on the first attempt and was rerun: CI was green, the images were published, and the production container was updated. Yesterday's article in the development diary now has all three languages published and verified through the public API.

Lesson of the day

A "provider returned an empty response" error can hide a very different root cause: in this case, a model that spends its budget thinking. Before retrying, you need to inspect why the response was empty.