Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting "Uploading chunks to a relative url is not recommended" warning out of the blue. #1051

Closed
newhouse opened this issue Oct 19, 2021 · 1 comment · Fixed by #1054
Closed

Comments

@newhouse
Copy link

Environment

How do you use Sentry? Sentry SaaS

Which SDK and version?
NodeJS @sentry/cli version 1.69.1

Steps to Reproduce

  1. Create a release via yarn sentry-cli releases new
  2. Upload the sourcemaps via yarn sentry-cli releases --project <my-project-slug> files <my release> upload-sourcemaps /path/to/sourcemaps --validate --ignore /path/to/sourcemaps/exception.js
  3. Warning encountered: Uploading chunks to a relative url is not recommended. Please update your system.url-prefixconfiguration inside config.ymlor useRoot URL option at https://<sentry-url>/manage/settings/ directly.

Expected Result

No warning message would be printed.

Actual Result

The following warning was printed: Uploading chunks to a relative url is not recommended. Please update your system.url-prefixconfiguration inside config.ymlor useRoot URL option at https://<sentry-url>/manage/settings/ directly.

This just started happening out of the blue a few hours ago.
We have recently updated our Sentry CLI version, but this warning was not happening before - I am sure b/c it actually broke things for us when it started happening.
At first I thought it might be because we had triggered some size or number of files, but it seems to happen no matter what we're uploading.
Since we are not hosting Sentry ourselves, and this error just started out of the blue, all signs point to me to be a bug in this CLI that was brought about by a change/regression on your server side. Perhaps this issue here is illuminating?

@kamilogorek
Copy link
Contributor

kamilogorek commented Oct 20, 2021

Hello, thanks for reporting this issue. It indeed is a bug on sentry-cli side. However it is log only, so it shouldn't affect the behavior itself. It will be fixed here #1054

In the meantime, you can silence the output with SENTRY_LOG_LEVEL=error (or in .sentryclirc):

[log]
level=error

Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants