gistfile0.txt

env MB_FUZZ=1 yarn test-unit frontend/src/metabase/querying/expressions/fuzz.compiler.unit.spec.ts
yarn run v1.22.22
warning ../package.json: No license field
$ yarn build:cljs && jest --maxWorkers=4 frontend/src/metabase/querying/expressions/fuzz.compiler.unit.spec.ts
warning ../package.json: No license field
$ yarn && yarn build-pure:cljs
warning ../package.json: No license field
$ echo $npm_execpath | grep -q yarn || echo '\033[0;33mSorry, npm is not supported. Please use Yarn (https://yarnpkg.com/).\033[0m'
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
warning Resolution field "[email protected]" is incompatible with requested version "ansi-regex@^6.0.1"
warning Resolution field "[email protected]" is incompatible with requested version "ansi-regex@^2.0.0"
warning Resolution field "[email protected]" is incompatible with requested version "json5@^2.2.3"
warning Resolution field "[email protected]" is incompatible with requested version "json5@^1.0.2"
warning Resolution field "[email protected]" is incompatible with requested version "path-to-regexp@^2.2.1"
warning Resolution field "[email protected]" is incompatible with requested version "ansi-regex@^6.0.1"
[3/5] 🚚  Fetching packages...
warning [email protected]: The engine "pnpm" appears to be invalid.
[4/5] 🔗  Linking dependencies...
warning " > @uiw/[email protected]" has unmet peer dependency "@babel/runtime@>=7.11.0".
warning " > @uiw/[email protected]" has unmet peer dependency "@codemirror/state@>=6.0.0".
warning " > @uiw/[email protected]" has unmet peer dependency "@codemirror/theme-one-dark@>=6.0.0".
warning " > @uiw/[email protected]" has unmet peer dependency "@codemirror/view@>=6.0.0".
warning " > @uiw/[email protected]" has unmet peer dependency "codemirror@>=6.0.0".
warning "@uiw/react-codemirror > @uiw/[email protected]" has unmet peer dependency "@codemirror/language@>=6.0.0".
warning "@uiw/react-codemirror > @uiw/[email protected]" has unmet peer dependency "@codemirror/lint@>=6.0.0".
warning "@uiw/react-codemirror > @uiw/[email protected]" has unmet peer dependency "@codemirror/search@>=6.0.0".
warning "@uiw/react-codemirror > @uiw/[email protected]" has unmet peer dependency "@codemirror/view@>=6.0.0".
warning "kbar > [email protected]" has incorrect peer dependency "react@^16.6.3 || ^17.0.0".
warning " > [email protected]" has incorrect peer dependency "react@^15.3.0 || ^16.0.0".
warning " > [email protected]" has incorrect peer dependency "react@^0.14.0 || ^15.0.0 || ^16.0.0".
warning " > @cypress/[email protected]" has incorrect peer dependency "react@^=16.x || ^=17.x".
warning " > @cypress/[email protected]" has incorrect peer dependency "react-dom@^=16.x || ^=17.x".
warning "@storybook/addon-a11y > [email protected]" has unmet peer dependency "vitest@>=0.16.0".
warning " > @testing-library/[email protected]" has unmet peer dependency "@testing-library/dom@>=7.21.4".
warning " > @testing-library/[email protected]" has incorrect peer dependency "cypress@^12.0.0 || ^13.0.0".
warning " > @testing-library/[email protected]" has unmet peer dependency "@testing-library/dom@^10.0.0".
[5/5] 🔨  Building fresh packages...

$ yarn yarn-deduplicate --scopes @babel && patch-package
warning ../package.json: No license field
$ /Users/bcm/dv/mb/metabase/node_modules/.bin/yarn-deduplicate --scopes @babel
patch-package 8.0.0
Applying patches...
@bahmutov/[email protected] ✔
@loki/[email protected] ✔
@mantine/[email protected] ✔
@types/[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔
[email protected] ✔

Warning: patch-package detected a patch file version mismatch

  Don't worry! This is probably fine. The patch was still applied
  successfully. Here's the deets:

  Patch file created for

    [email protected]

  applied to

    [email protected]

  At path

    node_modules/echarts

  This warning is just to give you a heads-up. There is a small chance of
  breakage even though the patch was applied successfully. Make sure the package
  still behaves like you expect (you wrote tests, right?) and then run

    patch-package echarts

  to update the version in the patch file name and make this warning go away.

---
patch-package finished with 1 warning(s).
$ husky install
husky - Git hooks installed
warning ../package.json: No license field
$ yarn clean-dev:cljs && shadow-cljs compile app
warning ../package.json: No license field
$ rm -rf target/cljs_dev/*
shadow-cljs - config: /Users/bcm/dv/mb/metabase/shadow-cljs.edn
shadow-cljs - starting via "clojure"
[:app] Compiling ...
Warning: environ value /Users/bcm/.sdkman/candidates/java/current for key :java-home has been overwritten with /Users/bcm/.sdkman/candidates/java/21.0.7-tem
2025-07-18 10:43:54,914 INFO metabase.util :: Maximum memory available to JVM: 16.0 GB
[:app] Build completed. (345 files, 136 compiled, 0 warnings, 5.99s)
No tests found, exiting with code 1
Run with `--passWithNoTests` to exit with code 0
In /Users/bcm/dv/mb/metabase
  23108 files checked across 2 projects. Run with `--verbose` for more details.
Pattern: frontend/src/metabase/querying/expressions/fuzz.compiler.unit.spec.ts - 0 matches
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.