Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

I used our own nginx for GitLab, and I guess that's how it messed up the API calls. I don't know how to proceed to figure out the root cause, So I reinstalled Gitlab on another server using the built-in nginx, and it works... On Sunday, July 10, 2016 at 9:46:28 AM UTC+8, Yang Yu wrote: > > Hi

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi Christian, I've tried to restart the memcached, but it didn't work either. Could you point me to where I should look into more? I tried to add new projects to rb, but all editing on the old files are still showing patch failed. Sincerely, Yang On Sunday, June 12, 2016 at 2:04:38 PM UTC+8,

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi Yang, That's a different sort of cache from memcached, and isn't related to diffs. Can you try doing a full restart of memcached? Christian On Saturday, June 11, 2016, Yang Yu wrote: > I just upgraded RB to 2.5.6.1 and it still has the same problem: works > only for

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

I just upgraded RB to 2.5.6.1 and it still has the same problem: works only for brand new files... During the upgrade, it says "Resetting in-database caches.", so I assume there is no cache. Thanks, Yang On Sunday, June 12, 2016 at 11:37:57 AM UTC+8, Christian Hammond wrote: > > Hi, > > Try

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi, Try upgrading to the latest Review Board (2.5.6.1). We fixed some issues with GitLab, and we should start there before investigating too much further. Christian On Saturday, June 11, 2016, Yang Yu wrote: > Hi Christian, > > Thanks for replying! > > We are using

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi Christian, Thanks for replying! We are using Review Board 2.5.4. I'm using default configurations for GitLab. The following is what I see from the internal state: {"repository_plan": "personal", "hosting_url": "http://gitlab.ito.com.cn;, "use_ticket_auth": false, "bug_tracker_use_hosting":

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi, We cache file lookups from the repository. During diff generation, we check if we have the file contents from the repository in our cache. If so, we use that as the base for generating a side-by-side diff. If we don't have it, we talk to the repository, asking it for the file, given a path

Re: The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Just some additional thoughts. How does reviewboard talk to GitLab when displaying the diff? If there is no cache in reviewboard, then it's definitely something with GitLab and git cache. I remember this happened before when switching repos. On Friday, June 10, 2016 at 12:17:22 PM UTC+8,

The classic "The patch to 'build.gradle' didn't apply cleanly" problem for existing files

Hi there, So, we originally installed RB and GitLab on our own hosts and access them through IP. Yesterday, we start to use domain names instead of IPs. 1. The GitLab repo addr changed from 111.111.*/repo to domain.com/repo 2. I changed the repo settings in reviewboard to point to the new