We’ve just released TimeoutMigrationTool 1.0.1
- #112 Preview command miscalculated total number of timeouts per endpoint for RavenDB
- #114 Preview command miscalculated shortest and longest timeout for RavenDB
How to know if you are affected
Everyone using the preview command with the RavenDB-persistence, only when that same storage is shared across multiple endpoints.
The total number of timeouts per endpoint listed when running the preview command incorrectly shows the total number of timeouts detected in the storage.
The shortest and longest timeout listed per endpoint when running the preview command did not take into account the endpoint.
This data was erroneous only when the same storage was shared across multiple endpoints.
Should you upgrade immediately
There is no urgency to upgrade as the migration process respects the endpoint being migrated, it’s only a presentation issue when running the
Where to get it
You can install the tool from NuGet using:
dotnet tool install Particular.TimeoutMigration -g
The team in Particular