Status: New
Owner: ----
Labels: Type-Defect Priority-Low Component-Other
New issue 1871 by [email protected]: Creating a Rietveld issue is less
atomic than it should be
http://code.google.com/p/google-caja/issues/detail?id=1871
What steps will reproduce the problem?
1. Run 'myvn mail' or 'myvn snapshot' to create an issue.
2. Have a network or server failure occur while uploading changes/base
files.
What is the expected output? What do you see instead?
The issue will have been created, and its URL printed, but the issue ID is
not inserted in the .appspot-change file. This means that retrying will
result in creating a duplicate issue.
appspot.py should write the .appspot-change file as soon as the Rietveld
server gives us the change ID, not after doing other operations that might
fail.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
