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.

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

chore(api-status): add container status check #2159

Closed

Conversation

NathanFlurry
Copy link
Member

Changes

Verified

This commit was signed with the committer’s verified signature.
NathanFlurry Nathan Flurry
Copy link

cloudflare-workers-and-pages bot commented Mar 8, 2025

Deploying rivet with  Cloudflare Pages  Cloudflare Pages

Latest commit: d15d889
Status:🚫  Build failed.

View logs

Copy link
Member Author


How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

Copy link
Contributor

graphite-app bot commented Mar 8, 2025

Merge activity

  • Mar 8, 4:45 PM EST: A user added this pull request to the Graphite merge queue.
  • Mar 8, 4:46 PM EST: CI is running for this PR on a draft PR: #2160
  • Mar 8, 4:47 PM EST: A user merged this pull request with the Graphite merge queue via draft PR: #2160.

Copy link

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR adds container status check functionality alongside existing isolate checks by generalizing the configuration and routing structure.

  • Renamed actor_isolate.rs to actor.rs and added StatusQueryBuild enum to support both ws-isolate and ws-container builds
  • Renamed configuration keys from system_test_isolate_* to system_test_* across config files for more generic status check handling
  • Added container-specific resource specifications (CPU: 100, Memory: 128) in actor.rs for container builds
  • Simplified API routing from /actor/isolate to /actor to handle both types of status checks
  • Updated server spec schema to reflect renamed configuration properties while maintaining functionality

6 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

#[derive(Debug, Serialize, Deserialize)]
enum StatusQueryBuild {
#[serde(rename = "ws-isolate")]
WsIsoalte,
Copy link

Choose a reason for hiding this comment

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

syntax: WsIsoalte is misspelled (should be WsIsolate)

Suggested change
WsIsoalte,
WsIsolate,

graphite-app bot pushed a commit that referenced this pull request Mar 8, 2025

Verified

This commit was signed with the committer’s verified signature.
NathanFlurry Nathan Flurry
<!-- Please make sure there is an issue that this PR is correlated to. -->

## Changes

<!-- If there are frontend changes, please include screenshots. -->
@graphite-app graphite-app bot closed this Mar 8, 2025
@graphite-app graphite-app bot deleted the 03-08-chore_api-status_add_container_status_check branch March 8, 2025 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant