Got a message (while on TPU):\n\"Are you still there? Your TPU notebook stops after 15 minutes of idle time. Commit your notebook for longer computations.\"\nTried to \"Save and commit\" - same result.\nSo... If I want to do a \"final commit\", I'll have to be close to a computer, moving mouse around, or how can I show it that it is not idle?
", "messages": [ { "id": "878761", "postDate": "06/08/2020 19:57:46", "content": "Got a message (while on TPU):\n\"Are you still there? Your TPU notebook stops after 15 minutes of idle time. Commit your notebook for longer computations.\"\nTried to \"Save and commit\" - same result.\nSo... If I want to do a \"final commit\", I'll have to be close to a computer, moving mouse around, or how can I show it that it is not idle?
", "rawMarkdown": "Got a message (while on TPU):\n\"Are you still there? Your TPU notebook stops after 15 minutes of idle time. Commit your notebook for longer computations.\"\nTried to \"Save and commit\" - same result.\nSo... If I want to do a \"final commit\", I'll have to be close to a computer, moving mouse around, or how can I show it that it is not idle?", "votes": null }, { "id": "878821", "postDate": "06/08/2020 22:08:33", "content": "One of my pet peeves about the new look - kind of hard to believe that Google/Kaggle folks are among the world's best - they seem to have created a very \"not makes sense\" interface for the step of saving and committing.
\n\n Save Version\n\n Save & Run All (Commit)\n\n Save\nSmall dialog now starts indicating that \"Creating Version\"
\n\nNOW - the \"not makes sense\" part. Just close the browser window. You code is running on the server. If you leave the window open - than you get the message.
\n\nSo how do you know its still running - TRUST Google.
\n\nHow do you know when its done running - hmmm beats the heck out of me. Just come back later.
\n\nThe old procedure was so clean and easy to understand - the new look is horrible !
", "rawMarkdown": "One of my pet peeves about the new look - kind of hard to believe that Google/Kaggle folks are among the world's best - they seem to have created a very \"not makes sense\" interface for the step of saving and committing.\n\n Save Version\n\n Save & Run All (Commit)\n\n Save\n\nSmall dialog now starts indicating that \"Creating Version\"\n\nNOW - the \"not makes sense\" part. Just close the browser window. You code is running on the server. If you leave the window open - than you get the message.\n\nSo how do you know its still running - TRUST Google.\n\nHow do you know when its done running - hmmm beats the heck out of me. Just come back later.\n\nThe old procedure was so clean and easy to understand - the new look is horrible !", "votes": null }, { "id": "878827", "postDate": "06/08/2020 22:24:13", "content": "When you are editing a notebook, a so called interactive session is running, like sitting in front of a computer.\nAfter pressing \"Save and Commit\", a copy of your current notebook code is transfered to a \"commit server\" and a second \"commit session\" ist started for the processing of your whole notebook.
\n\nThe interactive session is still running, and you can continue to work. In the background the commit session will process your notebook.
\n\nMy normal workflow for committing is:\n - press \"Save version\" on top right\n - choose \"Save and run all (commit)\"\n - wait a few seconds\n - in Menu on top \"run\" -> \"Stop session\" (to stop the interactive Session)\n - close browser tab or use the back-arrow on top left to leave the editor.\n - if I want to continue to work I fork a existing notebook or create a new one as long as the commit session is running.
\n\nPress in the left website menu on \"Notebooks\" to get a list with actual running sessions. The text changes from \"running since....\" to \"run ... ago\"
\n\nHave fun coding ;-)
", "rawMarkdown": "When you are editing a notebook, a so called interactive session is running, like sitting in front of a computer.\nAfter pressing \"Save and Commit\", a _copy_ of your current notebook code is transfered to a \"commit server\" and a second \"commit session\" ist started for the processing of your whole notebook.\n\nThe interactive session is still running, and you can continue to work. In the background the commit session will process your notebook.\n\nMy normal workflow for committing is:\n - press \"Save version\" on top right\n - choose \"Save and run all (commit)\"\n - wait a few seconds\n - in Menu on top \"run\" -> \"Stop session\" (to stop the interactive Session)\n - close browser tab or use the back-arrow on top left to leave the editor.\n - if I want to continue to work I fork a existing notebook or create a new one as long as the commit session is running.\n\nPress in the left website menu on \"Notebooks\" to get a list with actual running sessions. The text changes from \"running since....\" to \"run ... ago\"\n\nHave fun coding ;-)", "votes": null }, { "id": "879055", "postDate": "06/09/2020 06:38:55", "content": "Not sure. Because I see my commit made my by-hand upload 2 days ago, but I do not see my commit from that \"hidden session\".
", "rawMarkdown": "Not sure. Because I see my commit made my by-hand upload 2 days ago, but I do not see my commit from that \"hidden session\".", "votes": null }, { "id": "879056", "postDate": "06/09/2020 06:40:09", "content": "And one more question - that \"hidden\" session uses what the \"visible\" one used - like GPU or TPU? Or will it choose, say, TPU no mater?
", "rawMarkdown": "And one more question - that \"hidden\" session uses what the \"visible\" one used - like GPU or TPU? Or will it choose, say, TPU no mater?", "votes": null }, { "id": "879097", "postDate": "06/09/2020 07:32:53", "content": "Yes, after pressing \"Commit\" a copy of your current session inclusive all settings like CPU/GPU/TPU and datasets is processed as a commit session in the background.
", "rawMarkdown": "Yes, after pressing \"Commit\" a copy of your current session inclusive all settings like CPU/GPU/TPU and datasets is processed as a commit session in the background.", "votes": null }, { "id": "879108", "postDate": "06/09/2020 07:38:52", "content": "When you view a notebook like this one https://www.kaggle.com/cdeotte/how-to-create-tfrecords press on \"version 3 of 3\" to get a list of all versions of this notebook.
", "rawMarkdown": "When you view a notebook like this one [https://www.kaggle.com/cdeotte/how-to-create-tfrecords](Link) press on \"version 3 of 3\" to get a list of all versions of this notebook.", "votes": null }, { "id": "879766", "postDate": "06/09/2020 17:50:08", "content": "We're pretty down to earth. Always looking to improve. No need to be snarky.
", "rawMarkdown": "We're pretty down to earth. Always looking to improve. No need to be snarky.", "votes": null } ], "comments": [ { "id": 878821, "author_name": "pcjimmmy", "author_url": "", "post_date": "06/08/2020 22:08:33", "content": "One of my pet peeves about the new look - kind of hard to believe that Google/Kaggle folks are among the world's best - they seem to have created a very \"not makes sense\" interface for the step of saving and committing.
\n\n Save Version\n\n Save & Run All (Commit)\n\n Save\nSmall dialog now starts indicating that \"Creating Version\"
\n\nNOW - the \"not makes sense\" part. Just close the browser window. You code is running on the server. If you leave the window open - than you get the message.
\n\nSo how do you know its still running - TRUST Google.
\n\nHow do you know when its done running - hmmm beats the heck out of me. Just come back later.
\n\nThe old procedure was so clean and easy to understand - the new look is horrible !
", "votes": null, "replies": [ { "id": 879766, "author_name": "inversion", "author_url": "", "post_date": "06/09/2020 17:50:08", "content": "We're pretty down to earth. Always looking to improve. No need to be snarky.
", "votes": null, "replies": [] } ] }, { "id": 878827, "author_name": "agentauers", "author_url": "", "post_date": "06/08/2020 22:24:13", "content": "When you are editing a notebook, a so called interactive session is running, like sitting in front of a computer.\nAfter pressing \"Save and Commit\", a copy of your current notebook code is transfered to a \"commit server\" and a second \"commit session\" ist started for the processing of your whole notebook.
\n\nThe interactive session is still running, and you can continue to work. In the background the commit session will process your notebook.
\n\nMy normal workflow for committing is:\n - press \"Save version\" on top right\n - choose \"Save and run all (commit)\"\n - wait a few seconds\n - in Menu on top \"run\" -> \"Stop session\" (to stop the interactive Session)\n - close browser tab or use the back-arrow on top left to leave the editor.\n - if I want to continue to work I fork a existing notebook or create a new one as long as the commit session is running.
\n\nPress in the left website menu on \"Notebooks\" to get a list with actual running sessions. The text changes from \"running since....\" to \"run ... ago\"
\n\nHave fun coding ;-)
", "votes": null, "replies": [] }, { "id": 879055, "author_name": "fizpok", "author_url": "", "post_date": "06/09/2020 06:38:55", "content": "Not sure. Because I see my commit made my by-hand upload 2 days ago, but I do not see my commit from that \"hidden session\".
", "votes": null, "replies": [ { "id": 879108, "author_name": "agentauers", "author_url": "", "post_date": "06/09/2020 07:38:52", "content": "When you view a notebook like this one https://www.kaggle.com/cdeotte/how-to-create-tfrecords press on \"version 3 of 3\" to get a list of all versions of this notebook.
", "votes": null, "replies": [] } ] }, { "id": 879056, "author_name": "fizpok", "author_url": "", "post_date": "06/09/2020 06:40:09", "content": "And one more question - that \"hidden\" session uses what the \"visible\" one used - like GPU or TPU? Or will it choose, say, TPU no mater?
", "votes": null, "replies": [ { "id": 879097, "author_name": "agentauers", "author_url": "", "post_date": "06/09/2020 07:32:53", "content": "Yes, after pressing \"Commit\" a copy of your current session inclusive all settings like CPU/GPU/TPU and datasets is processed as a commit session in the background.
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "878761": "Got a message (while on TPU):\n\"Are you still there? Your TPU notebook stops after 15 minutes of idle time. Commit your notebook for longer computations.\"\nTried to \"Save and commit\" - same result.\nSo... If I want to do a \"final commit\", I'll have to be close to a computer, moving mouse around, or how can I show it that it is not idle?", "878821": "One of my pet peeves about the new look - kind of hard to believe that Google/Kaggle folks are among the world's best - they seem to have created a very \"not makes sense\" interface for the step of saving and committing.\n\n Save Version\n\n Save & Run All (Commit)\n\n Save\n\nSmall dialog now starts indicating that \"Creating Version\"\n\nNOW - the \"not makes sense\" part. Just close the browser window. You code is running on the server. If you leave the window open - than you get the message.\n\nSo how do you know its still running - TRUST Google.\n\nHow do you know when its done running - hmmm beats the heck out of me. Just come back later.\n\nThe old procedure was so clean and easy to understand - the new look is horrible !", "878827": "When you are editing a notebook, a so called interactive session is running, like sitting in front of a computer.\nAfter pressing \"Save and Commit\", a _copy_ of your current notebook code is transfered to a \"commit server\" and a second \"commit session\" ist started for the processing of your whole notebook.\n\nThe interactive session is still running, and you can continue to work. In the background the commit session will process your notebook.\n\nMy normal workflow for committing is:\n - press \"Save version\" on top right\n - choose \"Save and run all (commit)\"\n - wait a few seconds\n - in Menu on top \"run\" -> \"Stop session\" (to stop the interactive Session)\n - close browser tab or use the back-arrow on top left to leave the editor.\n - if I want to continue to work I fork a existing notebook or create a new one as long as the commit session is running.\n\nPress in the left website menu on \"Notebooks\" to get a list with actual running sessions. The text changes from \"running since....\" to \"run ... ago\"\n\nHave fun coding ;-)", "879055": "Not sure. Because I see my commit made my by-hand upload 2 days ago, but I do not see my commit from that \"hidden session\".", "879056": "And one more question - that \"hidden\" session uses what the \"visible\" one used - like GPU or TPU? Or will it choose, say, TPU no mater?", "879097": "Yes, after pressing \"Commit\" a copy of your current session inclusive all settings like CPU/GPU/TPU and datasets is processed as a commit session in the background.", "879108": "When you view a notebook like this one [https://www.kaggle.com/cdeotte/how-to-create-tfrecords](Link) press on \"version 3 of 3\" to get a list of all versions of this notebook.", "879766": "We're pretty down to earth. Always looking to improve. No need to be snarky." }, "source": "meta" }