Issue Station
Sign In
Tools hereToolbox

litellm - ✅(Solved) Fix [Feature]: GigaChat UI Dashboard support [4 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#23262•Fetched 2026-04-08 00:37:55
View on GitHub
Comments
0
Participants
1
Timeline
6
Reactions
0
Author
klankerrklankerr
Participants
klankerrklankerr
Timeline (top)
cross-referenced ×4labeled ×2

Fix Action

Fixed

PR fix notes

PR #23263: Feature/gigachat-UI-dashboard

Description (problem / solution / changelog)

Relevant issues

<!-- e.g. "Fixes #000" -->

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.

  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

<!-- Select the type of Pull Request --> <!-- Keep only the necessary ones -->

🆕 New Feature 🧹 Refactoring

Changes

Changed files

  • litellm/llms/gigachat/authenticator.py (modified, +3/-2)
  • litellm/llms/gigachat/chat/transformation.py (modified, +15/-1)
  • litellm/llms/gigachat/embedding/transformation.py (modified, +15/-2)
  • litellm/llms/gigachat/file_handler.py (modified, +14/-2)
  • litellm/proxy/public_endpoints/provider_create_fields.json (modified, +52/-0)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (modified, +2/-0)

PR #23304: [Feature]: GigaChat UI Dashboard support

Description (problem / solution / changelog)

Relevant issues

<!-- e.g. "Fixes #000" -->

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.

  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

<!-- Select the type of Pull Request --> <!-- Keep only the necessary ones -->

🧹 Refactoring 📖 Documentation

Changes

Changed files

  • litellm/llms/gigachat/authenticator.py (modified, +3/-2)
  • litellm/llms/gigachat/chat/transformation.py (modified, +16/-1)
  • litellm/llms/gigachat/embedding/transformation.py (modified, +17/-2)
  • litellm/llms/gigachat/file_handler.py (modified, +14/-2)
  • litellm/proxy/public_endpoints/provider_create_fields.json (modified, +52/-0)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (modified, +2/-0)

PR #23308: Feature/gigachat UI dashboard

Description (problem / solution / changelog)

Relevant issues

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.

  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

<!-- Select the type of Pull Request --> <!-- Keep only the necessary ones -->

🆕 New Feature 🧹 Refactoring

Changes

Changed files

  • litellm/llms/gigachat/authenticator.py (modified, +3/-2)
  • litellm/llms/gigachat/chat/transformation.py (modified, +28/-1)
  • litellm/llms/gigachat/embedding/transformation.py (modified, +29/-2)
  • litellm/llms/gigachat/file_handler.py (modified, +14/-2)
  • litellm/proxy/public_endpoints/provider_create_fields.json (modified, +52/-0)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (modified, +2/-0)

PR #23310: [Feature]: GigaChat UI Dashboard support

Description (problem / solution / changelog)

Relevant issues

Solves https://github.com/BerriAI/litellm/issues/23262

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem
  • I have requested a Greptile review by commenting @greptileai and received a Confidence Score of at least 4/5 before requesting a maintainer review

CI (LiteLLM team)

CI status guideline:

  • 50-55 passing tests: main is stable with minor issues.
  • 45-49 passing tests: acceptable but needs attention
  • <= 40 passing tests: unstable; be careful with your merges and assess the risk.

  • Branch creation CI run
    Link:

  • CI run for the last commit
    Link:

  • Merge / cherry-pick CI run
    Links:

Type

<!-- Select the type of Pull Request --> <!-- Keep only the necessary ones -->

🆕 New Feature 🧹 Refactoring

Changes

Added GigaChat provider to LiteLLM UI Dashboard with relevant defaults. Refactored GigaChat access token logic.

Changed files

  • litellm/llms/gigachat/authenticator.py (modified, +3/-2)
  • litellm/llms/gigachat/chat/transformation.py (modified, +28/-1)
  • litellm/llms/gigachat/embedding/transformation.py (modified, +29/-2)
  • litellm/llms/gigachat/file_handler.py (modified, +14/-2)
  • litellm/proxy/public_endpoints/provider_create_fields.json (modified, +52/-0)
  • ui/litellm-dashboard/src/components/provider_info_helpers.tsx (modified, +2/-0)
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

The Feature

Add GigaChat as a selectable provider in the LiteLLM UI dashboard.

Motivation, pitch

This will allow users to configure and use GigaChat directly from the dashboard without manual backend setup.

What part of LiteLLM is this about?

UI Dashboard

LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

Twitter / LinkedIn details

No response

extent analysis

Fix Plan

To add GigaChat as a selectable provider in the LiteLLM UI dashboard, we need to update the backend and frontend code.

Backend Changes

  • Add a new provider option in the database or configuration file.
  • Update the API endpoint to handle GigaChat provider selection.

Example code snippet (using Python and Flask):

# providers.py
providers = [
    {"id": 1, "name": "Existing Provider"},
    {"id": 2, "name": "GigaChat"}  # Add GigaChat provider
]

# app.py
from flask import request, jsonify
from providers import providers

@app.route("/providers", methods=["GET"])
def get_providers():
    return jsonify(providers)

@app.route("/provider", methods=["POST"])
def select_provider():
    provider_id = request.json["provider_id"]
    # Handle GigaChat provider selection
    if provider_id == 2:
        # Configure GigaChat
        pass
    return jsonify({"message": "Provider selected successfully"})

Frontend Changes

  • Update the UI dashboard to display GigaChat as a selectable option.
  • Handle GigaChat selection and send a request to the backend API.

Example code snippet (using JavaScript and React):

// ProviderSelector.js
import React, { useState } from "react";
import axios from "axios";

const providers = [
  { id: 1, name: "Existing Provider" },
  { id: 2, name: "GigaChat" }, // Add GigaChat provider
];

const ProviderSelector = () => {
  const [selectedProvider, setSelectedProvider] = useState(null);

  const handleProviderSelect = (provider) => {
    setSelectedProvider(provider);
    axios.post("/provider", { provider_id: provider.id })
     .then((response) => {
        console.log(response.data);
      })
     .catch((error) => {
        console.error(error);
      });
  };

  return (
    <div>
      {providers.map((provider) => (
        <button key={provider.id} onClick={() => handleProviderSelect(provider)}>
          {provider.name}
        </button>
      ))}
    </div>
  );
};

Verification

To verify the fix, test the following scenarios:

  • The GigaChat provider is displayed in the UI dashboard.
  • Selecting GigaChat as the provider sends a request to the backend API.
  • The backend API handles GigaChat provider selection correctly.

Extra Tips

  • Ensure that the GigaChat provider is properly configured and tested before deploying the changes to production.
  • Consider adding error handling and logging to the backend API to handle any issues that may arise during provider selection.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#ssr#installation#tensor shape#autograd error#prompt formatting#chain error#conversation history#tool integration#LLM response

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

litellm - ✅(Solved) Fix [Feature]: GigaChat UI Dashboard support [4 pull requests, 1 participants]