{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/7bd67e58e011c25ba9c0d62757386a27?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"7bd67e58e011c25ba9c0d62757386a27","url":"https://api.github.com/users/lydiam","login":"lydiam","id":305837},"milestone":null,"assignee":null,"updated_at":"2011-11-10T21:19:38Z","labels":[{"name":"DAITSS 2.x","color":"73f5f5","url":"https://api.github.com/repos/daitss/core/labels/DAITSS+2.x"}],"comments":2,"closed_at":"2011-11-10T21:19:38Z","url":"https://api.github.com/repos/daitss/core/issues/252","body":"I believe that this is already planned, but I want to make sure that the GUI registers throttle changes without a core restart.  Currently it does not, so the workspace throttle display is often out of sync with what pulse is doing.  I haven't been restarting core with each throttle change because I don't want to interrupt processing.","html_url":"https://github.com/daitss/core/issues/252","title":"GUI: recognize throttle changes without a core restart","number":252,"id":624145,"created_at":"2011-02-24T15:10:49Z"},"action":"closed"}