{"action":"closed","issue":{"url":"https://api.github.com/repos/Sonarr/IssuePilot/issues/292","labels_url":"https://api.github.com/repos/Sonarr/IssuePilot/issues/292/labels{/name}","comments_url":"https://api.github.com/repos/Sonarr/IssuePilot/issues/292/comments","events_url":"https://api.github.com/repos/Sonarr/IssuePilot/issues/292/events","html_url":"https://github.com/Sonarr/IssuePilot/issues/292","id":74731271,"number":292,"title":"SignalR Syncing Queue causes return to page 1","user":{"login":"SonarrBot","id":1149584,"avatar_url":"https://avatars.githubusercontent.com/u/1149584?v=3","gravatar_id":"","url":"https://api.github.com/users/SonarrBot","html_url":"https://github.com/SonarrBot","followers_url":"https://api.github.com/users/SonarrBot/followers","following_url":"https://api.github.com/users/SonarrBot/following{/other_user}","gists_url":"https://api.github.com/users/SonarrBot/gists{/gist_id}","starred_url":"https://api.github.com/users/SonarrBot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/SonarrBot/subscriptions","organizations_url":"https://api.github.com/users/SonarrBot/orgs","repos_url":"https://api.github.com/users/SonarrBot/repos","events_url":"https://api.github.com/users/SonarrBot/events{/privacy}","received_events_url":"https://api.github.com/users/SonarrBot/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Sonarr/IssuePilot/labels/type:quality-of-life","name":"type:quality-of-life","color":"ededed"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-10T00:23:05Z","updated_at":"2015-05-09T18:48:56Z","closed_at":"2015-05-09T18:48:56Z","body":"SignalR event comes in telling queue collection to sync (so it fetches), fetch completes and backgrid gets a reset event triggered (not to check the event flow to see why), which causes all the backgrid pages to update and retur to page 1.\n\nWe don't want to see added/removed/updated events for everything in the queue, but should be able to prevent this behavior on the client side."}}