Properly separate deepseek keys from the generic ones in service info

This commit is contained in:
user
2025-01-25 11:06:38 +00:00
parent 45576db441
commit 6de338c6ac
+6 -4
View File
@@ -382,10 +382,6 @@ function addKeyToAggregates(k: KeyPoolKey) {
k.modelFamilies.forEach(incrementGenericFamilyStats);
// TODO: add modelIds to GcpKey
break;
// These services don't have any additional stats to track.
case "azure":
case "google-ai":
case "mistral-ai":
case "deepseek":
if (!keyIsDeepseekKey(k)) throw new Error("Invalid key type");
k.modelFamilies.forEach((f) => {
@@ -393,6 +389,12 @@ function addKeyToAggregates(k: KeyPoolKey) {
addToFamily(`${f}__overQuota`, k.isOverQuota ? 1 : 0);
});
break;
// These services don't have any additional stats to track.
case "azure":
case "google-ai":
case "mistral-ai":
k.modelFamilies.forEach(incrementGenericFamilyStats);
break;
default:
assertNever(k.service);
}