Opened 8 years ago

Closed 7 years ago

#15321 closed defect (fixed)

async circular dependency loop - returns blank object - no obvious errors

Reported by: Karl Tiedt Owned by: Rawld Gill
Priority: low Milestone: 1.8
Component: Documentation Version: 1.7.2
Keywords: Cc:
Blocked By: Blocking:

Description

In trunk (and early 1.7) a dependency loop is very difficult to track down due to how the load responds to it.

http://ktiedt.dojotoolkit.org/dojo/deploop.html is a working page to demonstrate this behavior running off trunk.

Basically this returns a blank object much like what was fixed for sync loader it seems, but with no feedback that I found to help isolate the problem.

This may be a very edge case and be cause for a remodling of of this part of our application for async mode (worked prior to updating to AMD formats)

Change History (1)

comment:1 Changed 7 years ago by Rawld Gill

Component: LoaderDocumentation
Milestone: tbd1.8
Priority: undecidedlow
Resolution: fixed
Status: newclosed

The loader includes a tracing option to help with this. If you alter your dojoConfig in the example html file to look like this:

  data-dojo-config=
    "trace:{'loader-circular-dependency':1}, async:1, isDebug:true, packages:[{name:'test', location:'../test'}]"

Then you'll get the following output to the console:

trace:loader-circular-dependency:require*_1->test/dependsOnA->test/A->test/B->test/dependsOnA

I updated the docs to describe this switch (http://livedocs.dojotoolkit.org/loader/amd#tracing).

Note: See TracTickets for help on using tickets.