Skip to content

Conversation

@sanity
Copy link
Contributor

@sanity sanity commented Dec 22, 2025

Summary

Add explicit NotFound response type to the client API to distinguish "contract not found" from other failure modes like timeouts.

Changes

  • Add NotFound table to FlatBuffers schema with instance_id field
  • Add NotFound variant to ContractResponse enum
  • Update into_fbs_bytes to serialize NotFound
  • Update Display impl to handle NotFound
  • Regenerate flatbuffers with flatc 24.3.25 for compatibility
  • Bump version to 0.1.29

Context

This enables freenet-core to return ContractResponse::NotFound when a GET or SUBSCRIBE operation determines that a contract doesn't exist after exhaustive search, rather than returning a generic error.

Related: freenet/freenet-core#2368

Testing

  • All existing tests pass
  • Build verified with freenet-core

🤖 Generated with Claude Code

sanity and others added 2 commits December 21, 2025 22:14
Add explicit NotFound response type to the client API to distinguish
"contract not found" from other failure modes like timeouts.

Changes:
- Add NotFound table to FlatBuffers schema with instance_id field
- Add NotFound variant to ContractResponse enum
- Update into_fbs_bytes to serialize NotFound
- Update Display impl to handle NotFound
- Regenerate flatbuffers with flatc 24.3.25 for compatibility
- Bump version to 0.1.29

This enables freenet-core to return ContractResponse::NotFound when
a GET or SUBSCRIBE operation determines that a contract doesn't exist
after exhaustive search, rather than returning a generic error.

Closes #2368

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <[email protected]>
@sanity sanity merged commit 3b700ad into main Dec 22, 2025
6 of 9 checks passed
@sanity sanity deleted the fix-flatbuffers-and-add-notfound branch December 22, 2025 04:20
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.

2 participants