Skip to content
This repository has been archived by the owner on Jan 9, 2023. It is now read-only.

Async error on Imaging list #365

Closed
tangollama opened this issue Mar 16, 2016 · 4 comments
Closed

Async error on Imaging list #365

tangollama opened this issue Mar 16, 2016 · 4 comments
Labels
🐛bug issue/pull request that documents/fixes a bug

Comments

@tangollama
Copy link
Member

Expected behavior:
Imaging list renders.

Actual behavior:
Error: Assertion Failed: You looked up the 'patient' relationship on a 'imaging' with id 6C16C18A-1FCE-35A0-9777-47DD2F55C957 but some of the associated records were not loaded. Either make sure they are all loaded together with the parent record, or specify that the relationship is async (DS.belongsTo({ async: true }))
at new Error (native)
at Error.EmberError (http://localhost:4200/assets/vendor.js:26674:21)
at assert (http://localhost:4200/assets/vendor.js:16436:13)
at Object.assert (http://localhost:4200/assets/vendor.js:26438:34)
at assert (http://localhost:4200/assets/vendor.js:122930:37)
at BelongsToRelationship.getRecord (http://localhost:4200/assets/vendor.js:129287:41)
at get (http://localhost:4200/assets/vendor.js:128330:60)
at Descriptor.ComputedPropertyPrototype.get (http://localhost:4200/assets/vendor.js:25256:28)
at get (http://localhost:4200/assets/vendor.js:30915:19)
at call (http://localhost:4200/assets/vendor.js:146276:37)

Steps to reproduce:
/imaging

Screenshots (if applicable):
screen shot 2016-03-16 at 9 05 19 am

@tangollama tangollama added 🐛bug issue/pull request that documents/fixes a bug Imaging labels Mar 16, 2016
@rohansp
Copy link

rohansp commented Mar 20, 2016

Does this occur on the demo link https://beta.hospitalrun.io/#/imaging ? Cause there it seems to be working fine.. Is this a local issue?

@tangollama
Copy link
Member Author

@rohansp this appears to be an issues related to data deletion / migration. @jkleinsc is addressing from an architectural perspective. @jkleinsc do you think we should leave this open or assign to you?

@jkleinsc
Copy link
Member

@tangollama I think we could close this in favor of #381, but we should change that issue to be more generic - i.e. Flag records as archived instead of deleted.

@jkleinsc
Copy link
Member

Closing as this was resolved as part of #381

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🐛bug issue/pull request that documents/fixes a bug
Projects
None yet
Development

No branches or pull requests

3 participants