Skip to content

Mend hot fuzz target imports and return types #1185

Closed
Closed
Mend hot fuzz target imports and return types#1185
Labels
Stellar WaveStellar Wave Program issue

Description

@greatest0fallt1me
greatest0fallt1me
opened on Sep 27, 2026

Summary

callora-hot-fuzz fails to compile: main.rs:31 imports HotError, which is private in callora-hot, and line 162 treats a Result as ().

Why this matters

The fuzz target is a workspace member, so its compile error breaks cargo test --workspace; pause/cooldown state machines go unfuzzed.

Scope

Re-export HotError from callora_hot (pub use errors::HotError) and adapt the call site to use the try_ client variant.

Relevant code in CalloraOrg/Callora-Contracts:

  • contracts/hot/fuzz/targets/main.rs
  • contracts/hot/src/errors.rs

Priority

Medium

Acceptance criteria

  • cargo check -p callora-hot-fuzz succeeds
  • HotError exported publicly
  • Fuzz target runs locally
  • Fuzz harness asserts pause and unpause never both succeed inside one cooldown window

Validation

cargo check -p callora-hot-fuzz

Non-goals

  • Typo-only, formatting-only, or cosmetic changes.
  • Unrelated refactors, dependency upgrades, or broad rewrites.
  • Removing safeguards or weakening validation to make tests pass.

Contributor application

Before coding, describe the affected modules, proposed state/invariant changes, test strategy, compatibility considerations, and an estimate. Wait for assignment before starting implementation.

PR requirements

Use a feature branch and include Closes #<issue-number>. Address every criterion, map criteria to code and tests, explain security and failure-mode handling, and ensure CI passes.

Quality review

A maintainer will assess correctness, completeness, test depth, compatibility, observability, and adverse-case handling. A substantive implementation is required; merge or CI status alone does not guarantee reward eligibility.

Generated by Claude Code

Activity

  1. greatest0fallt1me
    changed the title [-]Keep leaderboard rank pages deterministic[/-] [+]Add focused test coverage for contracts/registry/src/lib.rs[/+] on Sep 27, 2026
  2. greatest0fallt1me
    changed the title [-]Add focused test coverage for contracts/registry/src/lib.rs[/-] [+]Mend hot fuzz target imports and return types[/+] on Sep 27, 2026
  3. greatest0fallt1me
    added
    Stellar WaveStellar Wave Program issue
    on Sep 27, 2026

  4. Bigtura commented on Sep 27, 2026

    @Bigtura
    Bigtura
    on Sep 27, 2026 – with Drips Wave
    Contributor

    @Bigtura has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello Maintainer, I’d like to work on this task.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bigtura to this issue.

  5. olufunsoolutayo commented on Sep 29, 2026

    @olufunsoolutayo
    olufunsoolutayo
    on Sep 29, 2026 – with Drips Wave

    @olufunsoolutayo has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Please assign this issue to me Maintainer. I'm grateful

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @olufunsoolutayo to this issue.

  6. AkpakaProsper commented on Sep 29, 2026

    @AkpakaProsper
    AkpakaProsper
    on Sep 29, 2026 – with Drips Wave

    @AkpakaProsper has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello Maintainer, can I work on this issue?

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @AkpakaProsper to this issue.

  7. Devadakene commented on Sep 30, 2026

    @Devadakene
    Devadakene
    on Sep 30, 2026 – with Drips Wave
    Contributor

    @Devadakene has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    I would like to work on this issue having worked on something similar issues in the past. Please assign

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Devadakene to this issue.

  8. Rodrigoue9 commented on Oct 3, 2026

    @Rodrigoue9
    Rodrigoue9
    on Oct 3, 2026

    Hi @maintainers! I'd like to work on this issue. Here is my proposed technical approach:

    Proposed Technical Approach:

    1. Contract Logic Implementation: Implement the required Soroban smart contract logic in Rust, ensuring strict validation, authorization checks (require_auth), and gas optimization.
    2. Storage Layout & State Management: Maintain safe data key patterns, TTL management, and prevent state inconsistency or unauthorized state mutations.
    3. Events & Error Encoding: Emit strongly typed contract events and return descriptive custom errors for all failure modes.
    4. Comprehensive Test Vectors: Implement Rust unit and integration tests using soroban-sdk::Env verifying both success and failure execution paths.

    Key Files:

    • contracts/**/src/lib.rs (contract entrypoints and interface implementations)
    • contracts/**/src/types.rs or storage.rs (types, data keys, and state)
    • contracts/**/src/test.rs (unit tests and integration vectors)

    Verification & Testing:

    • Run cargo test across all contract crates verifying 100% pass rate.
    • Run cargo clippy --all-targets -- -D warnings and cargo fmt --check.
    • Verify Soroban WASM build: soroban contract build.

    Relevant Track Record:

    I have successfully implemented and merged multiple production PRs across the Stellar ecosystem and Web3 open-source projects (e.g., Bitcoindefi/OpenAO #218, cybermax4200/stellar-did-credit #898 & #900, and FindMalek/sonaraem #416).

    Please feel free to assign this issue to me so I can proceed with the implementation. Thank you!

  9. guptakumarranjeet150 commented on Oct 7, 2026

    @guptakumarranjeet150
    guptakumarranjeet150
    on Oct 7, 2026

    Hi team,

    Happy to tackle this. Here is how I plan to implement it:

    Plan:

    1. Audit storage layout and state invariants ensuring strict auth guards.
    2. Implement deterministic state transitions with safe checked arithmetic.
    3. Add hermetic unit and regression tests covering authorized, unauthorized, and boundary edge cases.
    4. Profile instruction and CPU/gas limits under Soroban host environment.

    Please assign this to me if the plan looks good. Thanks!

  10. inioluwanureni90-cell commented on Oct 15, 2026

    @inioluwanureni90-cell
    inioluwanureni90-cell
    on Oct 15, 2026 – with Drips Wave

    @inioluwanureni90-cell has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello, I’m interested in working on this issue and would appreciate being assigned to it. Thank you.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @inioluwanureni90-cell to this issue.

  11. Bkizzy16 commented on Oct 15, 2026

    @Bkizzy16
    Bkizzy16
    on Oct 15, 2026 – with Drips Wave

    @Bkizzy16 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Please kindly assign me this issue.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bkizzy16 to this issue.

  12. iyanumajekodunmi756 commented on Oct 15, 2026

    @iyanumajekodunmi756
    iyanumajekodunmi756
    on Oct 15, 2026 – with Drips Wave

    @iyanumajekodunmi756 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I would love to work on this issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @iyanumajekodunmi756 to this issue.

  13. stevengrams commented on Oct 16, 2026

    @stevengrams
    stevengrams
    on Oct 16, 2026 – with Drips Wave

    @stevengrams has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I will like to work on this issue maintainer it's in the area of my expertise

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @stevengrams to this issue.

  14. lienhoatienphung-svg commented on Oct 16, 2026

    @lienhoatienphung-svg
    lienhoatienphung-svg
    on Oct 16, 2026

    Hi! I have implemented and verified this in #1378 with full unit test coverage and rustfmt compliance.

  15. lienhoatienphung-svg
    added a commit that references this issue on Oct 16, 2026

    fix(hot): re-export HotError and fix try_init return handling in fuzz…

    919f343

  16. Escelit commented on Oct 16, 2026

    @Escelit
    Escelit
    on Oct 16, 2026 – with Drips Wave
    Contributor

    @Escelit has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    I'd like to take this issue. It covers an important part of the project, and I want to contribute something that fits the existing architecture and development standards and holds up over time.

    I've worked across backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I'm comfortable reading an unfamiliar codebase, tracking an issue down to its root cause, and writing clean fixes with tests that guard against regressions.

    My plan is to start by reading the existing implementation and project conventions, then build the solution in small, focused steps. I'll test the changes, document them where needed, and keep the code simple so nothing existing breaks. I'll also respond quickly to review feedback so the PR is easy to merge.

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Escelit to this issue.

  17. El-Khaleefa01 commented on Oct 16, 2026

    @El-Khaleefa01
    El-Khaleefa01
    on Oct 16, 2026 – with Drips Wave

    @El-Khaleefa01 has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hey maintainer
    kindly assign me please

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @El-Khaleefa01 to this issue.

  18. greatest0fallt1me
    closed this as completedon Oct 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Stellar WaveStellar Wave Program issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions