You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This can happen when the IP address where the user is runnign neil from an IP address that has exceeded the GH json api rate limit, which for most people using the tool will be 60 req per hour.
When this happens, it is not obvious to the user why neil fails.
To reproduce
Check out neil
run the neil test suite at least twice, it will fail the scond time
bb tests
# and again
bb tests
(a user can check their usage by running curl -I https://api.github.com/users/<gh user name>)
I understand this is a known limitation, but I could not find anything mentioned in neil's documentation about it or elsewhere.
I can think of the following options to solve this issue
Explain in the documentation/neil usage output that this can happen while improving on error messages when this happens.
as before, but also allow users to set their pershonal GH token with neil (personal tokens permit thousands of calls per hour), e.g. using an env variable where the user can set their token at and picked up by neil.
Investigate alternatives ways to retrieve info from GH.
thanks
The text was updated successfully, but these errors were encountered:
Hi,
I've noticed that GH throws a NullPointer exception for some of its operations which call on the GH json API (e.g. querying about licences).
This can happen when the IP address where the user is runnign neil from an IP address that has exceeded the GH json api rate limit, which for most people using the tool will be 60 req per hour.
When this happens, it is not obvious to the user why neil fails.
To reproduce
neil
bb tests # and again bb tests
(a user can check their usage by running
curl -I https://api.github.com/users/<gh user name>
)I understand this is a known limitation, but I could not find anything mentioned in neil's documentation about it or elsewhere.
I can think of the following options to solve this issue
thanks
The text was updated successfully, but these errors were encountered: