Skip to content

tooling/sanctifier-core: Add unit tests + fixtures (events analysis (S008) gas/correctness) #503

Closed
#1064
Closed
tooling/sanctifier-core: Add unit tests + fixtures (events analysis (S008) gas/correctness)#503
#1064
Assignees
abayomiwav
Labels
Stellar WaveIssues in the Stellar wave programcomponent:coretooling/sanctifier-core (analysis engine)difficulty:mediumModerate changepriority:p2Medium prioritystatus:readyClear spec, ready for implementationtype:testingTest coverage, harnesses, fuzzing, QA
Milestone
v0.2 — Security + Correctness Hardening

Description

@Gbangbolaoluwagbemiga
Gbangbolaoluwagbemiga
opened on Apr 23, 2026

Problem

This work item hardens tooling/sanctifier-core in the area of events analysis (S008) gas/correctness so the project can
scale in production (reliable CI, predictable outputs, and safe-by-default behavior).

Work

  • Identify the owner modules/files inside tooling/sanctifier-core for events analysis (S008) gas/correctness.
  • Implement the change described by Add unit tests + fixtures with minimal breaking surface.
  • Add tests (unit + integration where relevant) and ensure they run in CI.
  • Update docs/examples so contributors can adopt the new behavior confidently.

Acceptance criteria

  • CI passes for the touched area (lint, tests, and any component-specific workflow).
  • Behavior is documented (link from DOCUMENTATION_INDEX.md or the nearest canonical doc).
  • Output formats remain stable; if changes are required, version bump + migration notes are included.

Notes

Component: tooling/sanctifier-core
Subarea: events analysis (S008) gas/correctness
If this expands beyond a single PR, split into sub-issues and cross-link.

Activity

  1. Gbangbolaoluwagbemiga
    added this to the v0.2 — Security + Correctness Hardening milestone on Apr 23, 2026
  2. Gbangbolaoluwagbemiga
    added
    difficulty:mediumModerate change
    type:testingTest coverage, harnesses, fuzzing, QA
    component:coretooling/sanctifier-core (analysis engine)
    priority:p2Medium priority
    status:readyClear spec, ready for implementation
    on Apr 23, 2026
  3. drips-wave
    added
    Stellar WaveIssues in the Stellar wave program
    on Jun 27, 2026

  4. emteebug12-jpg commented on Jun 27, 2026

    @emteebug12-jpg
    emteebug12-jpg
    on Jun 27, 2026 – with Drips Wave

    @emteebug12-jpg has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

    Hi maintainers! I’d love to help out with this issue. I’ve checked the current codebase/documentation and know exactly what needs to be updated to make this clearer. I will ensure everything aligns perfectly with your existing contribution guidelines.

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

  5. abayomiwav commented on Jun 27, 2026

    @abayomiwav
    abayomiwav
    on Jun 27, 2026 – with Drips Wave
    Contributor

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

    please assign me this issue

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

  6. Gbangbolaoluwagbemiga
    assigned
    abayomiwav
    on Jun 27, 2026

  7. drips-wave commented on Jun 27, 2026

    @drips-wave
    drips-wavebot
    on Jun 27, 2026 – with Drips Wave

    Congratulations, @abayomiwav! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

    🧑‍💻 @abayomiwav: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  8. Gbangbolaoluwagbemiga
    added a commit that references this issue on Jun 28, 2026

    feat(core): add tests, benchmarks, and fixes for S004/S005/S007/S008

    8e7b442
  9. Gbangbolaoluwagbemiga
    closed this as completedin #1064on Jun 28, 2026

  10. drips-wave commented on Jun 28, 2026

    @drips-wave
    drips-wavebot
    on Jun 28, 2026 – with Drips Wave

    This issue has been completed by @abayomiwav as part of the Stellar Wave Program's 6th Wave 🥳

    😎 @abayomiwav: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

  11. Gbangbolaoluwagbemiga
    added 3 commits that reference this issue on Jul 19, 2026

    feat(core): add tests, benchmarks, and fixes for S004/S005/S007/S008

    fcdafa0

    feat(core): add tests, benchmarks, and fixes for S004/S005/S007/S008

    9177ec8

    feat(core): add tests, benchmarks, and fixes for S004/S005/S007/S008

    f52131c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programcomponent:coretooling/sanctifier-core (analysis engine)difficulty:mediumModerate changepriority:p2Medium prioritystatus:readyClear spec, ready for implementationtype:testingTest coverage, harnesses, fuzzing, QA

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions