Closed johnfelipe closed 3 weeks ago
@johnfelipe which branch is this on?
It's working for me on the v2-dev
branch as of now.
Thanks @johnfelipe I found the issue (not present in Big-AGI 2, but was still present in 1) - fixed, sorry for the downtime (Google changed the protocol). I'm confident you'll love the Gemini support in Big-AGI 2.
Can you share me steps for update to V2 in ver El I fork you repo and when sync all is automatic How can upgrade to V2 pls
Para cambiar la rama (branch) de un fork y sincronizarlo con la rama v2-dev del repositorio original, puedes seguir estos pasos:
# Añadir el repositorio original como remote si aún no lo has hecho
git remote add upstream https://github.com/enricoros/big-AGI.git
git fetch upstream
git checkout -b v2-dev
git reset --hard upstream/v2-dev
git push -f origin v2-dev
2. Desde la interfaz web de GitHub:
- Ve a tu fork en GitHub
- Haz clic en el menĂş desplegable de ramas (donde dice "main" o "master")
- Selecciona o crea la rama "v2-dev"
- Ve a "Settings" de tu repositorio
- En la sección "General", desplázate hasta "Default branch"
- Cambia la rama predeterminada a "v2-dev"
- Confirma el cambio
3. Para mantener el fork sincronizado en el futuro:
```bash
git fetch upstream
git checkout v2-dev
git merge upstream/v2-dev
git push origin v2-dev
Si estás usando Vercel:
Ten en cuenta que la rama v2-dev es la rama de desarrollo para Big-AGI 2, que según el README se lanzará en Q4 2024 y puede contener cambios experimentales o inestables.
^ si
Description
[Stream Issue] Gemini: [ { "code": "invalid_type", "expected": "number", "received": "undefined", "path": [ "candidates", 0, "index" ], "message": "Required" } ]
Device and browser
windows 10 chrome latest version
Screenshots and more
No response
Willingness to Contribute