Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Dropped resource-updated notifications are never logged

Open Beginner friendly
#1,082 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@leeshengis is already working on this.

Since Oct 7, 2026.

  • #1102 by @leeshengis — open

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
86/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
kotlin
Domain
backend

Research direction

Start at the FeatureNotificationService entry point and inspect the fallback used when a resource-updated notification has no subscription. Change the fallback as specified, then run the relevant notification tests and verify that the "No subscription for resource … Skipping notification" message is logged.

Written by the indexing model from the issue text.

Description

bug P3

In FeatureNotificationService, the fallback ?: { logger.info { … } } evaluates to a lambda that is never invoked. A resource-updated notification without a subscription is therefore dropped without the intended "No subscription for resource … Skipping notification" log line.

Expected: use ?: run { … }.

Dominant language
Kotlin
Stars
1.5k
Forks
262
Avg merge
2d 14h
Merged PRs (30d)
46

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/kotlin-sdk

All issues in modelcontextprotocol/kotlin-sdk

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.