-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Github Enterprise License API fails when parsing temp license #2903
Labels
Status: Up for grabs
Issues that are ready to be worked on by anyone
Type: Bug
Something isn't working as documented
Comments
AlexanderBrehm-hps
added
Status: Triage
This is being looked at and prioritized
Type: Bug
Something isn't working as documented
labels
Apr 10, 2024
Here's the stack trace as well
|
kfcampbell
added
Status: Up for grabs
Issues that are ready to be worked on by anyone
and removed
Status: Triage
This is being looked at and prioritized
labels
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Status: Up for grabs
Issues that are ready to be worked on by anyone
Type: Bug
Something isn't working as documented
What happened?
Hey Team,
I'm getitng this error when attempting to use the Enterprise.License.Get() method in OcktoKit
This seems to be because my license is currently a temp one given out by Github/Microsoft with both "unlimited" seats and seats_available
I suspect this is then causing the license info class to have issues when attempting to parse the seats and seats_available properties, since those are both strings in my current license as opposed to being the INTs requested by the LicenseInfo object
I ended up hacking around it to prove it.
I'm not sure if this actually needs to be fixed because most people won't have the evaluation license, but I did want to bring it to your all's attention as it could cause issues for other people and you might want to consider making an update to your code.
Versions
Github Enterprise 3.11.5
Octokit v 10.0.0
Relevant log output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: