Skip to content

feat: RPC invocation listener support#24499

Open
caalador wants to merge 1 commit into
mainfrom
feat/rpc-invocation-listener
Open

feat: RPC invocation listener support#24499
caalador wants to merge 1 commit into
mainfrom
feat/rpc-invocation-listener

Conversation

@caalador
Copy link
Copy Markdown
Contributor

@caalador caalador commented Jun 2, 2026

Enable listening to RPC invocations

@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Jun 2, 2026

@github-actions github-actions Bot added the +0.1.0 label Jun 2, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 2, 2026

Test Results

 1 432 files  ±0   1 432 suites  ±0   1h 23m 8s ⏱️ - 1m 20s
10 060 tests +1   9 992 ✅ +1  68 💤 ±0  0 ❌ ±0 
10 532 runs  +1  10 463 ✅ +1  69 💤 ±0  0 ❌ ±0 

Results for commit eae0701. ± Comparison against base commit a35f9be.

Copy link
Copy Markdown
Member

@heruan heruan left a comment

Choose a reason for hiding this comment

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

Invocations of type RPC_TYPE_MAP_SYNC are not instrumented, I suppose this is intended because not meaningful in terms of request timing?

@caalador
Copy link
Copy Markdown
Contributor Author

caalador commented Jun 3, 2026

Yes. The RPC invocation listener is quite the balancing act for us to figure out to not have too much, but not have too little either.

@heruan heruan added this pull request to the merge queue Jun 3, 2026
@github-merge-queue github-merge-queue Bot removed this pull request from the merge queue due to a conflict with the base branch Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants