Page MenuHomePhabricator

UNRECOVERABLE FATAL ERROR -- PhabricatorProjectColumnPositionQuery::withColumns()
Closed, InvalidPublic

Description

Running Phabricator from GIT:

commit 56bd762dd3ed5ced1914c6f36fd58dab589ccb31

I've archived a Project and saw a task from that Project, and clicked on the Project tag, shown under the Tasks' label. The error was shown:

>>> UNRECOVERABLE FATAL ERROR <<<

Call to undefined method PhabricatorProjectColumnPositionQuery::withColumns()

/path/to/phabricator/libext/sprint/src/controller/board/SprintBoardViewController.php:181


┻━┻ ︵ ¯\_(ツ)_/¯ ︵ ┻━┻

URL:

https://<domain>/tag/<project-name>/

Running on Ubuntu Linux 14.04 LTS x64. Libraries arcanist and libphutil updated to GIT master on 19th July 2016.

Event Timeline

mibesis updated the task description. (Show Details)
chad added a subscriber: chad.

This isn't our code:

/path/to/phabricator/libext/sprint/src/controller/board/SprintBoardViewController.php:181

@chad Agree, but it is "in yours product/project". Does this does not count?

No, it's not our product. It's a third party extension. Please contact that maintainer for help.

@chad My bad, let me explain.

I've updated Phabricator few weeks ago (around July 19th). I did not update the "third party extension", as it was located inside ./phabricator/ folder.

Reading: https://secure.phabricator.com/book/phabricator/article/upgrading/ - there is no mention to upgrade "third party extension". Well, I do not remember I've installed this extension manually or not (I guess I must have done it), ether way - I forgot about this. I guess this should be obvious, but it was not - at the time of the update.

So, the solution is: update/pull extension source tree inside:

./phabricator/libext/sprint/
NOTE: When Phabricator is upgraded, keep also all the extensions up-to-date (inside phabricator folder) not just the sibling folders.

Task is closed, thanks @chad for pointing this out - this is third party extension.

Yeah, we don't support or recommend third-party extensions anywhere in the documentation. We're years away from that.