flopscope-server 0.3.0__tar.gz → 0.4.0__tar.gz

flopscope_server-0.4.0/PKG-INFO

@@ -0,0 +1,91 @@
+Metadata-Version: 2.4
+Name: flopscope-server
+Version: 0.4.0
+Summary: Backend server for flopscope client-server architecture
+License-Expression: MIT
+Requires-Python: >=3.10
+Requires-Dist: flopscope==0.4.0
+Requires-Dist: msgpack>=1.0.0
+Requires-Dist: numpy<2.5.0,>=2.0.0
+Requires-Dist: pyzmq>=26.0.0
+Description-Content-Type: text/markdown
+
+# flopscope-server
+
+[![PyPI version](https://img.shields.io/pypi/v/flopscope-server.svg)](https://pypi.org/project/flopscope-server/)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
+
+Server-side runtime for the [flopscope](https://pypi.org/project/flopscope/) client-server architecture.
+
+`flopscope-server` runs the heavy NumPy-backed `flopscope` library on behalf of remote `flopscope-client` processes that connect over ZMQ + msgpack. Use it when you want to isolate untrusted or sandboxed code (typically participant submissions in the [ARC Whitebox Estimation Challenge](https://www.alignment.org/blog/will-whitebox-runtime-monitoring-defeat-scheming-models/)) from the actual computation environment.
+
+## When to install this
+
+You want this on the **server** side of a client-server flopscope deployment. It pulls in `flopscope`, `numpy`, `pyzmq`, and `msgpack`:
+
+```bash
+pip install flopscope-server
+```
+
+Equivalent extra on the main flopscope distribution (installs both at the same exact version):
+
+```bash
+pip install "flopscope[server]"
+```
+
+## Quick start
+
+### Launch the server
+
+```bash
+# Over a UNIX domain socket (recommended for local / single-host deployments)
+python -m flopscope_server --url ipc:///tmp/flopscope.sock
+
+# Or over TCP
+python -m flopscope_server --url tcp://127.0.0.1:15555
+```
+
+### Connect a client
+
+In a separate process (typically a sandboxed container) that has [`flopscope-client`](https://pypi.org/project/flopscope-client/) installed:
+
+```bash
+export FLOPSCOPE_SERVER_URL=ipc:///tmp/flopscope.sock
+```
+
+```python
+import flopscope as flops
+import flopscope.numpy as fnp
+
+with flops.BudgetContext(flop_budget=1_000_000):
+    a = fnp.array([1.0, 2.0, 3.0])
+    b = fnp.array([4.0, 5.0, 6.0])
+    fnp.add(a, b)
+    flops.budget_summary()
+```
+
+The client's first request performs a version handshake with the server; mismatched flopscope versions raise `ConnectionError` with both versions in the message. Keep `flopscope-server` and `flopscope-client` on the same release.
+
+## Architecture overview
+
+```
+┌─────────────────────────────┐         ZMQ + msgpack         ┌──────────────────────────────┐
+│  flopscope-client process   │ ───────────────────────────▶  │  flopscope-server process    │
+│  (sandbox; no numpy)        │                                │  (full flopscope + numpy)    │
+│  `import flopscope as flops`│ ◀───────────────────────────  │  Executes ops, tracks budget │
+└─────────────────────────────┘                                └──────────────────────────────┘
+```
+
+Every counted operation (matmul, einsum, FFT, reductions, …) is dispatched to the server, executed against the real library, and the result + remaining budget streamed back. The client never sees numpy.
+
+## Related
+
+- [`flopscope`](https://pypi.org/project/flopscope/) — the NumPy-backed library hosted by this server
+- [`flopscope-client`](https://pypi.org/project/flopscope-client/) — the lightweight proxy clients use to talk to a flopscope-server
+- [Documentation](https://aicrowd.github.io/flopscope/) — full guides including client/server architecture and Docker recipes
+- [GitHub](https://github.com/AIcrowd/flopscope) — source, CHANGELOG, contributor guide
+
+## License
+
+[MIT](https://github.com/AIcrowd/flopscope/blob/main/LICENSE)

flopscope_server-0.4.0/README.md

@@ -0,0 +1,79 @@
+# flopscope-server
+
+[![PyPI version](https://img.shields.io/pypi/v/flopscope-server.svg)](https://pypi.org/project/flopscope-server/)
+[![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)](https://www.python.org/downloads/)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
+
+Server-side runtime for the [flopscope](https://pypi.org/project/flopscope/) client-server architecture.
+
+`flopscope-server` runs the heavy NumPy-backed `flopscope` library on behalf of remote `flopscope-client` processes that connect over ZMQ + msgpack. Use it when you want to isolate untrusted or sandboxed code (typically participant submissions in the [ARC Whitebox Estimation Challenge](https://www.alignment.org/blog/will-whitebox-runtime-monitoring-defeat-scheming-models/)) from the actual computation environment.
+
+## When to install this
+
+You want this on the **server** side of a client-server flopscope deployment. It pulls in `flopscope`, `numpy`, `pyzmq`, and `msgpack`:
+
+```bash
+pip install flopscope-server
+```
+
+Equivalent extra on the main flopscope distribution (installs both at the same exact version):
+
+```bash
+pip install "flopscope[server]"
+```
+
+## Quick start
+
+### Launch the server
+
+```bash
+# Over a UNIX domain socket (recommended for local / single-host deployments)
+python -m flopscope_server --url ipc:///tmp/flopscope.sock
+
+# Or over TCP
+python -m flopscope_server --url tcp://127.0.0.1:15555
+```
+
+### Connect a client
+
+In a separate process (typically a sandboxed container) that has [`flopscope-client`](https://pypi.org/project/flopscope-client/) installed:
+
+```bash
+export FLOPSCOPE_SERVER_URL=ipc:///tmp/flopscope.sock
+```
+
+```python
+import flopscope as flops
+import flopscope.numpy as fnp
+
+with flops.BudgetContext(flop_budget=1_000_000):
+    a = fnp.array([1.0, 2.0, 3.0])
+    b = fnp.array([4.0, 5.0, 6.0])
+    fnp.add(a, b)
+    flops.budget_summary()
+```
+
+The client's first request performs a version handshake with the server; mismatched flopscope versions raise `ConnectionError` with both versions in the message. Keep `flopscope-server` and `flopscope-client` on the same release.
+
+## Architecture overview
+
+```
+┌─────────────────────────────┐         ZMQ + msgpack         ┌──────────────────────────────┐
+│  flopscope-client process   │ ───────────────────────────▶  │  flopscope-server process    │
+│  (sandbox; no numpy)        │                                │  (full flopscope + numpy)    │
+│  `import flopscope as flops`│ ◀───────────────────────────  │  Executes ops, tracks budget │
+└─────────────────────────────┘                                └──────────────────────────────┘
+```
+
+Every counted operation (matmul, einsum, FFT, reductions, …) is dispatched to the server, executed against the real library, and the result + remaining budget streamed back. The client never sees numpy.
+
+## Related
+
+- [`flopscope`](https://pypi.org/project/flopscope/) — the NumPy-backed library hosted by this server
+- [`flopscope-client`](https://pypi.org/project/flopscope-client/) — the lightweight proxy clients use to talk to a flopscope-server
+- [Documentation](https://aicrowd.github.io/flopscope/) — full guides including client/server architecture and Docker recipes
+- [GitHub](https://github.com/AIcrowd/flopscope) — source, CHANGELOG, contributor guide
+
+## License
+
+[MIT](https://github.com/AIcrowd/flopscope/blob/main/LICENSE)

{flopscope_server-0.3.0 → flopscope_server-0.4.0}/pyproject.toml

@@ -4,11 +4,13 @@ build-backend = "hatchling.build"
 
 [project]
 name = "flopscope-server"
-version = "0.3.0"
+version = "0.4.0"
 description = "Backend server for flopscope client-server architecture"
+readme = "README.md"
 requires-python = ">=3.10"
+license = "MIT"
 dependencies = [
-    "flopscope==0.3.0",
+    "flopscope==0.4.0",
     "numpy>=2.0.0,<2.5.0",
     "pyzmq>=26.0.0",
     "msgpack>=1.0.0",

{flopscope_server-0.3.0 → flopscope_server-0.4.0}/src/flopscope_server/__init__.py

@@ -1,3 +1,3 @@
 """Flopscope backend server — executes numpy operations on behalf of remote clients."""
 
-__version__ = "0.3.0"
+__version__ = "0.4.0"

flopscope_server-0.3.0/PKG-INFO

@@ -1,9 +0,0 @@
-Metadata-Version: 2.4
-Name: flopscope-server
-Version: 0.3.0
-Summary: Backend server for flopscope client-server architecture
-Requires-Python: >=3.10
-Requires-Dist: flopscope==0.3.0
-Requires-Dist: msgpack>=1.0.0
-Requires-Dist: numpy<2.5.0,>=2.0.0
-Requires-Dist: pyzmq>=26.0.0