New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Track component changes like resource changes #116
Conversation
Guvante
commented
Mar 8, 2020
- Track reads as well as writes
- Writes are dependent on reads to avoid simultanious execution
- Reads handled after writes to prevent overriting last read
Mostly stole the way it was being done for resources. I think revisiting whether read and write for components is good is worthwhile but figured a bug fix that didn't require deciding on that was good. |
a863251
to
fcb2d9c
Compare
@TimonPost yep, this would be where we missed a check. Makes sense, I oopsied. @Guvante can you add Timon's example in #114 as a test in here so we can have a regression test? |
@jaynus I just tried those changes in my own project but still get the same error. Playing with system order doesn't matter. I try to reproduce this with the mini-example again. It does not occur there. Strange ... |
I might have found an issue in my code. So wait before putting in more research time. |
It happens when I add My guess would be that this system with write access is qued in parallel with the systems using it in there read query. Which will result in this type being borrowed immutable. |
I am not sure what is wrong with CI at the moment, it seems to be having trouble checking out the repo. I have ran the CI tests locally though and they all pass. |
Hmm, it looks like EDIT: I feel silly. The test inserts |
- Track reads as well as writes - Writes are dependent on reads to avoid simultanious execution - Reads handled after writes to prevent overriting last read
fcb2d9c
to
e2b9216
Compare
The tests now pass so this should be good to go. |