-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat: add Deepseek v3.1 to Fireworks AI provider #7375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,6 +6,7 @@ export type FireworksModelId = | |
| | "accounts/fireworks/models/qwen3-coder-480b-a35b-instruct" | ||
| | "accounts/fireworks/models/deepseek-r1-0528" | ||
| | "accounts/fireworks/models/deepseek-v3" | ||
| | "accounts/fireworks/models/deepseek-v3p1" | ||
| | "accounts/fireworks/models/glm-4p5" | ||
| | "accounts/fireworks/models/glm-4p5-air" | ||
| | "accounts/fireworks/models/gpt-oss-20b" | ||
|
|
@@ -62,6 +63,16 @@ export const fireworksModels = { | |
| description: | ||
| "A strong Mixture-of-Experts (MoE) language model with 671B total parameters with 37B activated for each token from Deepseek. Note that fine-tuning for this model is only available through contacting fireworks at https://fireworks.ai/company/contact-us.", | ||
| }, | ||
| "accounts/fireworks/models/deepseek-v3p1": { | ||
| maxTokens: 16384, | ||
| contextWindow: 163840, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 0.56, | ||
| outputPrice: 1.68, | ||
| description: | ||
| "DeepSeek v3.1 is an improved version of the v3 model with enhanced performance, better reasoning capabilities, and improved code generation. This Mixture-of-Experts (MoE) model maintains the same 671B total parameters with 37B activated per token.", | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Could we add a reference to official Fireworks or DeepSeek documentation about v3.1 to verify these specifications? This would help future maintainers understand where these values come from. |
||
| }, | ||
| "accounts/fireworks/models/glm-4p5": { | ||
| maxTokens: 16384, | ||
| contextWindow: 128000, | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -179,6 +179,27 @@ describe("FireworksHandler", () => { | |
| ) | ||
| }) | ||
|
|
||
| it("should return DeepSeek V3.1 model with correct configuration", () => { | ||
| const testModelId: FireworksModelId = "accounts/fireworks/models/deepseek-v3p1" | ||
| const handlerWithModel = new FireworksHandler({ | ||
| apiModelId: testModelId, | ||
| fireworksApiKey: "test-fireworks-api-key", | ||
| }) | ||
| const model = handlerWithModel.getModel() | ||
| expect(model.id).toBe(testModelId) | ||
| expect(model.info).toEqual( | ||
| expect.objectContaining({ | ||
| maxTokens: 16384, | ||
| contextWindow: 163840, | ||
| supportsImages: false, | ||
| supportsPromptCache: false, | ||
| inputPrice: 0.56, | ||
| outputPrice: 1.68, | ||
| description: expect.stringContaining("DeepSeek v3.1 is an improved version"), | ||
| }), | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good test coverage for the configuration! Consider also adding a test that verifies the model can be properly instantiated and used in the FireworksHandler's method, similar to the existing tests for other models. This would ensure end-to-end functionality. |
||
| ) | ||
| }) | ||
|
|
||
| it("should return GLM-4.5 model with correct configuration", () => { | ||
| const testModelId: FireworksModelId = "accounts/fireworks/models/glm-4p5" | ||
| const handlerWithModel = new FireworksHandler({ | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the intended naming convention here? I notice other model IDs in the codebase use hyphens for versioning (like ). Would be more consistent with the existing pattern, or is there a specific reason to avoid dots that also applies to hyphens?