Channel update from new sushichef script changes/run is not able to be deployed
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- javascript, python
- Área
- backend-api-design, frontend
Línea de trabajo
Start at the channel’s staging page and use the linked video to reproduce the deployment spinner; inspect the browser’s network activity as the issue suggests. The issue names no source files or tests, so first trace the deployment flow from that page. Done means the channel publishes successfully or the user receives an actionable error instead of an indefinite spinner.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Target branch: current Production
Observed behavior
I have a channel I have already uploaded with an older version of my sushichef script that I was able to successfully deploy and submit fore review. I noticed some missing sections that my script was not handling correctly and uploaded a new version. I am not able to deploy that new version.
Errors and logs
Browser console logs, but I don''t think these are relevant, just including for completeness
Node cannot be found in the current page.
console.ts:39 [Vuetify] 'default slot' is deprecated, use ':items and scoped slot "item"' instead
found in
---> <VBreadcrumbs>
<Breadcrumbs>
<VToolbar>
<ToolBar>
<VContent>
<StagingTreePage>
<VApp>
<Root>
console.ts:39 [Vuetify] 'default slot' is deprecated, use ':items and scoped slot "item"' instead
found in
---> <VBreadcrumbs>
<Breadcrumbs>
<VToolbar>
<CurrentTopicView>
<VContent>
<TreeViewBase>
<TreeView>
<VApp>
<Root>
console.ts:39 [Vuetify] 'default slot' is deprecated, use ':items and scoped slot "item"' instead
found in
---> <VBreadcrumbs>
<Breadcrumbs>
<VToolbar>
<ToolBar>
<VContent>
<StagingTreePage>
<VApp>
<Root>
console.ts:39 [Vuetify] 'default slot' is deprecated, use ':items and scoped slot "item"' instead
found in
---> <VBreadcrumbs>
<Breadcrumbs>
<VToolbar>
<CurrentTopicView>
<VContent>
<TreeViewBase>
<TreeView>
<VApp>
<Root>
console.ts:39 [Vuetify] 'default slot' is deprecated, use ':items and scoped slot "item"' instead
found in
---> <VBreadcrumbs>
<Breadcrumbs>
<VToolbar>
<ToolBar>
<VContent>
<StagingTreePage>
<VApp>
<Root>
Expected behavior
Channel should publish or give an error message, currently I just see a spinner and no new/pending network requests in the browser devtools.
User-facing consequences
Confusion for content authors/importers.
Steps to reproduce
My channel I'm trying to publish - (https://studio.learningequality.org/en/channels/78bc12f14f6a51938bbce44ca590e012/#/staging/3481613e7a814326941176a9e3e1c07c)
Video repro
https://github.com/user-attachments/assets/6d75bb91-e5f4-4da7-b849-786c9bc6f42e
Context
Chrome on Linux - Version 151.0.7922.71
AI usage
No AI was used in writing this issue, I did use some for looking up snippets and help while developing my sushichef script, but I wrote the bulk of the code for it.
- Lenguaje dominante
- Python
- Estrellas
- 192
- Forks
- 310
- Merge medio
- 2 d 13 h
- PR fusionados (30 d)
- 67
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de learningequality/studio
-
Set unpublishable: true on PublishedChange by construction to simplify handleMaxRevs predicateAbiertoDEV: frontend P3 - low
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
learningequality/studio#5868 ·
Los mantenedores suelen responder en 1 día
-
TAG: tech update / debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
learningequality/studio#2245 ·
Los mantenedores suelen responder en 1 día
-
bug DEV: frontend P0 - critical
Dificultad 3/5 1-2 días Aptitud para principiantes 22/100
learningequality/studio#6316 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 1-2 días Aptitud para principiantes 35/100
learningequality/studio#6315 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 4/5 1-2 días Aptitud para principiantes 25/100
learningequality/studio#6314 ·
Los mantenedores suelen responder en 1 día
Todos los issues de learningequality/studio
Issues similares
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
jbacalso24/mimry#291 ·
Los mantenedores suelen responder en 1 día
-
good first issue
Dificultad 2/5 Menos de una hora Aptitud para principiantes 82/100
eli-alvarado/us-watchlist-alerts#14 ·
Los mantenedores suelen responder en 1 día
-
from-review-extraction python severity:nit
Dificultad 2/5 1-3 horas Aptitud para principiantes 80/100
LearningCircuit/local-deep-research#7462 ·
Los mantenedores suelen responder en 2 días
-
mermaid_extract.py silently discards single-line state-diagram notes; sequence notes are keptAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
cathrynlavery/diagram-design#441 ·
Los mantenedores suelen responder en 2 días
-
[Cleanup] Include the public header in work_split.cppPosiblemente ocupada @blozano-tt la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
tenstorrent/tt-metal#60850 ·
Los mantenedores suelen responder en 1 día