Bug #5371
open
Comment times in Pull Requests are off by 1 day
Added by Evan Ward over 7 years ago.
Updated over 6 years ago.
Description
On a comment I just submitted I see:
note ward | 1 day ago | pull request #28
I would expect to see something like
note ward | 5 minutes ago | pull request #28
since I just submitted it.
I'm using RhodeCode Enterprise 4.8.0
Files
Hi Evan,
THis might be related to different timezone set on the server and Database, can you check if those are the same ?
Best
OK, how do I check that? The database and web server are on the same machine.
Hi Evan,
Sorry it took us so long, but we finally manage to look at this issue, and find potential solution. Because of nature of this task, we'd like to test this on your enviroment. Is it possible we could offer you a patch to test on your instance ?
I can test a patch as long as it is easy to revert and won't cause a large disruption.
Hi Evan,
The changes require are simple, and can be very easily reverted. Before i send you the patch and instructions, can you tell me what is your timezone on the server ?
e.g 'US/Central' ?
US/Eastern same as New York.
Evan,
Here are the instructions:
cd .rccontrol/enterprise-1/profile/etc/rhodecode_enterprise_ce_source/lib/python2.7/site-packages
copy over the example_patchfile.diff into that location
check if patch applies correctly
patch -p1 --dry-run -i example_patchfile.diff
# there should be no failed hunks.
# if that is true, proceed with execution.
patch -p1 -i patchfile.diff
# finally all the files that matched
# patching file <some_path>
# needs their .pyc cached files removed.
e.g
patching file rhodecode/lib/vcs/backends/base.py
...
so we need to remove
rm rhodecode/lib/vcs/backends/base.pyc
# in case of any problems, patches can be removed by doing.
# rccontrol upgrade --force --version=X.Y.Z <name of instance>
# e.g rccontrol upgrade --force --version 4.10.6 enterprise-1
# where X.Y.Z is your RhodeCode Version, e.g 4.10.6
After that please restart rhodecode by doing:
rccontrol restart '*'
That worked! Comment times now appear to be correct.
Hi Evan,
Thanks for checking and sending us your confirmation. We'll include this fix in the next release. You can keep the patch applied it will be automatically overwritten by next version when you do an upgrade.
Best,
Also available in: Atom
PDF
Updated by 
Updated by