computefence 0.2.4__tar.gz → 0.2.5__tar.gz

computefence-0.2.5/PKG-INFO

@@ -0,0 +1,161 @@
+Metadata-Version: 2.4
+Name: computefence
+Version: 0.2.5
+Summary: Pre-flight validation for GPU training runs on rented infrastructure
+License-Expression: MIT
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: rich>=13.0.0
+Requires-Dist: pandas>=1.5.0
+Requires-Dist: typer>=0.9.0
+Requires-Dist: requests>=2.28.0
+Dynamic: license-file
+
+# ComputeFence
+
+Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, CoreWeave, Paperspace, and any bare metal GPU provider.
+
+---
+
+## Install
+
+```bash
+pip install computefence
+```
+
+Or with UV (no install required):
+
+```bash
+uvx computefence doctor
+```
+
+---
+
+## Usage
+
+```bash
+computefence doctor
+```
+
+With a dataset:
+
+```bash
+computefence doctor --dataset train.csv --input-column text --label-column label
+```
+
+With checkpoint output directory validation:
+
+```bash
+computefence doctor --output-dir ./checkpoints
+```
+
+Add to your pod startup script so it runs automatically before every job:
+
+```bash
+pip install computefence && computefence doctor && python train.py
+```
+
+---
+
+## Example output
+
+```
+ComputeFence v0.2.4 — Pre-flight diagnostic
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 WARNINGS  ·  0 BLOCKERS  ·  3 PASSED
+
+Environment
+  ✓ Python 3.11.4
+  ✓ PyTorch 2.1.0 detected
+  ✓ CUDA available — NVIDIA A40
+
+Storage
+  ⚠ HF_HOME is not set. HuggingFace will use default local cache.
+    Fix: export HF_HOME=/workspace/.cache/huggingface
+  ⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
+    Fix: Free up disk space or move checkpoints to a larger volume: df -h to check usage
+
+Dataset
+  ✓ No dataset path provided — skipping dataset checks
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 warning(s) found. Review before launching.
+Anonymous run stats are collected to improve ComputeFence. To opt out: touch ~/.computefence_no_telemetry
+```
+
+---
+
+## What it checks
+
+- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
+- **HuggingFace cache path** — confirms model weights go to persistent storage not ephemeral disk that disappears on pod stop
+- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
+- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
+- **Checkpoint output directory** — confirms your training script's output path is on persistent storage not ephemeral disk (`--output-dir`)
+- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels (`--dataset`)
+
+---
+
+## What it does not check
+
+- Training script correctness
+- Model architecture compatibility
+- Learning rate or hyperparameter safety
+- Runtime monitoring during the job
+- Dataloader throughput or GPU utilisation during training
+
+---
+
+## Why this exists
+
+I burned approximately £1,000 on GPU training runs that failed silently.
+
+CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
+
+Nothing existed that caught these before the job started. So I built it.
+
+---
+
+## Real operator results
+
+**David at Neuralic** ran ComputeFence on a RunPod A100. It caught HF_HOME writing to `/root/.cache` and an Accelerate GPU count mismatch. He fixed both before launch.
+
+**Shahzeb Ali**, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
+
+**Seven overnight organic runs** appeared in telemetry from a Vast.ai operator running the tool six times in two minutes before a real training job — without being prompted or paid to do so.
+
+---
+
+## The problem it solves
+
+A healthy GPU does not mean you are training the right job.
+
+Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage that disappears on pod stop, whether your Accelerate config matches the GPUs actually on the instance, or whether your training script's checkpoint output directory is on persistent storage. ComputeFence addresses the job configuration layer — not the environment layer.
+
+HF_HOME and your checkpoint output directory are separate paths. Fixing one does not fix the other. Both disappear on pod restart if they point to ephemeral disk.
+
+Thirteen independent ML engineers confirmed this problem independently across RunPod, Vast.ai, and AWS. Five confirmed that Docker does not solve job-specific configuration mistakes.
+
+---
+
+## Founding Design Partner pilot
+
+Running high-cost GPU training on RunPod or Vast.ai?
+
+We offer a hands-on **Founding Design Partner** pilot at **$99 for 3 months**:
+
+- Personal audit of your launch templates and persistent storage configuration
+- ComputeFence installed into your pod startup scripts so pre-flight runs automatically on every job
+- Slack or Discord webhook alert when a check fails or blocks a launch
+- Monthly 30-minute call where you shape what gets built next
+- Money back if it does not catch one bad launch in 3 months
+
+Three spots available. Email **francisco@booth.ws** to apply.
+
+---
+
+## Links
+
+- **GitHub**: [github.com/Francisco-Booth/ComputeFence](https://github.com/Francisco-Booth/ComputeFence)
+- **PyPI**: [pypi.org/project/computefence](https://pypi.org/project/computefence)

computefence-0.2.5/README.md

@@ -0,0 +1,147 @@
+# ComputeFence
+
+Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, CoreWeave, Paperspace, and any bare metal GPU provider.
+
+---
+
+## Install
+
+```bash
+pip install computefence
+```
+
+Or with UV (no install required):
+
+```bash
+uvx computefence doctor
+```
+
+---
+
+## Usage
+
+```bash
+computefence doctor
+```
+
+With a dataset:
+
+```bash
+computefence doctor --dataset train.csv --input-column text --label-column label
+```
+
+With checkpoint output directory validation:
+
+```bash
+computefence doctor --output-dir ./checkpoints
+```
+
+Add to your pod startup script so it runs automatically before every job:
+
+```bash
+pip install computefence && computefence doctor && python train.py
+```
+
+---
+
+## Example output
+
+```
+ComputeFence v0.2.4 — Pre-flight diagnostic
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 WARNINGS  ·  0 BLOCKERS  ·  3 PASSED
+
+Environment
+  ✓ Python 3.11.4
+  ✓ PyTorch 2.1.0 detected
+  ✓ CUDA available — NVIDIA A40
+
+Storage
+  ⚠ HF_HOME is not set. HuggingFace will use default local cache.
+    Fix: export HF_HOME=/workspace/.cache/huggingface
+  ⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
+    Fix: Free up disk space or move checkpoints to a larger volume: df -h to check usage
+
+Dataset
+  ✓ No dataset path provided — skipping dataset checks
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 warning(s) found. Review before launching.
+Anonymous run stats are collected to improve ComputeFence. To opt out: touch ~/.computefence_no_telemetry
+```
+
+---
+
+## What it checks
+
+- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
+- **HuggingFace cache path** — confirms model weights go to persistent storage not ephemeral disk that disappears on pod stop
+- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
+- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
+- **Checkpoint output directory** — confirms your training script's output path is on persistent storage not ephemeral disk (`--output-dir`)
+- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels (`--dataset`)
+
+---
+
+## What it does not check
+
+- Training script correctness
+- Model architecture compatibility
+- Learning rate or hyperparameter safety
+- Runtime monitoring during the job
+- Dataloader throughput or GPU utilisation during training
+
+---
+
+## Why this exists
+
+I burned approximately £1,000 on GPU training runs that failed silently.
+
+CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
+
+Nothing existed that caught these before the job started. So I built it.
+
+---
+
+## Real operator results
+
+**David at Neuralic** ran ComputeFence on a RunPod A100. It caught HF_HOME writing to `/root/.cache` and an Accelerate GPU count mismatch. He fixed both before launch.
+
+**Shahzeb Ali**, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
+
+**Seven overnight organic runs** appeared in telemetry from a Vast.ai operator running the tool six times in two minutes before a real training job — without being prompted or paid to do so.
+
+---
+
+## The problem it solves
+
+A healthy GPU does not mean you are training the right job.
+
+Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage that disappears on pod stop, whether your Accelerate config matches the GPUs actually on the instance, or whether your training script's checkpoint output directory is on persistent storage. ComputeFence addresses the job configuration layer — not the environment layer.
+
+HF_HOME and your checkpoint output directory are separate paths. Fixing one does not fix the other. Both disappear on pod restart if they point to ephemeral disk.
+
+Thirteen independent ML engineers confirmed this problem independently across RunPod, Vast.ai, and AWS. Five confirmed that Docker does not solve job-specific configuration mistakes.
+
+---
+
+## Founding Design Partner pilot
+
+Running high-cost GPU training on RunPod or Vast.ai?
+
+We offer a hands-on **Founding Design Partner** pilot at **$99 for 3 months**:
+
+- Personal audit of your launch templates and persistent storage configuration
+- ComputeFence installed into your pod startup scripts so pre-flight runs automatically on every job
+- Slack or Discord webhook alert when a check fails or blocks a launch
+- Monthly 30-minute call where you shape what gets built next
+- Money back if it does not catch one bad launch in 3 months
+
+Three spots available. Email **francisco@booth.ws** to apply.
+
+---
+
+## Links
+
+- **GitHub**: [github.com/Francisco-Booth/ComputeFence](https://github.com/Francisco-Booth/ComputeFence)
+- **PyPI**: [pypi.org/project/computefence](https://pypi.org/project/computefence)

computefence-0.2.5/computefence/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.2.5"

{computefence-0.2.4 → computefence-0.2.5}/computefence/checks/storage.py

@@ -134,3 +134,51 @@ def check_disk_headroom():
             })
 
     return results
+
+
+# Paths that are wiped when a rented instance stops.
+EPHEMERAL_PREFIXES = ["/root", "/tmp"]
+# Paths that survive an instance restart.
+PERSISTENT_PREFIXES = ["/workspace", "/runpod-volume", "/vast", "/home"]
+OUTPUT_DIR_FIX = "Move your output_dir to /workspace/checkpoints or your mounted volume"
+
+
+def _is_under(path, prefix):
+    """True when path sits at or below prefix.
+
+    Compares path components rather than string prefixes so /workspace-old is
+    not mistaken for a child of /workspace. Avoids Path.is_relative_to, which
+    needs Python 3.9 while this package supports 3.8.
+    """
+    path_parts = Path(path).parts
+    prefix_parts = Path(prefix).parts
+    return path_parts[: len(prefix_parts)] == prefix_parts
+
+
+def check_output_dir(output_dir=None):
+    """Flag a checkpoint directory that will not survive the instance stopping.
+
+    Uses abspath rather than resolve() so a path is judged as written: on macOS
+    /tmp is a symlink to /private/tmp, and resolving it first would hide the
+    very ephemeral prefix this check exists to catch.
+    """
+    if output_dir is None:
+        return []
+
+    path = Path(os.path.abspath(os.path.expanduser(str(output_dir))))
+
+    is_ephemeral = any(_is_under(path, prefix) for prefix in EPHEMERAL_PREFIXES) or not any(
+        _is_under(path, prefix) for prefix in PERSISTENT_PREFIXES
+    )
+
+    if is_ephemeral:
+        return [{
+            "status": "fail",
+            "message": f"Output directory {path} is on ephemeral storage and will be lost when the instance stops",
+            "fix": OUTPUT_DIR_FIX
+        }]
+
+    return [{
+        "status": "pass",
+        "message": f"Output directory {path} is on persistent storage"
+    }]

{computefence-0.2.4 → computefence-0.2.5}/computefence/cli.py

@@ -2,7 +2,7 @@ import sys
 from rich.console import Console
 from computefence import __version__
 from computefence.checks.environment import check_environment
-from computefence.checks.storage import check_disk_headroom, check_storage
+from computefence.checks.storage import check_disk_headroom, check_output_dir, check_storage
 from computefence.checks.dataset import check_dataset
 from computefence.telemetry import record_run
 
@@ -27,6 +27,7 @@ def doctor():
     dataset = None
     input_column = None
     label_column = None
+    output_dir = None
     args = sys.argv[1:]
     i = 0
     while i < len(args):
@@ -39,6 +40,9 @@ def doctor():
         elif args[i] == "--label-column" and i + 1 < len(args):
             label_column = args[i + 1]
             i += 2
+        elif args[i] == "--output-dir" and i + 1 < len(args):
+            output_dir = args[i + 1]
+            i += 2
         else:
             i += 1
 
@@ -47,7 +51,7 @@ def doctor():
     console.print("━" * 50)
 
     env_results = check_environment()
-    storage_results = check_storage() + check_disk_headroom()
+    storage_results = check_storage() + check_disk_headroom() + check_output_dir(output_dir)
     dataset_results = check_dataset(
         dataset_path=dataset,
         input_column=input_column,

computefence-0.2.5/computefence.egg-info/PKG-INFO

@@ -0,0 +1,161 @@
+Metadata-Version: 2.4
+Name: computefence
+Version: 0.2.5
+Summary: Pre-flight validation for GPU training runs on rented infrastructure
+License-Expression: MIT
+Requires-Python: >=3.8
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: rich>=13.0.0
+Requires-Dist: pandas>=1.5.0
+Requires-Dist: typer>=0.9.0
+Requires-Dist: requests>=2.28.0
+Dynamic: license-file
+
+# ComputeFence
+
+Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, CoreWeave, Paperspace, and any bare metal GPU provider.
+
+---
+
+## Install
+
+```bash
+pip install computefence
+```
+
+Or with UV (no install required):
+
+```bash
+uvx computefence doctor
+```
+
+---
+
+## Usage
+
+```bash
+computefence doctor
+```
+
+With a dataset:
+
+```bash
+computefence doctor --dataset train.csv --input-column text --label-column label
+```
+
+With checkpoint output directory validation:
+
+```bash
+computefence doctor --output-dir ./checkpoints
+```
+
+Add to your pod startup script so it runs automatically before every job:
+
+```bash
+pip install computefence && computefence doctor && python train.py
+```
+
+---
+
+## Example output
+
+```
+ComputeFence v0.2.4 — Pre-flight diagnostic
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 WARNINGS  ·  0 BLOCKERS  ·  3 PASSED
+
+Environment
+  ✓ Python 3.11.4
+  ✓ PyTorch 2.1.0 detected
+  ✓ CUDA available — NVIDIA A40
+
+Storage
+  ⚠ HF_HOME is not set. HuggingFace will use default local cache.
+    Fix: export HF_HOME=/workspace/.cache/huggingface
+  ⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
+    Fix: Free up disk space or move checkpoints to a larger volume: df -h to check usage
+
+Dataset
+  ✓ No dataset path provided — skipping dataset checks
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+2 warning(s) found. Review before launching.
+Anonymous run stats are collected to improve ComputeFence. To opt out: touch ~/.computefence_no_telemetry
+```
+
+---
+
+## What it checks
+
+- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
+- **HuggingFace cache path** — confirms model weights go to persistent storage not ephemeral disk that disappears on pod stop
+- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
+- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
+- **Checkpoint output directory** — confirms your training script's output path is on persistent storage not ephemeral disk (`--output-dir`)
+- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels (`--dataset`)
+
+---
+
+## What it does not check
+
+- Training script correctness
+- Model architecture compatibility
+- Learning rate or hyperparameter safety
+- Runtime monitoring during the job
+- Dataloader throughput or GPU utilisation during training
+
+---
+
+## Why this exists
+
+I burned approximately £1,000 on GPU training runs that failed silently.
+
+CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
+
+Nothing existed that caught these before the job started. So I built it.
+
+---
+
+## Real operator results
+
+**David at Neuralic** ran ComputeFence on a RunPod A100. It caught HF_HOME writing to `/root/.cache` and an Accelerate GPU count mismatch. He fixed both before launch.
+
+**Shahzeb Ali**, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
+
+**Seven overnight organic runs** appeared in telemetry from a Vast.ai operator running the tool six times in two minutes before a real training job — without being prompted or paid to do so.
+
+---
+
+## The problem it solves
+
+A healthy GPU does not mean you are training the right job.
+
+Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage that disappears on pod stop, whether your Accelerate config matches the GPUs actually on the instance, or whether your training script's checkpoint output directory is on persistent storage. ComputeFence addresses the job configuration layer — not the environment layer.
+
+HF_HOME and your checkpoint output directory are separate paths. Fixing one does not fix the other. Both disappear on pod restart if they point to ephemeral disk.
+
+Thirteen independent ML engineers confirmed this problem independently across RunPod, Vast.ai, and AWS. Five confirmed that Docker does not solve job-specific configuration mistakes.
+
+---
+
+## Founding Design Partner pilot
+
+Running high-cost GPU training on RunPod or Vast.ai?
+
+We offer a hands-on **Founding Design Partner** pilot at **$99 for 3 months**:
+
+- Personal audit of your launch templates and persistent storage configuration
+- ComputeFence installed into your pod startup scripts so pre-flight runs automatically on every job
+- Slack or Discord webhook alert when a check fails or blocks a launch
+- Monthly 30-minute call where you shape what gets built next
+- Money back if it does not catch one bad launch in 3 months
+
+Three spots available. Email **francisco@booth.ws** to apply.
+
+---
+
+## Links
+
+- **GitHub**: [github.com/Francisco-Booth/ComputeFence](https://github.com/Francisco-Booth/ComputeFence)
+- **PyPI**: [pypi.org/project/computefence](https://pypi.org/project/computefence)

computefence-0.2.4/PKG-INFO

@@ -1,110 +0,0 @@
-Metadata-Version: 2.4
-Name: computefence
-Version: 0.2.4
-Summary: Pre-flight validation for GPU training runs on rented infrastructure
-License-Expression: MIT
-Requires-Python: >=3.8
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: rich>=13.0.0
-Requires-Dist: pandas>=1.5.0
-Requires-Dist: typer>=0.9.0
-Requires-Dist: requests>=2.28.0
-Dynamic: license-file
-
-# ComputeFence
-
-Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, and similar bare metal providers.
-
-## Install
-
-```bash
-pip install computefence
-```
-
-Or with UV:
-
-```bash
-uvx computefence doctor
-```
-
-## Usage
-
-```bash
-computefence doctor
-```
-
-With a dataset:
-
-```bash
-computefence doctor --dataset train.csv --input-column text --label-column label
-```
-
-## Example output
-
-ComputeFence v0.2.0 — Pre-flight diagnostic
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 WARNINGS · 0 BLOCKERS · 3 PASSED
-
-Environment
-✓ Python 3.11.4
-✓ PyTorch 2.1.0 detected
-✓ CUDA available — NVIDIA A40
-
-Storage
-⚠ HF_HOME is not set. HuggingFace will use default local cache.
-Fix: export HF_HOME=/workspace/.cache/huggingface
-⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
-Fix: Free up disk space or attach a larger volume before launching
-
-Dataset
-✓ No dataset path provided — skipping dataset checks
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 warning(s) found. Review before launching.
-
-
-## What it checks
-
-- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
-- **HuggingFace cache path** — confirms model files go to persistent storage not ephemeral disk
-- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
-- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
-- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels
-
-## What it does not check
-
-- Training script correctness
-- Model architecture compatibility
-- Learning rate or hyperparameter safety
-- Runtime monitoring during the job
-- Slow dataloader or data pipeline throughput
-- Dataloader bottleneck causing low GPU utilisation
-
-## Why this exists
-
-I burned approximately £1,000 on GPU training runs that failed silently. CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
-
-Nothing existed that caught these before the job started. So I built it.
-
-## Real operator results
-
-David at Neuralic ran ComputeFence on a RunPod A100. It caught HF_HOME writing to /root/.cache and an Accelerate GPU count mismatch. He fixed both before launch.
-
-Shahzeb Ali, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
-
-## The problem it solves
-
-A healthy GPU does not mean you are training the right job.
-
-Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage, whether your Accelerate config matches the GPUs actually on the instance, or whether your disk has enough headroom for checkpoints. ComputeFence addresses the job layer not the environment layer.
-
-Five independent operators confirmed this independently. Docker does not solve job-specific configuration mistakes.
-
-## GitHub
-
-github.com/Francisco-Booth/ComputeFence
-
-## PyPI
-
-pypi.org/project/computefence

computefence-0.2.4/README.md

@@ -1,96 +0,0 @@
-# ComputeFence
-
-Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, and similar bare metal providers.
-
-## Install
-
-```bash
-pip install computefence
-```
-
-Or with UV:
-
-```bash
-uvx computefence doctor
-```
-
-## Usage
-
-```bash
-computefence doctor
-```
-
-With a dataset:
-
-```bash
-computefence doctor --dataset train.csv --input-column text --label-column label
-```
-
-## Example output
-
-ComputeFence v0.2.0 — Pre-flight diagnostic
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 WARNINGS · 0 BLOCKERS · 3 PASSED
-
-Environment
-✓ Python 3.11.4
-✓ PyTorch 2.1.0 detected
-✓ CUDA available — NVIDIA A40
-
-Storage
-⚠ HF_HOME is not set. HuggingFace will use default local cache.
-Fix: export HF_HOME=/workspace/.cache/huggingface
-⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
-Fix: Free up disk space or attach a larger volume before launching
-
-Dataset
-✓ No dataset path provided — skipping dataset checks
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 warning(s) found. Review before launching.
-
-
-## What it checks
-
-- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
-- **HuggingFace cache path** — confirms model files go to persistent storage not ephemeral disk
-- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
-- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
-- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels
-
-## What it does not check
-
-- Training script correctness
-- Model architecture compatibility
-- Learning rate or hyperparameter safety
-- Runtime monitoring during the job
-- Slow dataloader or data pipeline throughput
-- Dataloader bottleneck causing low GPU utilisation
-
-## Why this exists
-
-I burned approximately £1,000 on GPU training runs that failed silently. CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
-
-Nothing existed that caught these before the job started. So I built it.
-
-## Real operator results
-
-David at Neuralic ran ComputeFence on a RunPod A100. It caught HF_HOME writing to /root/.cache and an Accelerate GPU count mismatch. He fixed both before launch.
-
-Shahzeb Ali, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
-
-## The problem it solves
-
-A healthy GPU does not mean you are training the right job.
-
-Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage, whether your Accelerate config matches the GPUs actually on the instance, or whether your disk has enough headroom for checkpoints. ComputeFence addresses the job layer not the environment layer.
-
-Five independent operators confirmed this independently. Docker does not solve job-specific configuration mistakes.
-
-## GitHub
-
-github.com/Francisco-Booth/ComputeFence
-
-## PyPI
-
-pypi.org/project/computefence

computefence-0.2.4/computefence/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.2.4"

computefence-0.2.4/computefence.egg-info/PKG-INFO

@@ -1,110 +0,0 @@
-Metadata-Version: 2.4
-Name: computefence
-Version: 0.2.4
-Summary: Pre-flight validation for GPU training runs on rented infrastructure
-License-Expression: MIT
-Requires-Python: >=3.8
-Description-Content-Type: text/markdown
-License-File: LICENSE
-Requires-Dist: rich>=13.0.0
-Requires-Dist: pandas>=1.5.0
-Requires-Dist: typer>=0.9.0
-Requires-Dist: requests>=2.28.0
-Dynamic: license-file
-
-# ComputeFence
-
-Pre-flight safety gate for ML training jobs on rented GPU compute. Built for RunPod, Vast.ai, Lambda Labs, and similar bare metal providers.
-
-## Install
-
-```bash
-pip install computefence
-```
-
-Or with UV:
-
-```bash
-uvx computefence doctor
-```
-
-## Usage
-
-```bash
-computefence doctor
-```
-
-With a dataset:
-
-```bash
-computefence doctor --dataset train.csv --input-column text --label-column label
-```
-
-## Example output
-
-ComputeFence v0.2.0 — Pre-flight diagnostic
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 WARNINGS · 0 BLOCKERS · 3 PASSED
-
-Environment
-✓ Python 3.11.4
-✓ PyTorch 2.1.0 detected
-✓ CUDA available — NVIDIA A40
-
-Storage
-⚠ HF_HOME is not set. HuggingFace will use default local cache.
-Fix: export HF_HOME=/workspace/.cache/huggingface
-⚠ Root disk (/) — 14.3 GB free of 460.4 GB (below 20 GB)
-Fix: Free up disk space or attach a larger volume before launching
-
-Dataset
-✓ No dataset path provided — skipping dataset checks
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-2 warning(s) found. Review before launching.
-
-
-## What it checks
-
-- **CUDA and GPU visibility** — confirms PyTorch can see the GPU and training will not silently fall back to CPU
-- **HuggingFace cache path** — confirms model files go to persistent storage not ephemeral disk
-- **Accelerate GPU count** — confirms your distributed training config matches the GPUs actually on the instance
-- **Disk space headroom** — checks free space on workspace volumes and root disk. Warns below 20 GB, blocks below 5 GB
-- **Dataset integrity** — optional scan for duplicates, missing values, and conflicting labels
-
-## What it does not check
-
-- Training script correctness
-- Model architecture compatibility
-- Learning rate or hyperparameter safety
-- Runtime monitoring during the job
-- Slow dataloader or data pipeline throughput
-- Dataloader bottleneck causing low GPU utilisation
-
-## Why this exists
-
-I burned approximately £1,000 on GPU training runs that failed silently. CUDA fell back to CPU with no error. 24 seconds per iteration instead of 0.4. Class weights caused loss collapse to 0.693 immediately. My dataset had 28,432 duplicate rows and 312 conflicting labels I only found after the run.
-
-Nothing existed that caught these before the job started. So I built it.
-
-## Real operator results
-
-David at Neuralic ran ComputeFence on a RunPod A100. It caught HF_HOME writing to /root/.cache and an Accelerate GPU count mismatch. He fixed both before launch.
-
-Shahzeb Ali, a computer vision engineer running client training jobs on RunPod, confirmed the storage warning matches real pod behaviour and would not have caught the HF_HOME issue explicitly without the tool.
-
-## The problem it solves
-
-A healthy GPU does not mean you are training the right job.
-
-Docker makes environments reproducible. It does not check whether your HuggingFace cache is writing to ephemeral storage, whether your Accelerate config matches the GPUs actually on the instance, or whether your disk has enough headroom for checkpoints. ComputeFence addresses the job layer not the environment layer.
-
-Five independent operators confirmed this independently. Docker does not solve job-specific configuration mistakes.
-
-## GitHub
-
-github.com/Francisco-Booth/ComputeFence
-
-## PyPI
-
-pypi.org/project/computefence