{"action":"opened","issue":{"url":"https://api.github.com/repos/CanonicalLtd/jujucharms.com/issues/562","repository_url":"https://api.github.com/repos/CanonicalLtd/jujucharms.com","labels_url":"https://api.github.com/repos/CanonicalLtd/jujucharms.com/issues/562/labels{/name}","comments_url":"https://api.github.com/repos/CanonicalLtd/jujucharms.com/issues/562/comments","events_url":"https://api.github.com/repos/CanonicalLtd/jujucharms.com/issues/562/events","html_url":"https://github.com/CanonicalLtd/jujucharms.com/issues/562","id":389656667,"node_id":"MDU6SXNzdWUzODk2NTY2Njc=","number":562,"title":"Cycling progress bar is deceptive","user":{"login":"matthewpaulthomas","id":19801137,"node_id":"MDQ6VXNlcjE5ODAxMTM3","avatar_url":"https://avatars2.githubusercontent.com/u/19801137?v=4","gravatar_id":"","url":"https://api.github.com/users/matthewpaulthomas","html_url":"https://github.com/matthewpaulthomas","followers_url":"https://api.github.com/users/matthewpaulthomas/followers","following_url":"https://api.github.com/users/matthewpaulthomas/following{/other_user}","gists_url":"https://api.github.com/users/matthewpaulthomas/gists{/gist_id}","starred_url":"https://api.github.com/users/matthewpaulthomas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/matthewpaulthomas/subscriptions","organizations_url":"https://api.github.com/users/matthewpaulthomas/orgs","repos_url":"https://api.github.com/users/matthewpaulthomas/repos","events_url":"https://api.github.com/users/matthewpaulthomas/events{/privacy}","received_events_url":"https://api.github.com/users/matthewpaulthomas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-11T08:58:53Z","updated_at":"2018-12-11T08:58:53Z","closed_at":null,"author_association":"NONE","body":"1\\. On jujucharms.com, click [“Try Big Data Anssr Engine”](https://jujucharms.com/new/?dd=~spiculecharms/bundle/anssr-data-engine).\r\n2\\. Watch the following page.\r\n\r\nWhat happens:\r\n- A progress bar quickly fills up. Ah, great, this is going to be ready in a moment.\r\n- The progress bar detaches from the beginning of its trough, and empties. What?\r\n- The progress bar fills up again from the beginning. Now I don’t trust it any more.\r\n- The progress bar detaches again.\r\n- The progress bar fills up again from the beginning. Etc.\r\n\r\nWhat should happen: [A progress bar always fills, for a successful task, exactly once.](https://docs.google.com/document/d/1UP7pD-jtX_mIn7Mw3YBS2SbKgDcNnLoMlvnAhzArfko/edit#heading=h.7srvw2rm1s1p)\r\n\r\nA simple first iteration would be to allocate 1/7 of the progress bar to each of the currently labelled subtasks (“Requesting the code”, “Reading the configuration”, “Connecting to the backend [sic]”, “Reticulating splines” (mhm), “Establishing API connections”, “Verifying identity”, and “Checking controller information”).\r\n\r\nA next step could be to measure what proportion of time each of those subtasks take on average, and adjust the proportions to match. Separately, perhaps one or more of the subtasks can have more granular updates."}}
{"actor":{"display_login":"matthewpaulthomas"}}