The hazards of writing email on the critical path:)
My screen is NOT tall enough for me to see the loop:)My screen is tall enough for me to see the loop:)
Another good problem ;-)
I see that you are using a number public projects intermixed with your own projects, so I'm going to guess that the loop is introduced by one of your projects. The public projects don't usually have undetected load loops ...
I'm guessing you mean "personal" rather than private, because I think all the dependencies are publicly accessible.
I should have said that public projects don't usually have
undetected load loops when the standard entry points are used,
otherwise they would have been reported and fixed.
Magritte, OSSubProcess, Grease, NeoCsv are used in a number of
places without hitting loops, but the fact that these projects
appear to be part of the loop leads me to believe the the loop is
introduce in one of "your projects" ---
I see that you are using very few public projects without a
personal fork and I would be suspicious of any changes that you
have made to the baselines of these projects ...
Oh look almost all of the projects involved in the loop seem to involve *-CompatibleUserName baselines and those are all presumably additions that you have made and the loop is almost certainly in the customization that you've done in those baselines ...
The log doesn't have information about the first entry point into the *-CompatibleUserName baselines in your load, but I would look very closely at that first entry point and find the other projects involved in the loop and find the one that uses the same entry point ...
Dale
| Free forum by Nabble | Edit this page |