https://www.boundaryml.com logo
Powered by
🟡 Bug in boundary studio affecting function traci...
# questions
a
I found a bug in boundary studio. Only certain functions are traced in my TS backend and I don’t know why. Have ~10 BAML functions but can see traces for only 2 functions in studio
v
can you confirm which one you are suing?
using*
a
what version of the package are you on?
v
studio.boundaryml.com
(this is being transitioned to) or 
app.boundaryml.com
(this is being deprecated)
a
Double checking
app.boundaryml.com
V 0.213
v
message has been deleted
perf! that old studio has some issues (and was based on a very very very old version of BAML, think <0.30.0 🙂 )
we're finally just about ready with the newer version - doing just final perf validations before we announce it more broadly and then swapping out our docs + sending official deprecation emails for 
app.boundaryml.com
in early/mid dec
no obligation to migrate over today, but we are mostly only doing security fixes atm on 
app.boundaryml.com
and focusing all energy on making 
studio.boundaryml.com
awesome!
we are actively resolving any issues over on #1406858241337593876
a
for tracing using studio.boundaryml I only have to add BOUNDARY_API_KEY="xxxx....." to my envars right?
a
if you add BAML_LOG_INTERNAL=info, do you see the log 'publisher not started' ?
a
nope but I also had BAML_LOG set to WARN. So retrying with BAML_LOG set to INFO in case they conflicted
can confirm not seeing my traces in the studio
a
Hmm do you see other internal logs?
a
no
a
Oh sorry can you try BAML_INTERNAL_LOG=info
I messed up the name
a
trying rn
ok yea, i'm able to see some logs
The logs show a 500 error
a
Can you paste the logs?
a
oh there's 4 different calls because the endpoint calls 4 different BAML functions
a
the api key should be BOUNDARY_API_KEY
oh weird
you dont see anything at studio.boundaryml.com ?
a
a
do you see a log called "starting publisher" ?
do you have time to get on a zoom call?
im taking a look at our logs in the backend -- interestingly enough i see data from your project there so I need to figure out what the gap is
a
Happy to hop on call
no
a
ok let me send you a link
a
Copy code
import { defineConfig } from "tsup"
import { resolve } from "path"

export default defineConfig({
  entry: ["src/index.ts"],
  format: ["esm", "cjs"],
  dts: true,
  tsconfig: "tsconfig.json",
  esbuildOptions(options) {
    options.alias = {
      "routes/editor": resolve(__dirname, "src/routes/editor"),
      "routes/common": resolve(__dirname, "src/routes/common"),
    }
  },
})
a
a
a
a
import { Pdf } from "@boundaryml/baml" ^ SyntaxError: The requested module '@boundaryml/baml' does not provide an export named 'Pdf' at #_instantiate (node:internal/modules/esm/module_job:254:21) at async ModuleJob.run (node:internal/modules/esm/module_job:363:5) at async onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:683:26) at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:101:5) Node.js v24.7.0 [nodemon] app crashed - waiting for file changes before starting...
a
seems like the build passed when we fixed an issue where boundaryml/baml package was a different version on the root package.json than a subpackage package.json
a
ok I was able to get the pdf working. I export the PDF like this in the baml package that I have.
Copy code
export { BamlPdf as Pdf } from "@boundaryml/baml/native"
and import it as such:
Copy code
import { Pdf, b } from "@workspace/baml"
a
wow nice find!
thanks, we will try to repro and fix
created PR https://github.com/BoundaryML/baml/pull/2725 but will take a bit ofr us to merge it
PreviousNext
Powered by