Re: Failed upgrade to RC2
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.comwrote:
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
Re: Failed upgrade to RC2
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
Re: Failed upgrade to RC2
For the screenshots, I was interested in a field that it turns out isn't
shown in the admin UI. So nevermind on that.
Feel free to send the raw dumps to me directly. They don't contain any
identifying information, just database table schema data, but no need to
attach them publicly either.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Fri, Jul 29, 2011 at 12:25 PM, Tucker j...@gmail.com wrote:
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',
