Skip to content

fix(cli): calculate coder ping max correctly #18734

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

Merged
merged 2 commits into from
Jul 3, 2025

Conversation

ethanndickson
Copy link
Member

@ethanndickson ethanndickson commented Jul 3, 2025

Embarassing mistake I made months ago 😦

*Doesn't effect schmoder, since we don't parse that max, it calculates it itself

Copy link
Member Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@ethanndickson ethanndickson marked this pull request as ready for review July 3, 2025 03:07
Comment on lines +24 to +28
LatencySeconds: 0.3,
},
{
Err: "",
LatencySeconds: 0.3,
LatencySeconds: 0.2,
Copy link
Member Author

Choose a reason for hiding this comment

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

This reordering is the regression test

@ethanndickson ethanndickson merged commit 7500aa4 into main Jul 3, 2025
35 checks passed
@ethanndickson ethanndickson deleted the ethan/fix-cli-ping-max branch July 3, 2025 03:22
@github-actions github-actions bot locked and limited conversation to collaborators Jul 3, 2025
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