Metadata
- Source
- FLUID-5667
- Type
- Bug
- Priority
- Major
- Status
- Closed
- Resolution
- Fixed
- Assignee
- Antranig Basman
- Reporter
- Antranig Basman
- Created
2015-05-19T12:18:41.664-0400 - Updated
2017-02-27T15:49:14.756-0500 - Versions
- N/A
- Fixed Versions
-
- 2.0
- Component
-
- Framework
Description
FLUID-5088 and FLUID-4978 provide some measure of resistance to circularity during options expansion. However, there's an important case we haven't tackled - if the material to be expanded is ALREADY circular by the time it is referenced from the options material. This arose in the context of the gpii-express project where the following definition of a dynamic subcomponent:
timeoutResponse: {
createOnEvent: "onNewTimeoutRequest",
type: "gpii.express.tests.requestAware.request",
options: {
request: "{arguments}.0",
response: "{arguments}.1"
}
}
referred via "arguments" to the native express request and response objects. This caused a failure through memory exhaustion. In the browser, we get a "call stack exceeded" messages. This should be detected by a dedicated framework pathway which provides a readable diagnostic.
Comments
-
Antranig Basman commented
2015-08-20T15:08:49.254-0400 Merged into trunk at revision 282f1a318718eed0b0ec060fb8b4ad254417fd7e (sub-pull https://github.com/fluid-project/infusion/pull/604 )