Skip to content

Conversation

Kovbo
Copy link
Collaborator

@Kovbo Kovbo commented Apr 29, 2025

Skypilot switched to a new client-server architecture where all client methods are async. Now we have a SkyPilot client and a SkyPilot server running on the same machine. The client just starts jobs, and the server executes them in the background. If we want to see logs, we need to capture them manually.

@Kovbo Kovbo marked this pull request as draft April 29, 2025 03:33
@Kovbo Kovbo changed the title Update skypilot Update skypilot, use async api Apr 30, 2025
@Kovbo Kovbo marked this pull request as ready for review April 30, 2025 00:57
Copy link
Contributor

@arcticfly arcticfly left a comment

Choose a reason for hiding this comment

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

Thanks for taking on this update!

This may be an issue with the new skypilot version (or an unrelated update), but when you launch a cluster through the SkyPilotAPI, do you see messages like these?

WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 1 of 3. Reason: timed out
WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 2 of 3. Reason: timed out
WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 3 of 3. Reason: [Errno 64] Host is down
WARNING:google.auth._default:Authentication failed using Compute Engine authentication due to unavailable metadata server.
WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 1 of 3. Reason: [Errno 64] Host is down
WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 2 of 3. Reason: [Errno 64] Host is down
WARNING:google.auth.compute_engine._metadata:Compute Engine Metadata server unavailable on attempt 3 of 3. Reason: [Errno 64] Host is down
WARNING:google.auth._default:Authentication failed using Compute Engine authentication due to unavailable metadata server.

uv.lock Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

Make sure to run uv sync on a linux machine. We've seen weird bugs from syncing on macbooks then running the backend on a linux machine.

@Kovbo Kovbo marked this pull request as draft May 1, 2025 02:15
@Kovbo Kovbo marked this pull request as ready for review May 30, 2025 22:31
@Kovbo Kovbo requested a review from arcticfly May 30, 2025 22:32
@corbt
Copy link
Contributor

corbt commented Jul 14, 2025

@Kovbo when you get a chance do you want to check to make sure this still works and then we can get it in?

@Kovbo
Copy link
Collaborator Author

Kovbo commented Jul 14, 2025

@Kovbo when you get a chance do you want to check to make sure this still works and then we can get it in?

I ran some tests last week, and it worked fine. I can try running more examples today.

@corbt corbt merged commit 5edf821 into OpenPipe:main Jul 15, 2025
1 check passed
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.

3 participants