-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
facing issue in git checkout while upgrading to 24.1.1 to 24.1.2 #2802
Comments
@chadwhitacre @hubertdeng123 - Kindly help me with your suggestion here |
This is a normal Git error that you are experiencing. You made custom changes to this file, and git asks if you want to overwrite these. If the changes you have made to the Dockerfile are not relevant, you can do the following. |
Hi @balaG4046 I can't really deduct what your issue is from that clipped log. Can you show us the complete log? There should be a |
Hi @aldy505 Thanks! |
Oh, it's just the Sentry container got a connection lost issue during connecting to the Postgres container. It's probably because a bad hardware on your end. Since the second log file looks like everything is okay, I suppose you are running a normal working Sentry right now? If you don't have normal working Sentry running, try to check your server disk speed. |
Hi @aldy505 Thanks for looking in to our issue, We are using RDS Postgres 13.10, in our Sentry. We have replaced the below variables which was provided in sentry.conf.py SENTRY_DB_NAME Looks like in our log, it is trying to access default postgress container, Below Hardware specification for our Sentry Dev Environment (AWS Cloud) Instance type - m6a.4xlarge, Sentry is deployed via docker compose method. Kindly suggest us, what need to be done, if we are using external postgress like RDS in our case. Thanks! |
This is being discussed in another issue at the moment: #2804 Worth noting that Sentry is currently on postgres 14. This probably isn't the cause of this specific issue, but may be a problem down the line in other subtle ways. |
Will there be any upcoming fix for this issue? the same issue facing while upgrading to 24.2.0 as well from 24.1.1 |
I've put up this PR to help with self-hosted installs using external DBs. However, you can get around this by performing the sql commands manually yourself. |
@hubertdeng123 @aldy505 @BYK @azaslavsky Any new release for this fix coming soon? |
@praseeb I'm kind of lost here, what kind of issue are you experiencing right now? |
The fix to support non-default postgres db setups should be released soon. Thanks for your patience |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
#2827 is merged. Are we good here? |
Should be, and we've cut a release with the changes. |
Self-Hosted Version
24.1.1
CPU Architecture
x86_64
Docker Version
20.10.25
Docker Compose Version
2.16.0
Steps to Reproduce
while upgrading to 24.1.1 to 24.1.2 we are facing issue
error: Your local changes to the following files would be overwritten by checkout:
cron/Dockerfile
even for 24.2.0 also same issue - kindly help us to resolve the issue. @hubertdeng123 @chad
Expected Result
it should upgrade to 24.1.2
Actual Result
Event ID
No response
The text was updated successfully, but these errors were encountered: