Unable to access developer repository, Unprocessable Entity for url
Not sure if this was maybe just a network issue but got this for a new branch i created and submited, opening a new tab and doing it again worked.
Unable to access developer repository https://github.com/Disservin/Stockfish: 422 Client Error: Unprocessable Entity for url: https://api.github.com/repos/Disservin/Stockfish/commits/test-big-net)
git grep -n "Unable to access"
server/fishtest/views.py:799: raise Exception(f"Unable to access developer repository {repo_url}: {str(e)}")
server/fishtest/views.py:835: raise Exception(f"Unable to access developer repository {repo_url}: {str(e)}")
server/fishtest/views.py:950: f"Unable to access developer repository {data['tests_repo']}: {str(e)}"
server/fishtest/views.py:984: f"Unable to access developer repository {data['tests_repo']}: {str(e)}"
https://github.com/official-stockfish/fishtest/blob/e3e593961b4260f5114c915c02f8dda7ac15361b/server/fishtest/views.py#L794-L804 https://github.com/official-stockfish/fishtest/blob/e3e593961b4260f5114c915c02f8dda7ac15361b/server/fishtest/views.py#L927-L964
I don't think this code has fundamentally changed and the url https://api.github.com/repos/Disservin/Stockfish/commits/test-big-net currently works fine.
Did you quickly create the test after creating the branch? I have the impression that it sometimes takes a small amount of time for changes on a github repo to propagate.
If there are more reports like this then we can try to get a bit more information by looking at the returned body.
curl https://api.github.com/repos/Disservin/Stockfish/commits/test-big-ne
{
"message": "No commit found for SHA: test-big-ne",
"documentation_url": "https://docs.github.com/rest/commits/commits#get-a-commit",
"status": "422"
}
I don't think this code has fundamentally changed and the url https://api.github.com/repos/Disservin/Stockfish/commits/test-big-net currently works fine.
Did you quickly create the test after creating the branch? I have the impression that it sometimes takes a small amount of time for changes on a github repo to propagate.
Yeah I think maybe GitHub lagged a bit behind so might not be a fishtest issue after all