Open naheller opened 1 month ago
We do have some docs about building the binary, but they are not detailed. @JonasBa we should probably add more docs about this. Going to backlog for now, but PRs are welcome.
Aside: One issue with using arch
from node:os
is that it records the architecture of where node was compiled - not where node is actually running. See https://www.npmjs.com/package/system-architecture (I have a long standing TODO to just PR a new API into node.js to fix this, let me see if I can just do it this weekend).
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
8.17.0
Framework Version
@sentry/node 8.17.0
Link to Sentry event
No response
SDK Setup/Reproduction Example
Steps to Reproduce
Expected Result
If precompiled binary is not found for the dynamically constructed source path, there should be fallback functionality that builds the required binary from source. In this case, for 32-bit linux.
Otherwise, if there is no automatic fallback behavior, there should be steps outlining a manual approach in the setup guide.
Actual Result
Notice the following error when running line
require("@sentry/profiling-node")
in Fastify app:Notice that
@sentry/profiling-node
is trying to use a precompiled binary that does not exist. The dynamic path builder is evaluatingnode_os.arch()
toarm
, since I'm on 32-bit Linux. I see that only 64-bit precompiled binaries are provided.