Fix tests for notifications (#446)
<!-- Provide a brief summary of your changes --> ## Motivation and Context <!-- Why is this change needed? What problem does it solve? --> ## How Has This Been Tested? <!-- Have you tested this in a real application? Which scenarios were tested? --> ## Breaking Changes <!-- Will users need to update their code or configurations? --> ## Types of changes <!-- What types of changes does your code introduce? Put an `x` in all the boxes that apply: --> - [x] 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 update ## Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. --> - [ ] I have read the [MCP Documentation](https://modelcontextprotocol.io) - [ ] My code follows the repository's style guidelines - [ ] New and existing tests pass locally - [ ] I have added appropriate error handling - [ ] I have added or updated documentation as needed ## Additional context <!-- Add any other context, implementation notes, or design decisions -->
This commit is contained in:
parent
1744e16d86
commit
274089a6da
1 changed files with 43 additions and 46 deletions
|
|
@ -348,7 +348,7 @@ internal class FeatureNotificationService(
|
|||
job.start()
|
||||
}
|
||||
|
||||
/** Returns the current timestamp in milliseconds. */
|
||||
/** Returns the current timestamp in milliseconds since Unix epoch. */
|
||||
@OptIn(ExperimentalTime::class)
|
||||
private fun getCurrentTimestamp(): Long = clock.now().toEpochMilliseconds()
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue