chore: update .NET dependencies - #1
Merged
Merged
Conversation
guillaume-chervet
force-pushed
the
chore/update-dependencies-2026-09
branch
2 times, most recently
from
September 4, 2026 08:18
4138b7c to
caba108
Compare
Signed-off-by: Guillaume Chervet <guillaume.chervet@gmail.com>
guillaume-chervet
force-pushed
the
chore/update-dependencies-2026-09
branch
from
September 4, 2026 08:24
caba108 to
a57c734
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Résumé
dotnet testvers Microsoft.Testing.Platform et adapte les commandes CI/documentéesMultiRaftNode.DisposeAsyncidempotent lorsque les alias DI libèrent le même nœud, avec un test de régressionglobal.jsonet rend les publications fail-fastLe dépôt ne contient aucun manifeste npm, yarn ou pnpm : les scripts Studio sont du code propriétaire sans bibliothèque JavaScript externe. Leur syntaxe et leur intégration HTTP/MessagePack ont été validées.
Validation
dotnet format SlimVector.slnx --verify-no-changes --no-restoredotnet build SlimVector.slnx -c Release --no-restore: 0 avertissementdotnet test --solution SlimVector.slnx -c Release --no-restore --no-build: 141/141dotnet build SlimVector.slnx --no-restore: 0 avertissementdotnet test --solution SlimVector.slnx --no-restore --no-build: 141/141node --checksurapp.jsetmsgpack.jsgit diff --checkBenchmark
Commande identique avant/après, en Release, corpus synthétique temporaire :
dotnet run -c Release --project benchmarks/SlimVector.Benchmarks -- --e2e --profile Smoke --indexes Flat-Float32,Hnsw --repetitions 5 --warmups 1 --operation-count 512 --baseline benchmark-results.json --fail-on-regressionRésultat : références compatibles, aucune régression significative, zéro erreur. La comparaison des dépendances donnait notamment les débits médians avant → après suivants : Flat 3062.46 → 2976.77 éléments/s (-2.80 %), HNSW ef256 3950.85 → 3933.14 (-0.45 %), Raft 168.55 → 189.11 (+12.19 %), serveur Flat bufferisé 204.59 → 204.49 (-0.05 %). Le correctif Raft a ensuite été comparé séparément au commit précédent avec le même protocole et ne présente aucune régression significative. Les résultats temporaires ont été supprimés après examen.