Error: Macro BackLinksMenu(None) failed

compressed data is corrupt

Error: Macro TicketQuery(summary=PRO_LIB_LOCAL_CHANGE_SERVER_R0, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|) failed

current transaction is aborted, commands ignored until end of transaction block

Analysis

^{(Give as much as possible of the needed information for designing and implementing the task in the following sections.)}

Overview

^{(Provide a brief overview of the whole task in its first revision. Stick to the current revision of the task, but keep an eye to the whole task progress, and stay alert for possible smells.)}

Task requirements

^{(List the necessary requirements that the task must fulfill.)}

Task result

^{(List the end product of the task (for example "Source code", "Wiki page", etc.))}

Implementation idea

^{(Provide some rough implementation idea(s).)}

Related

PRO_CHANGE_MANAGER_R0

How to demo

^{(Provide instructions for demonstration of the task.)}

Design

^{(Describe your design here.)}

Implementation

^{(Describe and link the implementation results here (from the wiki or the repository).)}

Testing

^{(Place the testing results here.)}

Comments

provide a local change server simulate multi-user actions if possible get the concept about how we're going to deal with collaboration common approach is to have remote proxy objects, when you set them and the server recieves it instead of this, we won't have proxy objects, but real objects. We won't transfer just he values, we'll transfer changes, instead of setting the frame to 5, we'll have a change server that will collect the changes and periodically sync the changes, change server is on client and server, merges changes, this is the server that is on the client, should work without internet connectivity. Modify resource, generates changes, change manager adds them to the change server