Compilation errors referencing index.js?

[sb335c]

Trying to understand if this is intended behavior.... As of 3.0.57 the compilation error message changed from referencing the sqlx file to something called "index.js". Is this expected?

config {
    type: "view",

}

SELECT 1 from ${ref("FOO")}

When running dataform compile in version 3.0.57 and above:

  Compilation errors:
  index.js: Error: Could not resolve "FOO"
    at CallSite {}
....
  definitions/mytable.sqlx: Error: Missing dependency detected: Action "dev.dataform.mytable" depends on "{"name":"FOO","includeDependentAssertions":false}" which does not exist
    at CallSite {}

3.0.56

  Compilation errors:
  definitions/mytable.sqlx: Error: Could not resolve "FOO"
    at t.Session.resolve (/tmp/tmp-79497-Iz3b8U5LAZfs/node_modules/@dataform/core/bundle.js:16:751567)
....
  definitions/mytable.sqlx: Error: Missing dependency detected: Action "dev.dataform.mytable" depends on "{"name":"FOO","includeDependentAssertions":false}" which does not exist
  

[kolina]

@rafal-hawrylak, can you take a look?

[rafal-hawrylak]

Sure, will do.

[rafal-hawrylak]

Confirmed - this is a regression. Opened #2271 with a fix.

Root cause: the vm2 bump (3.10.2 → 3.11.3) in #2168 changed how V8 CallSite objects behave inside the sandbox: they no longer carry file paths. The CLI has a global.__dataform_current_file fallback for exactly this case, but it's set/reset per module load - by the time a sqlx action's callback runs (during Session.compile), that global has been restored to the sandbox entry (index.js). So every ref()/Session.resolve failure got attributed to index.js instead of the calling .sqlx file.

Fix: track the current action's file on the Session while its callback is compiled, and use it in compileError() when no explicit path was passed. No globals, no stack introspection.

[rafal-hawrylak]

Released in 3.0.68. Feel free to share the feedback.