{"action":"created","issue":{"url":"https://api.github.com/repos/rails/rails/issues/28124","repository_url":"https://api.github.com/repos/rails/rails","labels_url":"https://api.github.com/repos/rails/rails/issues/28124/labels{/name}","comments_url":"https://api.github.com/repos/rails/rails/issues/28124/comments","events_url":"https://api.github.com/repos/rails/rails/issues/28124/events","html_url":"https://github.com/rails/rails/issues/28124","id":209749166,"number":28124,"title":"rails 4.2 gets stuck when schema migrations table differs from active migrations on disk","user":{"login":"sandys","id":76883,"avatar_url":"https://avatars.githubusercontent.com/u/76883?v=3","gravatar_id":"","url":"https://api.github.com/users/sandys","html_url":"https://github.com/sandys","followers_url":"https://api.github.com/users/sandys/followers","following_url":"https://api.github.com/users/sandys/following{/other_user}","gists_url":"https://api.github.com/users/sandys/gists{/gist_id}","starred_url":"https://api.github.com/users/sandys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sandys/subscriptions","organizations_url":"https://api.github.com/users/sandys/orgs","repos_url":"https://api.github.com/users/sandys/repos","events_url":"https://api.github.com/users/sandys/events{/privacy}","received_events_url":"https://api.github.com/users/sandys/received_events","type":"User","site_admin":false},"labels":[{"id":257468118,"url":"https://api.github.com/repos/rails/rails/labels/needs%20work","name":"needs work","color":"000000","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-02-23T12:34:17Z","updated_at":"2017-02-24T03:38:12Z","closed_at":null,"body":"we had a sequence when another engineer ran migrations on our staging database (and therefore updated the schema migrations table), however forgot to check it in.\r\n\r\nWe then added new migrations, and then attempted to run these  migrations  on the staging database.\r\n\r\nRake db:migrate gets stuck and doesnt move forward. neither does rollback.\r\n\r\nWhat we expected is an error that the rails migrations are mismatching - that would help us instantly figure out what was wrong. Instead we spent an hour trying to figure out if our connection pooling was working fine, database locks were freed, etc."},"comment":{"url":"https://api.github.com/repos/rails/rails/issues/comments/282195362","html_url":"https://github.com/rails/rails/issues/28124#issuecomment-282195362","issue_url":"https://api.github.com/repos/rails/rails/issues/28124","id":282195362,"user":{"login":"rafaelfranca","id":47848,"avatar_url":"https://avatars.githubusercontent.com/u/47848?v=3","gravatar_id":"","url":"https://api.github.com/users/rafaelfranca","html_url":"https://github.com/rafaelfranca","followers_url":"https://api.github.com/users/rafaelfranca/followers","following_url":"https://api.github.com/users/rafaelfranca/following{/other_user}","gists_url":"https://api.github.com/users/rafaelfranca/gists{/gist_id}","starred_url":"https://api.github.com/users/rafaelfranca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rafaelfranca/subscriptions","organizations_url":"https://api.github.com/users/rafaelfranca/orgs","repos_url":"https://api.github.com/users/rafaelfranca/repos","events_url":"https://api.github.com/users/rafaelfranca/events{/privacy}","received_events_url":"https://api.github.com/users/rafaelfranca/received_events","type":"User","site_admin":false},"created_at":"2017-02-24T03:38:12Z","updated_at":"2017-02-24T03:38:12Z","body":"Without a way to reproduce it is hard to us to do anything. In my application we always have more rows in the schema migration table than migration files on disk so I don't think that is the problem. We would need a way to reproduce this problem so we can work on a fix."}}
{"actor":{"display_login":"rafaelfranca"}}