Skip to content

Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, DeepSeek-V4.1, MiniMax-H3, Gemma 4, FLUX and more.

Move the studiobench attribution config in with the harness (#10100)

Daniel Han1d2679f4f02f
diff --git a/tests/studio/studiobench/analysis/bridge_build.py b/tests/studio/studiobench/analysis/bridge_build.py
index 7ec73161205..f14fed7d030 100644
--- a/tests/studio/studiobench/analysis/bridge_build.py
+++ b/tests/studio/studiobench/analysis/bridge_build.py
@@ -332,7 +332,7 @@ def assert_attribution_build(page: Any) -> dict[str, Any]:
Catches the staleness failure: a shipping dist left in the directory handed
to `unsloth studio --frontend <dir>` produces a perfectly healthy Unsloth
serving the WRONG bundle, with no profiling renderer and therefore a React
- stage that reads 0.00. `attribution/vite.studiobench.config.ts` defines
+ stage that reads 0.00. `../attribution/vite.studiobench.config.ts` defines
`__STUDIOBENCH_ATTRIBUTION_BUILD__` for exactly this check.
"""
marker = page.evaluate("globalThis.__STUDIOBENCH_ATTRIBUTION_BUILD__ === true")
@@ -341,7 +341,8 @@ def assert_attribution_build(page: Any) -> dict[str, Any]:
"not_the_attribution_build",
"__STUDIOBENCH_ATTRIBUTION_BUILD__ is not defined in the loaded bundle. The "
"directory passed to `unsloth studio --frontend` is serving some other dist, most "
- "likely a stale shipping build. Rebuild with attribution/vite.studiobench.config.ts.",
+ "likely a stale shipping build. Rebuild with "
+ "tests/studio/studiobench/attribution/vite.studiobench.config.ts.",
)
return {"attribution_build_verified": True}
diff --git a/attribution/vite.studiobench.config.ts b/tests/studio/studiobench/attribution/vite.studiobench.config.ts
similarity index 97%
rename from attribution/vite.studiobench.config.ts
rename to tests/studio/studiobench/attribution/vite.studiobench.config.ts
index 9f4369e0b0a..0d2a76ec3b2 100644
--- a/attribution/vite.studiobench.config.ts
+++ b/tests/studio/studiobench/attribution/vite.studiobench.config.ts
@@ -30,7 +30,7 @@
import { createRequire } from "node:module";
import path from "node:path";
-const FRONTEND_ROOT = path.resolve(__dirname, "../studio/frontend");
+const FRONTEND_ROOT = path.resolve(__dirname, "../../../../studio/frontend");
// The plugins are resolved from the FRONTEND package, not from this directory,
// and that is not a stylistic preference. Vite bundles a `--config` file with
@@ -38,8 +38,8 @@ const FRONTEND_ROOT = path.resolve(__dirname, "../studio/frontend");
// path.dirname(fileName)`) and then loads the bundle under the config file's
// own path: CJS via `module._compile(code, <config path>)`, ESM via a temp file
// in the nearest ancestor `node_modules`, of which this directory has none. So
-// Node starts its `node_modules` walk at `attribution/` and climbs to the
-// repository root, and NEITHER has a `node_modules` -- only
+// Node starts its `node_modules` walk here and climbs to the repository root,
+// and NOTHING on that path has a `node_modules` -- only
// `studio/frontend/node_modules` does. Written with plain top-level imports
// this config could not be loaded from any working directory, by any `vite`
// binary: `Cannot find module '@tailwindcss/vite'`, and the same for the React
@@ -183,7 +183,7 @@ export default defineConfig({
// Marks the bundle so the harness can prove it is measuring the
// attribution build and not a stale shipping dist left in the
// directory handed to `unsloth studio --frontend`. Read by
- // `analysis/bridge_build.py:assert_attribution_build`.
+ // `../analysis/bridge_build.py:assert_attribution_build`.
//
// This is a BANNER and not a `define`, and the difference is not
// cosmetic. `define` performs identifier SUBSTITUTION in source: it