[Bf-committers] Multiview branch, updated status

Dalai Felinto dfelinto at gmail.com
Mon Nov 24 01:47:10 CET 2014

Hi Campbell,

I just tried to 'arc diff' a squashed version of the branch, but I
think it's too big for Phabricator.

The error I get is:
No unit test engine is configured for this project.
[HTTP/500] Internal Server Error
As received by the server, this request had a nonzero content length
but no POST data.

Normally, this indicates that it exceeds the 'post_max_size' setting
in the PHP configuration on the server. Increase the 'post_max_size'
setting or reduce the size of the request.

Request size according to 'Content-Length' was '9781018',
'post_max_size' is set to '8M'.

Any suggestions?


2014-11-22 15:40 GMT-02:00 Campbell Barton <ideasman42 at gmail.com>:
> Hi Dalai, even with the small todo's left, its probably worth doing a
> first pass review.
> I'll go over the branch Monday, Sergey can take a look this week too.
> IIRC the policy is not to use tracker for branches, but we could
> re-visit that and associate reports with a branch so its not clogging
> up the tracker and mixing bugs from master.
> On Sat, Nov 22, 2014 at 5:26 PM, Dalai Felinto <dfelinto at gmail.com> wrote:
>> Hi,
>> This email is to address the point raised in the previous dev meeting.
>> Since I won't be online tomorrow here are my thoughts.
>> (from dev meeting)
>> "Note, officially Multiview has to migrate to master this week, has
>> that been planned?"
>> I think multiview can be merged to master if blender as it is (with
>> 'Views" disabled) works as before (absolutely no regression and no
>> crashes). So the user that doesn't touch the "Views" panel shouldn't
>> experience any differences. That also means that, if due to
>> instability or  plain simple bugs, we think it's not ready for 2.73 we
>> can hide the UI panels and no harm is done.
>> At the moment there is only one known issue for that milestone, which
>> is proxies in the Sequencer. I started looking at it today, but I will
>> have to resume working on it on Monday only.
>> That means that, as soon as proxy is working (again, in non-multiview
>> mode), I can send the code for review and we merge as soon as another
>> core developer approves it.
>> After that, for multiview itself the missing bits are: proxies in
>> sequencer, some usability todos and other small bugs (e.g., to filter
>> out _L or _R when adding image strips).
>> Meanwhile if anyone wants to help testing it, (specially the
>> 'non-multiview' mode), there are builds for the 3 major platforms in
>> 64 bits:
>> Win 64: http://goo.gl/eucBWf
>> Linux: http://goo.gl/zOeGD0
>> OSX: http://goo.gl/1b6XmD
>> (if you want to build it yourself the branch is 'multiview' in the
>> official git.blender.org server)
>> I've been using my own github repository to collect bugs, but I guess
>> you can send me an email directly to report an issue in case you don't
>> have a github account.
>> https://github.com/dfelinto/blender/issues
>> (or we could use the blender tracker, but I'm not sure what is our
>> policy on reporting bugs in branches).
>> Thanks!
>> Dalai
>> --
>> blendernetwork.org/dalai-felinto
>> www.dalaifelinto.com
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
> --
> - Campbell
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers

More information about the Bf-committers mailing list