search

getsentry / sentry-cli

A command line utility to work with Sentry.
https://docs.sentry.io/cli/
BSD 3-Clause "New" or "Revised" License
899 stars 221 forks source link

Unable to bundle sources to be send from a Linux Environment #2186

Open jopheno opened 3 days ago

jopheno commented 3 days ago

CLI Version

sentry-cli 2.37.0

Operating System and Architecture

Operating System Version

Ubuntu 22.04.3 LTS

Link to reproduction repository

No response

CLI Command

sentry-cli --log-level=debug debug-files bundle-sources .

Exact Reproduction Steps

Using a native C++ application (I used GDB to check if symbols were missing or if the source path was somehow wrong, but gdb was able to see all the sources just fine...)

Expected Results

It should correctly generate the source bundle debug files that would be uploaded to the sentry backend, but it didn't work;

Actual Results

jopheno@lnx-tlm-dev:~/repo/tlm-server$ ./tools/sentry-cli --log-level=debug debug-files bundle-sources .
  INFO    2024-10-18 21:44:48.306920627 +00:00 Loaded config from /home/jopheno/repo/tlm-server/.sentryclirc
  DEBUG   2024-10-18 21:44:48.307030067 +00:00 sentry-cli version: 2.37.0, platform: "linux", architecture: "x86_64"
  INFO    2024-10-18 21:44:48.308006929 +00:00 sentry-cli was invoked with the following command line: "./tools/sentry-cli" "--log-level=debug" "debug-files" "bundle-sources" "."
error: No such device (os error 19)
  INFO    2024-10-18 21:44:48.310324091 +00:00 Skipping update nagger update check

I am unsure if I am using it wrongly, but I have no idea what No such device means, if I indeed add a path that doesn't exists, it does say No such file or directory, but passing the executable, or the path where the executable is, or any path at all grants me with No such device (os error 19)

Even tried adding a symbolic link so that I could execute using sentry-cli directly instead of having to pass the whole repository; Got no results;

Logs

jopheno@lnx-tlm-dev:~/repo/tlm-server$ ./tools/sentry-cli --log-level=debug debug-files bundle-sources .
  INFO    2024-10-18 21:44:48.306920627 +00:00 Loaded config from /home/jopheno/repo/tlm-server/.sentryclirc
  DEBUG   2024-10-18 21:44:48.307030067 +00:00 sentry-cli version: 2.37.0, platform: "linux", architecture: "x86_64"
  INFO    2024-10-18 21:44:48.308006929 +00:00 sentry-cli was invoked with the following command line: "./tools/sentry-cli" "--log-level=debug" "debug-files" "bundle-sources" "."
error: No such device (os error 19)
  INFO    2024-10-18 21:44:48.310324091 +00:00 Skipping update nagger update check
szokeasaurusrex commented 16 hours ago

@jopheno I am not really sure where this error is coming from. Could you perhaps try uploading your debug files using this command, instead:

sentry-cli debug-files upload --include-sources /path/to/files

When using the --include-sources flag with debug-files upload, the Sentry CLI automatically creates the source bundles when uploading the debug files, so you do not need to call sentry-cli debug-files bundle-sources.

Please let me know whether this suggestion fixes your problem.