[Feature]: To be able to specify a user login for github api calls

Open
#4,855 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
shell
Domain
api, cli

Research direction

Start with the mods-update command and trace the GitHub API calls that lead to the reported jq null error. Review the linked GitHub rate-limit documentation and define how a configurable user login would be supplied and how exhausted limits should be reported; done means authenticated calls work for this command and failures identify the rate-limit cause.

Written by the indexing model from the issue text.

Description

command: mods engine: unity3d game: Rust type: feature
User story

With more than about 3 servers on 1 IP, the anonymous api calls is ratelimited to 60 per hour

Game

Rust

Linux distro

Other

Command

command: mods-update

Further information

I run 9 servers in total and the ratelimit is killing me during server wipes and updates. Each time mods-update is run, it performs about 11 api calls. This would allow at most 5 servers on the same IP before ratelimiting starts to interfere. If I could specify a user for the api calls to use (I'd be happy to specify my own) then the ratelimit goes up to 5,000 which is more than enough.

The error you see when you have exhausted your limit is

jq: error (at :1): Cannot iterate over null (null)
jq: error (at :1): Cannot iterate over null (null)

which doesn't really indicate what the real reason for the failure is.

I briefly looked through the scripts and it doesn't look like this feature currently exists.

Github rate limits are described here

https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28

Dominant language
Shell
Stars
4.9k
Forks
866
Avg merge
17h 58m
Merged PRs (30d)
100

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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 GameServerManagers/LinuxGSM

All issues in GameServerManagers/LinuxGSM

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.