Skip to content

Fix null errors on live reads and stop leaked API test deployments - #9839

Merged
Martin-Molinero merged 1 commit into
masterfrom
fix-live-read-null-errors
Sep 28, 2026
Merged

Martin-Molinero merged 1 commit into
masterfrom
fix-live-read-null-errors

Conversation

@Martin-Molinero

Copy link
Copy Markdown
Member
  • LiveAlgorithmResultsJsonConverter set Errors to null when the response had no errors array (every successful read), so string.Join on it threw. It now keeps an empty list like every other response.
  • CreatesLiveAlgorithm failed on exactly that, and its catch deleted the project without stopping the deployment, leaving live nodes busy. The catch now liquidates first and rethrows with the original stack.

Verified locally: converter unit tests plus CreatesLiveAlgorithm and ReadLiveInsightsWorksAsExpected pass against the API.

🤖 Generated with Claude Code

…the live api test fails

The live results converter set Errors to null whenever the response carried no errors
array, which is every successful read, so callers joining the errors threw. The
CreatesLiveAlgorithm api test hit exactly that, and its cleanup deleted the project
without stopping the deployment, leaving live nodes busy for later runs.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@Martin-Molinero
Martin-Molinero merged commit ebd7268 into master Sep 28, 2026
12 of 16 checks passed
@Martin-Molinero
Martin-Molinero deleted the fix-live-read-null-errors branch September 28, 2026 17:49
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.

1 participant