Skip to content

Fix stale /status rate limits in active TUI sessions#16201

Merged
etraut-openai merged 10 commits intomainfrom
etraut/status-rate-limit-update
Mar 31, 2026
Merged

Fix stale /status rate limits in active TUI sessions#16201
etraut-openai merged 10 commits intomainfrom
etraut/status-rate-limit-update

Conversation

@etraut-openai
Copy link
Copy Markdown
Collaborator

@etraut-openai etraut-openai commented Mar 29, 2026

Fix stale weekly limit in /status (#16194): /status reused the session’s cached rate-limit snapshot, so the weekly remaining limit could stay frozen within an active session.

With this change, we now dynamically update the rate limits after status is displayed.

I needed to delete a few low-value test cases from the chatWidget tests because the test.rs file is really large, and the new tests in this PR pushed us over the 512K mandated limit. I'm working on a separate PR to refactor that test file.

@fcoury
Copy link
Copy Markdown
Contributor

fcoury commented Mar 31, 2026

@etraut-openai the code looks good, but since I am physically far away from the server this is running on, there is a very noticeable lag between when I type /status and the result appearing, to a point where I thought it was not going to work. It's not a huge wait, don't get me wrong - but noticeable.

I know we want to make things as simple as possible but I wonder if we should have a message displayed instantly that indicates we are loading the status and then maybe delete it before showing the actual status?

@etraut-openai etraut-openai force-pushed the etraut/status-rate-limit-update branch from 36aea03 to 7d59d6f Compare March 31, 2026 18:13
@etraut-openai etraut-openai force-pushed the etraut/status-rate-limit-update branch from 7d59d6f to 0d00050 Compare March 31, 2026 18:15
Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0d00050fae

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copy link
Copy Markdown
Contributor

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a8330ac889

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@etraut-openai
Copy link
Copy Markdown
Collaborator Author

@fcoury, thanks for the review. That's a good point. I've asked codex to update the implementation as you suggested. I'd appreciate it if you could retry the new version and let me know if it feels better for you.

@fcoury
Copy link
Copy Markdown
Contributor

fcoury commented Mar 31, 2026

@etraut-openai it is instant now!

@etraut-openai etraut-openai merged commit ae057e0 into main Mar 31, 2026
22 checks passed
@etraut-openai etraut-openai deleted the etraut/status-rate-limit-update branch March 31, 2026 23:03
@github-actions github-actions bot locked and limited conversation to collaborators Mar 31, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants