{"action":"created","issue":{"url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/541","repository_url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension","labels_url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/541/labels{/name}","comments_url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/541/comments","events_url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/541/events","html_url":"https://github.com/rainforestapp/tester-chrome-extension/issues/541","id":176492562,"number":541,"title":"Restart Job button and disabling refreshing","user":{"login":"ikjt","id":22079118,"avatar_url":"https://avatars.githubusercontent.com/u/22079118?v=3","gravatar_id":"","url":"https://api.github.com/users/ikjt","html_url":"https://github.com/ikjt","followers_url":"https://api.github.com/users/ikjt/followers","following_url":"https://api.github.com/users/ikjt/following{/other_user}","gists_url":"https://api.github.com/users/ikjt/gists{/gist_id}","starred_url":"https://api.github.com/users/ikjt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ikjt/subscriptions","organizations_url":"https://api.github.com/users/ikjt/orgs","repos_url":"https://api.github.com/users/ikjt/repos","events_url":"https://api.github.com/users/ikjt/events{/privacy}","received_events_url":"https://api.github.com/users/ikjt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":12,"created_at":"2016-09-12T21:41:56Z","updated_at":"2016-09-13T13:45:04Z","closed_at":null,"body":"@pscohn\r\n\r\nPaul, first thanks for the Restart Job button. It's great to have it when something happens to the VM.\r\n\r\nI have a concern about disabling refreshing, though. Here is the case that concerns me. It has happened quite a few times that after clicking Restart Job button, there is an error (something bad happened, couldn't get safari machine, too many requests, failed to fetch, application error etc). In case of any of those errors, the page gets redirected to the specific error page. That means we have no longer access to the Restart Job button. If we can no longer refresh those error pages, the jobs will get abandoned, sadly. I would have lost around 5 jobs yesterday/today if refreshing was not allowed. Luckily, thanks to the remaining refreshes, I was able to get a working VM and not lose the jobs.\r\n\r\nPerhaps, it would be possible to display all those error messages on top of the testing interface page? So we wouldn't be redirected from that page and we still have access to the Restart Job button. In case of the screenshot, io, security errors, they are all displayed on top of the testing interface page, so perhaps that would also be possible in case of the errors that we'll encounter when clicking the Restart Job button?\r\n\r\nAlso, could you please clarify at what point is the job considered in-progress. There are times when the testing interface page is loaded and only terminal is still loading, but if the terminal fails to load, we are once again redirected to the error page (something bad happened,couldn't get ... machine, too many requests, failed to fetch etc). Is that already considered as job in-progress since the job was allocated to us, even though we were not able to start it? If it is, those jobs will also be lost if we can't refresh the error pages.\r\n\r\nThank a lot. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/comments/246685694","html_url":"https://github.com/rainforestapp/tester-chrome-extension/issues/541#issuecomment-246685694","issue_url":"https://api.github.com/repos/rainforestapp/tester-chrome-extension/issues/541","id":246685694,"user":{"login":"jackqc","id":20456320,"avatar_url":"https://avatars.githubusercontent.com/u/20456320?v=3","gravatar_id":"","url":"https://api.github.com/users/jackqc","html_url":"https://github.com/jackqc","followers_url":"https://api.github.com/users/jackqc/followers","following_url":"https://api.github.com/users/jackqc/following{/other_user}","gists_url":"https://api.github.com/users/jackqc/gists{/gist_id}","starred_url":"https://api.github.com/users/jackqc/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jackqc/subscriptions","organizations_url":"https://api.github.com/users/jackqc/orgs","repos_url":"https://api.github.com/users/jackqc/repos","events_url":"https://api.github.com/users/jackqc/events{/privacy}","received_events_url":"https://api.github.com/users/jackqc/received_events","type":"User","site_admin":false},"created_at":"2016-09-13T13:45:04Z","updated_at":"2016-09-13T13:45:04Z","body":"Today the following happened to me: job started, everything went find, after 2 two steps, there was a red error message \"something bad happened\" on an otherwise blank page, no way to use the restart job or reconnect button as the terminal the instructions and the buttons were all gone. I managed to recover my job by reloading the browser page, restarting the job. If reloading means would mean abandoning the job in future, I might as well have closed the tab. "}}
{"actor":{"display_login":"jackqc"}}