Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Subjective CPU billing using uint32_t #123

Closed
heifner opened this issue Sep 8, 2022 · 0 comments · Fixed by #125
Closed

Subjective CPU billing using uint32_t #123

heifner opened this issue Sep 8, 2022 · 0 comments · Fixed by #125
Assignees
@heifner
Labels
OCI Work exclusive to OCI team
Milestone
Leap 3.1.1

Comments

@heifner
Copy link
Member

heifner commented Sep 8, 2022

Objective CPU billing uses an int64_t. uint32_t is limited to 4294967295. It would be beneficial for these types to be the same.
Switch subjective CPU billing to use int64_t.
@heifner heifner moved this to Todo in Team Backlog Sep 8, 2022
@heifner heifner self-assigned this Sep 8, 2022
@heifner heifner added the OCI Work exclusive to OCI team label Sep 8, 2022
@heifner heifner modified the milestones: Leap 3.2.0-rc1, Leap 3.1.1 Sep 8, 2022
This was referenced Sep 8, 2022
Merged
Merged
Repository owner moved this from Todo to Done in Team Backlog Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@heifner heifner

Labels
OCI Work exclusive to OCI team
Projects
Team Backlog
Archived in project
Milestone
Leap 3.1.1
Development

Successfully merging a pull request may close this issue.

[3.1 -> main] Allow for larger subjective CPU billing amounts AntelopeIO/leap
1 participant
@heifner