Bump condenser defaults: max_size 120->240#12267
Conversation
|
|
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||
|
Looks like there are a few issues preventing this PR from being merged!
If you'd like me to help, just leave a comment, like Feel free to include any additional details that might help me get this PR into a better state. You can manage your notification settings |
|
Feature deployment is available at: https://ohpr-12267.staging.all-hands.dev |
|
@OpenHands please check datadog API for logs - looks like the DB migration didn't work for https://ohpr-12267.staging.all-hands.dev/ I still see 120 max history size in the UI, any idea? |
|
I'm on it! xingyaoww can track my progress at all-hands.dev |
SummaryI investigated the issue using the Datadog API and found the root cause of why you're still seeing 120 in the UI despite the migration running. Root Cause AnalysisFrom the Datadog logs, I confirmed that:
So users with Fix AppliedI pushed a commit that:
Next StepsOnce the staging deployment redeploys with this fix, the migration will:
And new users will get 240 as the default instead of 120. The changes have been pushed to the |
|
Feature deployment is available at: https://ohpr-12267.staging.all-hands.dev |
|
@OpenHands please fix these - we should set default value to 240 in FE and backend as well including the test The application code defaults NULL to 120 in both frontend (DEFAULT_SETTINGS.condenser_max_size: 120) and backend (settings.condenser_max_size or 120) |
|
I'm on it! xingyaoww can track my progress at all-hands.dev |
- Add migration 086 to update existing users with condenser_max_size=120 to 240 - Add new condenser_keep_first column to user_settings table - Set condenser_keep_first=4 for existing users who have condenser settings - Update Settings model with condenser_keep_first field and validator - Update _create_condenser to accept and use condenser_keep_first parameter - Fix outdated comment about SDK defaults (was 120/4, now 240/2) Co-authored-by: openhands <openhands@all-hands.dev>
…or keep_first Remove condenser_keep_first column and related code since the SDK default will be used automatically when the column is not present. Co-authored-by: openhands <openhands@all-hands.dev>
The migration was only updating rows where condenser_max_size=120, but most users have NULL in the database (which defaulted to 120 in application code). Changes: - Migration now updates both condenser_max_size=120 AND NULL values to 240 - Updated frontend default from 120 to 240 - Updated backend default from 120 to 240 (V0 session.py) - Updated test comments to reflect correct SDK defaults (240/2) Co-authored-by: openhands <openhands@all-hands.dev>
89ead3f to
82e221e
Compare
|
I've fixed the failing GitHub Action by rebasing the Issue: The Fix: Rebased the PR branch on top of
The PR should now pass the |
|
Feature deployment is available at: https://ohpr-12267.staging.all-hands.dev |
|
@OpenHands check datadog, i got these error when i open the deployment: 400 Bad Request |
|
I'm on it! xingyaoww can track my progress at all-hands.dev |
|
Feature deployment is available at: https://ohpr-12267.staging.all-hands.dev |
SummaryI investigated the "400 Bad Request - Request Header Or Cookie Too Large" error you're experiencing when opening the deployment at https://ohpr-12267.staging.all-hands.dev using the Datadog API. Findings
Root CauseThe "Request Header Or Cookie Too Large" error is a client-side browser issue, not a code problem. It happens when:
SolutionTo fix this immediately:
This is not a bug in the PR code - it's a common issue when testing multiple staging deployments that share a parent domain. No code changes are needed. |
|
OK! Confirmed this is fixed. #12267 (comment) -> this issue is just a blip
|

Description
This PR updates the condenser defaults for existing users to address the staling issue in V1 conversations.
Changes
Database Migration (086):
condenser_max_size=120to240condenser_keep_firstcolumn touser_settingstablecondenser_keep_first=4for existing users who have condenser settingsModel Updates:
condenser_keep_firstfield toSettingsdata modelcondenser_keep_first(must be non-negative)condenser_keep_firstcolumn to enterpriseUserSettingstableCode Updates:
_create_condensermethod to accept and usecondenser_keep_firstparameter_create_agent_with_contextto passcondenser_keep_firstfrom user settingsBackground
The SDK has defaults of
max_size=240andkeep_first=2, but existing users who had the old default ofmax_size=120stored in the database were not benefiting from the increased default. This migration updates those users to the new values and adds support for customizingkeep_first.Testing
Related Issues
Addresses staling issues in V1 conversations by increasing the condenser history size.
@xingyaoww can click here to continue refining the PR
To run this PR locally, use the following command:
GUI with Docker: