Skip to content

Conversation

@bolekk
Copy link
Contributor

@bolekk bolekk commented Aug 26, 2025

Launcher per-method shims and CombinedClient.

CombinedClient unit tests generated with Claude.

@bolekk bolekk force-pushed the feature/PRODCRE-792-remote-shims-for-v2-caps branch 2 times, most recently from bb70143 to aaa59f7 Compare August 27, 2025 04:40
@bolekk bolekk force-pushed the feature/PRODCRE-792-remote-shims-for-v2-caps branch 6 times, most recently from 89c0710 to ca7a685 Compare August 28, 2025 04:48
@bolekk bolekk force-pushed the feature/PRODCRE-792-remote-shims-for-v2-caps branch 3 times, most recently from cc59a85 to b5609e0 Compare September 4, 2025 03:01
@bolekk bolekk changed the title [DRAFT][PRODCRE-792] Support capabilities that are both Triggers and Executables [PRODCRE-792] Support capabilities that are both Triggers and Executables Sep 4, 2025

methodConfig := capabilityConfig.CapabilityMethodConfig
if methodConfig != nil { // v2 capability
w.exposeCapabilityV2(ctx, cid, methodConfig, myPeerID, don, idsToDONs)
Copy link
Contributor

Choose a reason for hiding this comment

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

also, shouldn't you check capability.CapabilityType==nil to make sure people not use both types of parametrizations at the same time?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This type doesn't matter here any more. exposeCapabilityV2() goes method-by-method

return nil
}

func (w *launcher) exposeCapabilityV2(ctx context.Context, capID string, methodConfig map[string]capabilities.CapabilityMethodConfig, myPeerID p2ptypes.PeerID, myDON registrysyncer.DON, idsToDONs map[uint32]capabilities.DON) error {
Copy link
Contributor

Choose a reason for hiding this comment

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

@george-dorin uncovered a very hairy bug (ticket pending...) where it seem like if the loop crashes the in-memory registry is corrupted and never recovers despite a new loop process starting.

how does this code get alerted/triggered by, say, a looop restart?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It doesn't. And it didn't even before this change :( I opened a separate epic to handle dynamic updates to underlying capabilities and config, which should include LOOPP restarts (CRE-788)

@bolekk bolekk force-pushed the feature/PRODCRE-792-remote-shims-for-v2-caps branch 7 times, most recently from 30d2f55 to a6bea65 Compare September 8, 2025 05:03
@bolekk bolekk force-pushed the feature/PRODCRE-792-remote-shims-for-v2-caps branch from a6bea65 to 7c7cebc Compare September 8, 2025 05:33
@bolekk bolekk marked this pull request as ready for review September 8, 2025 05:36
@bolekk bolekk requested review from a team as code owners September 8, 2025 05:36
@bolekk bolekk requested review from a team as code owners September 8, 2025 05:36
@cl-sonarqube-production
Copy link

@bolekk bolekk added this pull request to the merge queue Sep 8, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Sep 8, 2025
@bolekk bolekk added this pull request to the merge queue Sep 8, 2025
github-merge-queue bot pushed a commit that referenced this pull request Sep 8, 2025
…bles (#19102)

[DRAFT][PRODCRE-792] Support capabilities that are both Triggers and Executables
Merged via the queue into develop with commit 6684594 Sep 8, 2025
155 checks passed
@bolekk bolekk deleted the feature/PRODCRE-792-remote-shims-for-v2-caps branch September 8, 2025 13:55
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.

5 participants