{"action":"created","issue":{"url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/81","labels_url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/81/labels{/name}","comments_url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/81/comments","events_url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/81/events","html_url":"https://github.com/dragonjet/KC3Kai/issues/81","id":76748384,"number":81,"title":"Bugs found in Events sortie debrief","user":{"login":"BWinkKeyShellDinkInc","id":12371701,"avatar_url":"https://avatars.githubusercontent.com/u/12371701?v=3","gravatar_id":"","url":"https://api.github.com/users/BWinkKeyShellDinkInc","html_url":"https://github.com/BWinkKeyShellDinkInc","followers_url":"https://api.github.com/users/BWinkKeyShellDinkInc/followers","following_url":"https://api.github.com/users/BWinkKeyShellDinkInc/following{/other_user}","gists_url":"https://api.github.com/users/BWinkKeyShellDinkInc/gists{/gist_id}","starred_url":"https://api.github.com/users/BWinkKeyShellDinkInc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BWinkKeyShellDinkInc/subscriptions","organizations_url":"https://api.github.com/users/BWinkKeyShellDinkInc/orgs","repos_url":"https://api.github.com/users/BWinkKeyShellDinkInc/repos","events_url":"https://api.github.com/users/BWinkKeyShellDinkInc/events{/privacy}","received_events_url":"https://api.github.com/users/BWinkKeyShellDinkInc/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-15T14:43:26Z","updated_at":"2015-05-16T12:39:17Z","closed_at":null,"body":"The following bugs are found under the Events section of Strategy Room.\r\n\r\n* Repeated main fleet composition on pre/boss support fleet in event debrief and wrong fleet composition on pre/boss support fleet\r\n\r\nPictures:\r\n1: http://i.imgur.com/71jMBYy.png\r\n2: http://i.imgur.com/5cuBpN2.png\r\n3: http://i.imgur.com/feM5GLE.png\r\n\r\nI suspect it is due to KC3(require confirmation) is coded to read fleet 2 as \"PreB Sup\" and 3 as \"Boss Sup\". I deduced this as I remembered that the fleet composition for \"Boss Sup\" in Pic 1 is actually my fleet for expedition 12#, my actual \"PreB Sup\" composition is the composition for \"Boss Sup\" in Pic 3 and actual \"Boss Sup\" composition is the composition for \"PreB Sup\" in Pic 2. Hence it may explain the reason for repeated or wrong fleet composition. I will conduct a few tests to confirm on it and I will submit my findings here.\r\n\r\n* Repeated fleet composition of older sorties debrief on newer sorties debrief \r\n\r\nI found another bug while writing the report for the one above. The following pictures are the steps I used to recreate it.\r\n\r\n1. http://i.imgur.com/evtDy9O.png\r\n2. http://i.imgur.com/HQprdxd.png\r\n3. http://i.imgur.com/prG2CXw.png\r\n4. http://i.imgur.com/G9VDAWg.png\r\n\r\nPic 4 just shows that other debriefs are also affected after opening debrief 5# (the older, if not the oldest, event debrief in my strategy room). This can be fixed just by refreshing the page."},"comment":{"url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/comments/102623595","html_url":"https://github.com/dragonjet/KC3Kai/issues/81#issuecomment-102623595","issue_url":"https://api.github.com/repos/dragonjet/KC3Kai/issues/81","id":102623595,"user":{"login":"BWinkKeyShellDinkInc","id":12371701,"avatar_url":"https://avatars.githubusercontent.com/u/12371701?v=3","gravatar_id":"","url":"https://api.github.com/users/BWinkKeyShellDinkInc","html_url":"https://github.com/BWinkKeyShellDinkInc","followers_url":"https://api.github.com/users/BWinkKeyShellDinkInc/followers","following_url":"https://api.github.com/users/BWinkKeyShellDinkInc/following{/other_user}","gists_url":"https://api.github.com/users/BWinkKeyShellDinkInc/gists{/gist_id}","starred_url":"https://api.github.com/users/BWinkKeyShellDinkInc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/BWinkKeyShellDinkInc/subscriptions","organizations_url":"https://api.github.com/users/BWinkKeyShellDinkInc/orgs","repos_url":"https://api.github.com/users/BWinkKeyShellDinkInc/repos","events_url":"https://api.github.com/users/BWinkKeyShellDinkInc/events{/privacy}","received_events_url":"https://api.github.com/users/BWinkKeyShellDinkInc/received_events","type":"User","site_admin":false},"created_at":"2015-05-16T12:39:16Z","updated_at":"2015-05-16T12:39:16Z","body":"I conducted two test on \"Repeated main fleet composition on pre/boss support fleet in event debrief and wrong fleet composition on pre/boss support fleet\" \r\n\r\nHypothesis: Fleet 2 is read as \"PreB Sup\", Fleet 3 is read as \"Boss Sup\" \r\nTest 1:\r\n* Fleet compositions:\r\n\r\nFleet 2: http://i.imgur.com/DIAlHDL.png (Main Fleet)\r\nFleet 3: http://i.imgur.com/v6XUJVo.png (PreB Sup)\r\nFleet 4: http://i.imgur.com/4Ln0A4B.png (Boss Sup)\r\n* Expeditions sent:\r\nhttp://i.imgur.com/gUePDmL.png\r\n* Sortie Debrief:\r\nhttp://i.imgur.com/br1CSmm.png\r\n\r\nTest 1 does support my hypothesis as Fleet 3 is read as a \"Boss Sup\" when it is actually sent as a \"PreB Sup\", Fleet 2 is read also read as \"PreB Sup\" and Fleet 4 is left out.\r\n\r\nTest 2:\r\n* Fleet compositions:\r\n\r\nFleet 1: http://i.imgur.com/y0RSfMJ.png (Main Fleet)\r\nFleet 2: http://i.imgur.com/5gabcQb.png (PreB Sup)\r\nFleet 3: http://i.imgur.com/LrQlk7r.png (Expedition Fleet)\r\nFleet 4: http://i.imgur.com/PiK2Ont.png (Boss Sup)\r\n* Expedition sent:\r\nhttp://i.imgur.com/zuyv44L.png\r\n* Sortie Debrief:\r\nhttp://i.imgur.com/zFsIcrP.png\r\n\r\nAgain, Test 2 does support my hypothesis. However, I was surprised by the repeating Main fleet composition on \"PreB Sup\" composition even though the fleet 1 is the main fleet. I can't find any reasoning with that. I would have though the repeating Main fleet composition is due to KC3 double reads it as a \"Main Fleet\" and \"PreB Sup\" when Fleet 2 is send out to sortie.\r\n\r\nThat concludes my findings \r\n\r\nOn another interesting find, regarding second bug thats listed above. It wasn't due to the old event sortie debrief but any debrief with only the main fleet that is sent out that triggers the bug to occur.\r\n\r\nEvidence:\r\n1. http://imgur.com/kVwBcCH.png (Sortie 61 is one of the latest event sortie i did)\r\n2. http://i.imgur.com/Xin2iA1.png (Before)\r\n3. http://i.imgur.com/oNjqOZ8.png\r\n4. http://i.imgur.com/hV3BMpv.png (After)\r\n"}}