Closed dylan-thinnes closed 7 years ago
My suspicions were true, adding process.nextTick on the server to make a this.childDone("init") call just before the }
solves the issue server-side. Unfortunately, it seems that the Profile assembler has broken. I'm not sure if it was ever really working in the first place...
Left in process.nextTick and disabled factorProfile to replace it with serverside piXDepth=1 configuration. May return to this later...
Numbers such as 233943789437 cause strange piX callback problems. I think it's an issue with the callback starting before the object is done initializing (before it reaches it's close
}
).