Metadata
- Source
- DECA-251
- Type
- Bug
- Priority
- Blocker
- Status
- Closed
- Resolution
- Fixed
- Assignee
- N/A
- Reporter
- Justin Obara
- Created
2012-05-14T14:57:18.124-0400 - Updated
2012-05-18T14:47:12.873-0400 - Versions
- N/A
- Fixed Versions
-
- 0.5
- Component
-
- Export
Description
The unit tests are passing in Chrome, so it is likely a timing issue.
Environments
FF 12 (Ubuntu 10.04)
Comments
-
Justin Obara commented
2012-05-15T10:49:49.336-0400 In chatting with Antranig (Bosmon) today in the channel, it seems that the cause is an extra bit of asynchrony imposed on subsequent calls to fluid.fetchResources. Since I've already fetched the resources and am passing them along wholesale, I'll just refactor the code to not call fetchResources if they are already provided.
http://wiki.fluidproject.org/display/fluid/fluid-work+IRC+Logs-2012-05-15
-
Justin Obara commented
2012-05-15T16:23:03.225-0400 Made the changes as described above. Created a wrapper function around fluid.fetchResources that checks first if the resourceText exists and will divert to just calling the call back function if it does. Also had to change the startImport tests to trigger on the afterExportersReady event instead of onReady.
The changes are in my bitbucket repo:
https://bitbucket.org/jobara/decapod-ui-05release -
Justin Obara commented
2012-05-18T14:47:09.621-0400 Merged into the project repo