{"push_id":844042254,"size":7,"distinct_size":1,"ref":"refs/heads/issue/2981","head":"7f1cc204b687db22c3e1f535c722b2414f0fcd89","before":"44c61a334b02fdc890a7eaaee1c58832fa31b6f4","commits":[{"sha":"fdeaa2931739406f56140fa96d71a6f63db84425","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Added new diagnostic trace to weaver analyzer showing how a declared synonym was resolved.","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/fdeaa2931739406f56140fa96d71a6f63db84425"},{"sha":"ec24ee8cc0c69996a3e03da4bb442207f23dd059","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Added new diagnostic traces revealing how we generate field accessors for synonyms.","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/ec24ee8cc0c69996a3e03da4bb442207f23dd059"},{"sha":"9883910a2f10bd49d0d749b726c563124fe00cf7","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Tweaked the weaver transformation task to get around the problem reported in #2997. Still don't understand how this could start happening, but I think its caused by something that has changed the order of classes/fields and how they are returned to us when we it iterate them during transformation. Probably caused by some new bits in PostSharp, and/or Visual Studio 2015. With this new approach, we assure fix the entire type specification in the first step, assuring field column handles are there when synonyms are later resolved.","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/9883910a2f10bd49d0d749b726c563124fe00cf7"},{"sha":"00f54a3f1b345eba9ab879eb1ce77acabe341e79","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Merge branch 'develop' into issue/2997","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/00f54a3f1b345eba9ab879eb1ce77acabe341e79"},{"sha":"cb135bf8a790fd633f4356a3afe05cb73c7bbc67","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Updated changelog to include the fix.","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/cb135bf8a790fd633f4356a3afe05cb73c7bbc67"},{"sha":"4a45cf732e96a17418441994ebfbd420b89e4e4f","author":{"email":"8205aed0c460f4ecd16c764157a7dd5afa286b11@starcounter.com","name":"Per Samuelsson"},"message":"Merge branch 'issue/2997' into develop. The described issue is now working, with the help of a redesign in the weaver transformation engine. I'm still not 100% what caused this, but everything I have found is that it was caused by some external change, most likely in PostSharp (we use a new version) and/or in VS 2015 (which we haven't tested much). With this, I consider #2997 fixed.","distinct":false,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/4a45cf732e96a17418441994ebfbd420b89e4e4f"},{"sha":"7f1cc204b687db22c3e1f535c722b2414f0fcd89","author":{"email":"d16f649c0852d5d8b35b95efe4784a8a5fa04b53@starcounter.com","name":"Christian Holmstrand"},"message":"Merge branch 'develop' into issue/2981","distinct":true,"url":"https://api.github.com/repos/Starcounter/Starcounter/commits/7f1cc204b687db22c3e1f535c722b2414f0fcd89"}]}