GH CLI for large Classroom Assignment 500 Server Error
- Lenguaje dominante
- Go
- Estrellas
- 125
- Forks
- 21
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hello,
I have previously raised a ticket with GitHub support: [Ticket 2847591](https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.github.com%2Fticket%2F2847591&data=05%7C02%7Ctimothy.wiley%40rmit.edu.au%7C92c9a0755af548935c6008dc90b33cc3%7Cd1323671cdbe4417b4d4bdb24b51316b%7C0%7C0%7C638544346714872878%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=tMAZqFkFZn8H8kgw3U%2Fi3n0jhFUeTXB9XTRXUIbHgdg%3D&reserved=0) who suggested I raise an issue here.
We are encountering an issue trying to use the GH Classroom CLI when trying to download repositories for a very large classroom and assignment. This issue appears similar to the following previous issues:
* https://github.com/orgs/community/discussions/67264
* https://github.com/github/gh-classroom/issues/38
The classroom we have has 1000 listed students, with 420 teams, and 335 currently "submitted" assignments. When attempting to access the repositories on the CLI tool gh classroom clone student-repos -a --page 1 --per-page 1 the resulting error occurs:
HTTP 500: Server Error (https://api.github.com/assignments/_no_/accepted_assignments?page=2&per_page=1)
Changing the page number and per-page value does not resolve the error.
We are able to access other smaller classrooms, so this appears to be an issue on the larger classroom.
For reference I am using the following versions:
* gh version 2.50.0 (2024-05-30)
* gh classroom github/gh-classroom v0.1.13
Assistance in this matter would be greatly appreciated.
Guía de contribución
Línea de trabajo
Comienza reproduciendo `gh classroom clone student-repos -a --page 1 --per-page 1` contra un classroom grande e inspecciona la solicitud fallida a la API de `accepted_assignments`. Compárala con un classroom más pequeño y revisa los issues anteriores vinculados y la discusión; se considerará terminado cuando se pueda acceder a la assignment grande sin el HTTP 500 o se haya identificado claramente la limitación.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github, go
- Área
- api, cli
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 32/100