FOUND FIX FOR PANIC Error in 1.47.0 with optimized build of router with custom PLUGINS in router-bridge-0.5.21+v2.7.5/src/worker.rs:101:38:

[golfingal72]

I was testing everything with the un-optimized build of 1.47.0... using cargo build to create the target/debug library and everything was working. I am using rust version 1.78.0

When I build the "optimized" executable and run it, i am getting errors at startup. I am building A supergraph using rover and supplying it at startup. I also tried telling the router to use a schema that is in APOLLO Studio and I get the same error. I have tried multiple versions 1.46 and 1.45.1 and get the same error....

I tried compiling the cargo build with the release profile: below. with opt-level=1, it works, with opt-level=2 it FAILS

[profile.release]
panic='unwind'
opt-level=1
debug-assertions = true
overflow-checks = true
codegen-units = 256
debug = 1

If I use the cargo build with the dev profile, I do not get this error????

HELP! I can't find where the source code is for the worker.rs to even figure out where the error might be

` follow OpenTelemetry semantic conventions. This option will be defaulted to 'spec_compliant' in a future release and eventually removed altogether
2024-05-24T15:11:32.202025Z WARN an error happened in the worker runtime TypeError: Error parsing args at position 1: serde_v8 error: invalid type; expected: object, got: string

2024-05-24T15:11:32.202071Z WARN plan_worker: an unknown error occurred TypeError: Error parsing args at position 1: serde_v8 error: invalid type; expected: object, got: string

2024-05-24T15:11:32.207235Z ERROR panicked at /Users/lisa.cox/.cargo/registry/src/index.crates.io-6f17d22bba15001f/router-bridge-0.5.21+v2.7.5/src/worker.rs:101:38:
called Result::unwrap() on an Err value: TypeError: Error parsing args at position 1: serde_v8 error: invalid type; expected: object, got: string
at send (worker.js:54:25)
at run (worker.js:171:19)
`

[golfingal72]

I found the answer:

if you are rebuilding a custom router, please add these lines to your Cargo.toml. It appears that serde_v8 build with opt_level > 1 causes all the problems

[profile.release.package.serde_v8]
opt-level=1

[profile.dev.package.serde_v8]
opt-level=1