Fix a write on read situation #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jensens
added
22 status: in-progress
04 type: enhancement
11 prio: blocker
24 status: ready
and removed
22 status: in-progress
labels
|
merge together with other, see coredev4 above |
4 tasks
|
tests in 4.3 may fail, see above, in 5.0 it should be fine |
If the context gets its first annotation it need to be marked as safe to write. The same goes for the annotations on the object.
gforcada
force-pushed
the
write-on-read
branch
from
0ca2bcb to
dac1655
Compare
This was referenced Feb 21, 2016
|
Running tests together with plone/plone.protect#39 here for Plone 5: http://jenkins.plone.org/job/pull-request-5.0/942/ |
mauritsvanrees
added a commit
that referenced
this pull request
Feb 25, 2016
Fix a write on read situation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
see plone/buildout.coredev#150
If the context gets its first annotation it need to be marked as
safe to write.
The same goes for the annotations on the object.