{"push_id":602018350,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"ce8488b60cc10910289122a641fecec7be17814f","before":"2afb44888649617c0254e063de0e528f5fede0ed","commits":[{"sha":"ce8488b60cc10910289122a641fecec7be17814f","author":{"email":"627cca369b1d357a5abbfbbff23864b6fe682198@gmail.com","name":"simh"},"message":"Broadcast works at the lab. But there are issues.\n\nWhen we broadcast, we also receive an echo on our own machine.\nThis is picked up by the network module, which proceeds to\nsend a message over the FROM_CLIENT channel. But when we are\nrunning an instance of only the Client routine, we do not read\nfrom this channel. Thus, the network module becomes blocked\nfrom sending further messages.\n\nWe can not just read from the channel in the Client routine,\nsince it will run concurrently with the Master routine - which\nDOES read from the channel.\n\nIn main I added a concurrent thread that reads from the channel\nwhen we only launch the client. This fixed the bugs I had today,\nbut will not fix the bugs we get in the future when a backup\nclient needs to become the master. Since then we need to stop\nthat routine, and it gets really ugly.\n\nTODO: Figure this out.","distinct":true,"url":"https://api.github.com/repos/lightbits/ttk4145/commits/ce8488b60cc10910289122a641fecec7be17814f"}]}