{"action":"created","issue":{"url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/6018","labels_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/6018/labels{/name}","comments_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/6018/comments","events_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/6018/events","html_url":"https://github.com/HabitRPG/habitrpg/pull/6018","id":110135982,"number":6018,"title":"Issue #2606 - Verify/fix indices during sortTask","user":{"login":"dcecile","id":311866,"avatar_url":"https://avatars.githubusercontent.com/u/311866?v=3","gravatar_id":"","url":"https://api.github.com/users/dcecile","html_url":"https://github.com/dcecile","followers_url":"https://api.github.com/users/dcecile/followers","following_url":"https://api.github.com/users/dcecile/following{/other_user}","gists_url":"https://api.github.com/users/dcecile/gists{/gist_id}","starred_url":"https://api.github.com/users/dcecile/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dcecile/subscriptions","organizations_url":"https://api.github.com/users/dcecile/orgs","repos_url":"https://api.github.com/users/dcecile/repos","events_url":"https://api.github.com/users/dcecile/events{/privacy}","received_events_url":"https://api.github.com/users/dcecile/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-10-07T01:35:49Z","updated_at":"2015-10-09T21:15:29Z","closed_at":"2015-10-09T11:30:14Z","pull_request":{"url":"https://api.github.com/repos/HabitRPG/habitrpg/pulls/6018","html_url":"https://github.com/HabitRPG/habitrpg/pull/6018","diff_url":"https://github.com/HabitRPG/habitrpg/pull/6018.diff","patch_url":"https://github.com/HabitRPG/habitrpg/pull/6018.patch"},"body":"Because the 'sortTask' operation uses a 'from' index and a 'to'\r\nindex as parameters, the server needs to check if these indices\r\nare valid before performing the client's request. If the task ID\r\ndoesn't match the task at the 'from' index, then it's clear that\r\nthe client was looking at a preened list of todos (everything except\r\nmore-than-3-days-old-non-quest completed tasks). In that case, try\r\nto recalculate the indices before continuing."},"comment":{"url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/comments/146987732","html_url":"https://github.com/HabitRPG/habitrpg/pull/6018#issuecomment-146987732","issue_url":"https://api.github.com/repos/HabitRPG/habitrpg/issues/6018","id":146987732,"user":{"login":"Alys","id":1495809,"avatar_url":"https://avatars.githubusercontent.com/u/1495809?v=3","gravatar_id":"","url":"https://api.github.com/users/Alys","html_url":"https://github.com/Alys","followers_url":"https://api.github.com/users/Alys/followers","following_url":"https://api.github.com/users/Alys/following{/other_user}","gists_url":"https://api.github.com/users/Alys/gists{/gist_id}","starred_url":"https://api.github.com/users/Alys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Alys/subscriptions","organizations_url":"https://api.github.com/users/Alys/orgs","repos_url":"https://api.github.com/users/Alys/repos","events_url":"https://api.github.com/users/Alys/events{/privacy}","received_events_url":"https://api.github.com/users/Alys/received_events","type":"User","site_admin":false},"created_at":"2015-10-09T21:15:29Z","updated_at":"2015-10-09T21:15:29Z","body":"Tier awarded! I hope it will be the first of many!\r\n\r\nNote that the higher tiers require more work than the lower ones, so as you progress, you'll find that it takes a few PRs or one large one to achieve each tier. There's information about [Contributor Rewards](http://habitica.wikia.com/wiki/Contributor_Rewards) on the wiki, but you're welcome to ask questions here or in the [Aspiring Coders](https://habitica.com/#/options/groups/guilds/68d4a01e-db97-4786-8ee3-05d612c5af6f) guild.\r\n\r\nWhen a PR is merged, it is automatically deployed to a staging site that only staff and admins use (this is to protect regular players from any bugs that weren't noticed during review of the PR). All material on the staging site is deployed to production manually when we feel it's appropriate (never automatically). For critical fixes or very minor, safe changes, we might deploy immediately. User-visible changes that were planned by the staff (e.g., new quests, new equipment) are deployed on a specific date chosen ahead of time. For everything else, such as this PR, it's variable. It can take a few days before the change will appear in production.\r\n\r\nI'll comment here when this is deployed, since it won't be obvious to anyone who doesn't sort To-Dos a lot. :)"}}