Skip to content

Tags: wandb/catnip

Tags

feature_feature_1.3.3

Toggle feature_feature_1.3.3's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add defensive error handling and logging to postStartCommand (#250)

- Add PID validation in catnip-start.sh to verify process is actually
catnip, not a recycled PID from another process after container resume
- Rewrite catnip-upgrade-and-start.sh to be more defensive:
  - Remove set -e so we always reach `service catnip start`
  - Add timestamped logging to /opt/catnip/upgrade.log for debugging
  - Wrap all potentially failing commands in conditionals
  - Add final status verification step
- This helps debug cases where catnip doesn't start on codespace resume

---------

Co-authored-by: Claude <claude@anthropic.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

v0.12.1

Toggle v0.12.1's commit message
Added pty status endpoint

feature_feature_1.3.2

Toggle feature_feature_1.3.2's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Wait for fresh environment before starting catnip service (#247)

Instead of starting catnip immediately in the entrypoint (before
GITHUB_TOKEN is available), spawn a background watcher that polls for
fresh environment data in /etc/default/catnip. The watcher waits for the
file to be recently modified AND contain GITHUB_TOKEN before starting
the service.

This ensures catnip starts with the correct environment on both fresh
builds and codespace resumes. Falls back to starting after 30s timeout
if env never becomes available.

Co-authored-by: Claude <claude@anthropic.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>

feature_feature_1.3.1

Toggle feature_feature_1.3.1's commit message
Fix catnip service not starting on codespace resume

Add catnip service start to the devcontainer entrypoint script to ensure
it starts reliably on both fresh builds and codespace resumes. Previously,
the service only started via postStartCommand which could fail silently.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

feature_feature_1.3.0

Toggle feature_feature_1.3.0's commit message
Bump devcontainer feature version to 1.3.0

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

v0.12.0

Toggle v0.12.0's commit message
Release v0.12.0

v0.11.4

Toggle v0.11.4's commit message
Release v0.11.4

v0.11.3

Toggle v0.11.3's commit message
Update default branch, fix performance issues.

feature_feature_1.2.2

Toggle feature_feature_1.2.2's commit message
Bump devcontainer feature version

feature_feature_1.2.1

Toggle feature_feature_1.2.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Add preview mode for unauthenticated users in iOS app (#213)

## Summary

Adds a preview mode toggle to the iOS app login screen, allowing users
to explore the app interface without signing in with GitHub. This uses
the existing mock data infrastructure to simulate a fully functional
experience.

## Changes

- Added `isPreviewMode` state to `AuthManager` with `enterPreviewMode()`
and `exitPreviewMode()` methods
- Added "Preview without signing in" button to `AuthView` login screen
- Updated `ContentView` navigation to show main app when in preview mode
- Modified `CodespaceView` toolbar to show "Exit Preview" option when in
preview mode (replaces "Logout")
- Extended `UITestingHelper.shouldUseMockData` to return `true` when
preview mode is active, leveraging existing test mock data

## Implementation Notes

The implementation reuses the robust mock data infrastructure already in
place for UI testing (`PreviewData.swift`, `UITestingHelper.swift`).
When preview mode is active, all API calls automatically return mock
data without requiring any changes to the network layer. The "Install
Catnip" option is hidden in preview mode since it requires authenticated
API access.

---------

Co-authored-by: Claude <claude@anthropic.com>
Co-authored-by: Claude <noreply@anthropic.com>