-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
Add runtime size configuration feature #5805
base: main
Are you sure you want to change the base?
Conversation
- Keep runtime size configuration feature - Update settings to use API instead of localStorage - Update tests to work with API-based settings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me now, @amanape it'd be great if you could do a second review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the backend already set to recognize these new setting keys?
@amanape : yes it is
UPDATE: but now that I think about it, I didn't carefully check the backend code that receives the changes from the frontend, I will check that. |
Should be OK now but I want to run locally to see that it works. |
This PR adds a new feature to configure the runtime size in the settings modal. Users can now choose between 1x (2 core, 8G) and 2x (4 core, 16G) options.
Changes include:
REMOTE_RUNTIME_RESOURCE_FACTOR
field to theSettings
typeRuntimeSizeSelector
componentSettingsForm
component to include the new selectorgetSettings
andsaveSettings
functions to handle the new settingPlease review and let me know if any changes are needed.
Notes:
To run this PR locally, use the following command: