Skip to content
This repository has been archived by the owner on Jun 4, 2020. It is now read-only.

Build page template error #25

Open
maxg opened this issue Oct 5, 2014 · 4 comments
Open

Build page template error #25

maxg opened this issue Oct 5, 2014 · 4 comments

Comments

@maxg
Copy link
Owner

maxg commented Oct 5, 2014

/var/didit/views/build.jade:94
    92|   h3 #{suite.package}#{suite.package ? '.' : ''}#{suite.name} 
    93|     mixin testcounts(suite)
  > 94|   p= suite.properties.desc
    95|   ul
    96|     each test in suite.testcases
    97|       li
    Cannot call method 'escape' of null
@scotttmiller
Copy link

Max -- did you find a resolution to this jade error? I find no other references to this error via Google and am encountering it our project

@maxg
Copy link
Owner Author

maxg commented Jun 3, 2015

I don't have a fix. I haven't been able to reproduce the bug, and it occurs only very rarely in production.

We've been using an old version of Jade, so I'm planning to update and see whether the error still occurs (see 784922a, although that version is already now behind).

@scotttmiller
Copy link

Thanks for your reply -- we still see the same error on the latest version of Jade. We are updating other dependencies in our project (NodeJS, Mongoose, and on and on...) to see whether it gets sideswiped by going current on all of those. Just thought it worth mentioning that upgrading Jade did not fix it for us.

In our situation, what's happening is a piece of javascript that often corresponds to several dynamically assembled method calls for rendering page fragments is passed a Jade rendering object that, for some unknown reason, gets nulled out somewhere in the middle of the rendering the page. There is one particular mixin we have that triggers this issue across several different page types, and we have no idea why. We're wondering whether the reference to the jade renderer is getting garbage collected or perhaps an error is being handled badly deep within Jade, Node, or even V8.

Please do respond if anything you do seems to fix it -- I'll do likewise.

@robertleeplummerjr
Copy link

If it was a cleanup issue, wouldn't it be undefined other than null?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants