Page MenuHomePhabricator

db schema error
Closed, InvalidPublic

Assigned To
None
Authored By
dainysunil
Mar 28 2017, 8:23 AM
Referenced Files
F4323039: Phab_Version.png
Mar 29 2017, 5:39 AM
F4300049: phab_issue.png
Mar 28 2017, 8:23 AM
F4300051: phab_err1.png
Mar 28 2017, 8:23 AM

Description

While upgrading phabricator, there is a schema error with the db.
Verifying database schemata on "localhost:3306"...
Found no adjustments for schemata.

Target Error
phabricator_differential.differential_revision.properties Wrong Nullable Setting
Find attached screen shots

phab_err1.png (900×1 px, 291 KB)

phab_issue.png (900×1 px, 104 KB)

Event Timeline

epriestley added a subscriber: epriestley.

If you believe you've found a bug in Phabricator, we need all the information discussed in Contributing Bug Reports to move forward. Specifically:

See Support Resources for other ways to get help if you can't provide this information.

@epristley

Please find the image with upgrade branch. While upgrading the phabricator from this branch we found this error. Please check this upgrade to reproduce the error.

Phab_Version.png (900×1 px, 212 KB)

We don't accept bug reports without reproduction steps.

@chad you need to try upgrade phabricator from branch abff6dc8a9b4e081d74beaf8f062223cb5308ec3 to reproduce the issue. Can you consider this as step to reproduce the error.

If you believe those are the full, complete steps to reproduce the issue then please take the time and launch a clean test environment and follow the steps and let us know if they are complete.

My only guess here is something is corrupt, incomplete, or not upgraded properly. I don't see anything on our side that would lead to this state.

@chad -we tried the upgrade once again .. but the issue is still there

@dainysunil you need to provide full instructions to reproduce this issue in an untainted environment.

You're referring to your local environment where the upgrade fails, but as long as there's no way for the Phacility team to reproduce this issue in a generic environment there's no way to further investigate and possibly fix it.

We don't know how to reproduce this.