Skip to content

Conversation

@mpetrun5
Copy link
Collaborator

@mpetrun5 mpetrun5 commented Oct 6, 2025

Description

Related Issue Or Context

Closes: #52

How Has This Been Tested? Testing details.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation

Checklist:

  • I have commented my code, particularly in hard-to-understand areas.
  • I have ensured that all acceptance criteria (or expected behavior) from issue are met
  • I have updated the documentation locally and in docs.
  • I have added tests to cover my changes.
  • I have ensured that all the checks are passing and green, I've signed the CLA bot

@github-actions
Copy link

github-actions bot commented Oct 6, 2025

Go Test coverage is 54.9 %\ ✨ ✨ ✨

return nil, err
}

err = h.coordinator.Execute(context.Background(), []tss.TssProcess{signing}, data.SigChn, data.Coordinator)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why doesn't handleMessage func take context?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code of message handlers is old.
I would have to change it in the core library and in all the other handlers.

@mpetrunic mpetrunic merged commit a3bf182 into main Oct 8, 2025
7 of 8 checks passed
@mpetrunic mpetrunic deleted the feat/unlock-api branch October 8, 2025 09:21
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.

Unlock API

4 participants