Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

GH CLI for large Classroom Assignment 500 Server Error

Open
#72 23 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
32/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, go
Domain
api, cli

Research direction

Start by reproducing gh classroom clone student-repos -a <no> --page 1 --per-page 1 against a large classroom and inspect the failing accepted_assignments API request. Compare it with a smaller classroom and review the linked prior issues and discussion; done should mean the large assignment can be accessed without the HTTP 500 or the limitation is clearly identified.

Written by the indexing model from the issue text.

Description

Hello,

I have previously raised a ticket with GitHub support: Ticket 2847591 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:

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.

Dominant language
Go
Stars
126
Forks
21
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/gh-classroom

All issues in github/gh-classroom

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.