I don't quite think I'm groking your request. You want screen caps of "Home › Django_evolution › Versions › Hinted version, updated on 2011-06-30 20:16:00" and "Home › Django_evolution › Versions › Stored version, updated on 2011-06-30 20:16:00"? I just looked at those and they look rather uninteresting, due to the default text field size. The text field is only 10 rows tall.
As for DB dumps, what are the chances that they could contain identifying or interesting information about my company? If greater than 0, we'll have to discuss that off list. On Fri, Jul 29, 2011 at 2:52 AM, Christian Hammond <chip...@chipx86.com> wrote: > I have a script now that can simulate various database upgrade scenarios, > and have spent lots of time with it now. I've yet to be able to reproduce > this. I've tried sqlite and MySQL, Python versions 2.4 through 2.6, and > various combinations of Review Board versions. > > I am curious about the Hinted entry. I would very much like to be able to > get a dump of the contents of that, straight from the database if possible. > Same with the Stored of the same date. > > Could you provide a screenshot from the admin UI too for both? > > To be quite frank, it looks very much like unintentional user error at some > point caused by playing with versions. However, given that there have been a > few reports (3, maybe 4) of similar things, I'm eager to figure out exactly > what is happening. These aren't problems we've encountered in the past from > a user's typical upgrade. > > Christian > > -- > Christian Hammond - chip...@chipx86.com > Review Board - http://www.reviewboard.org > VMware, Inc. - http://www.vmware.com > > > On Wed, Jul 27, 2011 at 10:44 PM, Christian Hammond <chip...@chipx86.com> > wrote: >> >> I wouldn't expect a hint + stored evolutions to be updated at the same >> time. Usually it's one or the other. >> >> The common denominators in the cases I've seen where people have hit this >> are Python 2.4 and MySQL, so I'll run some tests and see if I can reproduce >> this somehow. >> >> Christian >> >> -- >> Christian Hammond - chip...@chipx86.com >> Review Board - http://www.reviewboard.org >> VMware, Inc. - http://www.vmware.com >> >> >> On Wed, Jul 27, 2011 at 7:25 PM, Tucker <j...@gmail.com> wrote: >>> >>> I don't recall having run that but it doesn't mean I didn't. I >>> believe the upgrade from beta1 to RC1 may have complained. It's >>> possible reran the upgrade script or, if it told me to run "evolve >>> --hint --execute," I did. I'm almost positive I never rolled back to >>> a previous revision. Is it normal that the stored version and hinted >>> version were updated at identical times? >>> >>> If there's anything potentially destructive you'd like me to try, to >>> assist in investigation, I can do this. This is my test server and my >>> production server won't be upgraded from beta1 until the next full >>> release. >>> >>> On Wed, Jul 27, 2011 at 4:30 PM, Christian Hammond <chip...@chipx86.com> >>> wrote: >>> > Okay, I suspect this is somehow due to you having at some point ran >>> > evolve >>> > --hint --execute. The "Versions" list shows a hint was applied, and I'd >>> > be >>> > interested in seeing what the contents of that was (it'll be mostly >>> > giberish >>> > though). >>> > >>> > You do, however, appear to have migrations for the changes listed in >>> > the >>> > error. So that's confusing. >>> > >>> > Do you remember ever running evolve --hint --execute? Did you at any >>> > point >>> > go back to a previous release/commit? >>> > >>> > Christian >>> > >>> > -- >>> > Christian Hammond - chip...@chipx86.com >>> > Review Board - http://www.reviewboard.org >>> > VMware, Inc. - http://www.vmware.com >>> > >>> > >>> > On Wed, Jul 27, 2011 at 2:34 PM, Tucker <j...@gmail.com> wrote: >>> >> >>> >> It actually is my address. It matches what used to be my @google.com >>> >> address. >>> >> >>> >> * Started with 1.6RC1. >>> >> * Using MySQL >>> >> * Output of --hint >>> >> >>> >> """ >>> >> $ sudo rb-site manage /var/www/sites/reviews-dev evolve -- --hint >>> >> Password: >>> >> #----- Evolution for accounts >>> >> from django_evolution.mutations import * >>> >> from django.db import models >>> >> >>> >> MUTATIONS = [ >>> >> AddField('Profile', 'is_private', models.BooleanField, >>> >> initial=False) >>> >> ] >>> >> #---------------------- >>> >> #----- Evolution for reviews >>> >> from django_evolution.mutations import * >>> >> from django.db import models >>> >> >>> >> MUTATIONS = [ >>> >> AddField('ReviewRequest', 'inactive_file_attachments', >>> >> models.ManyToManyField, related_model='attachments.FileAttachment'), >>> >> AddField('ReviewRequest', 'file_attachments', >>> >> models.ManyToManyField, related_model='attachments.FileAttachment'), >>> >> AddField('Review', 'file_attachment_comments', >>> >> models.ManyToManyField, >>> >> related_model='reviews.FileAttachmentComment'), >>> >> AddField('ReviewRequestDraft', 'inactive_file_attachments', >>> >> models.ManyToManyField, related_model='attachments.FileAttachment'), >>> >> AddField('ReviewRequestDraft', 'file_attachments', >>> >> models.ManyToManyField, related_model='attachments.FileAttachment') >>> >> ] >>> >> #---------------------- >>> >> Trial evolution successful. >>> >> Run './manage.py evolve --hint --execute' to apply evolution. >>> >> """ >>> >> >>> >> * Dump attached >>> >> * Screenshots attached >>> >> * Python django ouput >>> >> >>> >> """ >>> >> Python 2.4.3 (#1, May 24 2008, 13:57:05) >>> >> [GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2 >>> >> Type "help", "copyright", "credits" or "license" for more information. >>> >> >>> import django >>> >> >>> print django.VERSION >>> >> (1, 3, 0, 'final', 0) >>> >> """ >>> >> >>> >> >>> >> On Tue, Jul 26, 2011 at 2:41 PM, Christian Hammond >>> >> <chip...@chipx86.com> >>> >> wrote: >>> >> > Hi Tucker, >>> >> > >>> >> > (Is j...@gmail.com really your e-mail address?) >>> >> > >>> >> > This is something I've seen a few times now and still haven't >>> >> > figured >>> >> > out >>> >> > the cause of. Can I have you answer the questions in this bug >>> >> > report: >>> >> > >>> >> > http://code.google.com/p/reviewboard/issues/detail?id=2186 >>> >> > >>> >> > It'll help us figure out what's causing this. >>> >> > >>> >> > Christian >>> >> > >>> >> > -- >>> >> > Christian Hammond - chip...@chipx86.com >>> >> > Review Board - http://www.reviewboard.org >>> >> > VMware, Inc. - http://www.vmware.com >>> >> > >>> >> > >>> >> > On Tue, Jul 26, 2011 at 1:22 PM, Tucker <j...@gmail.com> wrote: >>> >> >> >>> >> >> Attempted an upgrade from RC1 to RC2. >>> >> >> >>> >> >> 1. easy_install -U ReviewBoard >>> >> >> 2. easy_install -U RBTools >>> >> >> 3. rb-site upgrade /var/www/sites/reviews-dev.zynga.com/ >>> >> >> >>> >> >> And this is where it broke: >>> >> >> >>> >> >> # rb-site upgrade /var/www/sites/reviews-dev.zynga.com/ >>> >> >> Rebuilding directory structure >>> >> >> Updating database. This may take a while. >>> >> >> Creating tables ... >>> >> >> There are unapplied evolutions for diffviewer. >>> >> >> Project signature has changed - an evolution is required >>> >> >> Installing custom SQL ... >>> >> >> Installing indexes ... >>> >> >> No fixtures found. >>> >> >> >>> >> >> >>> >> >> >>> >> >> /usr/lib/python2.4/site-packages/pycrypto-2.3-py2.4-linux-x86_64.egg/Crypto/Util/randpool.py:40: >>> >> >> RandomPool_DeprecationWarning: This application uses RandomPool, >>> >> >> which >>> >> >> is BROKEN in older releases. See >>> >> >> http://www.pycrypto.org/randpool-broken >>> >> >> Unable to load SCMTool perforce = >>> >> >> reviewboard.scmtools.perforce:PerforceTool: invalid syntax >>> >> >> (perforce.py, line 155) >>> >> >> The stored evolutions do not completely resolve all model changes. >>> >> >> Run `./manage.py evolve --hint` to see a suggestion for the changes >>> >> >> required. >>> >> >> >>> >> >> The following are the changes that could not be resolved: >>> >> >> In model reviews.ReviewRequest: >>> >> >> Field 'inactive_file_attachments' has been added >>> >> >> Field 'file_attachments' has been added >>> >> >> In model reviews.Review: >>> >> >> Field 'file_attachment_comments' has been added >>> >> >> In model reviews.ReviewRequestDraft: >>> >> >> Field 'inactive_file_attachments' has been added >>> >> >> Field 'file_attachments' has been added >>> >> >> In model accounts.Profile: >>> >> >> Field 'is_private' has been added >>> >> >> Error: Your models contain changes that Django Evolution cannot >>> >> >> resolve automatically. >>> >> >> >>> >> >> I haven't run the evolve script at all, which was a question I saw >>> >> >> come up in a similar thread. The host is running CentOS 5.2 and >>> >> >> python2.4. This machine was originally running beta1 and was then >>> >> >> upgraded to RC1, without a problem. It is a dev host, so there's a >>> >> >> possibility that something was done to the machine that was >>> >> >> unrelated >>> >> >> but had an impact. >>> >> >> >>> >> >> -- >>> >> >> >>> >> >> --tucker >>> >> >> >>> >> >> -- >>> >> >> Want to help the Review Board project? Donate today at >>> >> >> http://www.reviewboard.org/donate/ >>> >> >> Happy user? Let us know at http://www.reviewboard.org/users/ >>> >> >> -~----------~----~----~----~------~----~------~--~--- >>> >> >> To unsubscribe from this group, send email to >>> >> >> reviewboard+unsubscr...@googlegroups.com >>> >> >> For more options, visit this group at >>> >> >> http://groups.google.com/group/reviewboard?hl=en >>> >> > >>> >> > -- >>> >> > Want to help the Review Board project? Donate today at >>> >> > http://www.reviewboard.org/donate/ >>> >> > Happy user? Let us know at http://www.reviewboard.org/users/ >>> >> > -~----------~----~----~----~------~----~------~--~--- >>> >> > To unsubscribe from this group, send email to >>> >> > reviewboard+unsubscr...@googlegroups.com >>> >> > For more options, visit this group at >>> >> > http://groups.google.com/group/reviewboard?hl=en >>> >> >>> >> >>> >> >>> >> -- >>> >> >>> >> --tucker >>> >> >>> >> -- >>> >> Want to help the Review Board project? Donate today at >>> >> http://www.reviewboard.org/donate/ >>> >> Happy user? Let us know at http://www.reviewboard.org/users/ >>> >> -~----------~----~----~----~------~----~------~--~--- >>> >> To unsubscribe from this group, send email to >>> >> reviewboard+unsubscr...@googlegroups.com >>> >> For more options, visit this group at >>> >> http://groups.google.com/group/reviewboard?hl=en >>> > >>> > -- >>> > Want to help the Review Board project? Donate today at >>> > http://www.reviewboard.org/donate/ >>> > Happy user? Let us know at http://www.reviewboard.org/users/ >>> > -~----------~----~----~----~------~----~------~--~--- >>> > To unsubscribe from this group, send email to >>> > reviewboard+unsubscr...@googlegroups.com >>> > For more options, visit this group at >>> > http://groups.google.com/group/reviewboard?hl=en >>> >>> >>> >>> -- >>> >>> --tucker >>> >>> -- >>> Want to help the Review Board project? Donate today at >>> http://www.reviewboard.org/donate/ >>> Happy user? Let us know at http://www.reviewboard.org/users/ >>> -~----------~----~----~----~------~----~------~--~--- >>> To unsubscribe from this group, send email to >>> reviewboard+unsubscr...@googlegroups.com >>> For more options, visit this group at >>> http://groups.google.com/group/reviewboard?hl=en > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > reviewboard+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en -- --tucker -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
