![\"Whiteout\"](\"https://i.imgur.com/aJUtJQK.png\")
Its really irritating and frustrating.
\n\nEdit : this has been resolved :)
", "messages": [ { "id": "538556", "postDate": "05/28/2019 18:27:12", "content": "Its really irritating and frustrating.
\n\nEdit : this has been resolved :)
", "rawMarkdown": "Its really irritating and frustrating. \n\nEdit : this has been resolved :)", "votes": null }, { "id": "538570", "postDate": "05/28/2019 19:12:44", "content": "and sometimes the frames in a notebook are empty until you click into them...
", "rawMarkdown": "and sometimes the frames in a notebook are empty until you click into them...", "votes": null }, { "id": "538576", "postDate": "05/28/2019 19:18:34", "content": "I thought this is only happening with me due to weak network. I thought kernels are not loading properly. My bad :D \nI was waiting for them to load :)
", "rawMarkdown": "I thought this is only happening with me due to weak network. I thought kernels are not loading properly. My bad :D \nI was waiting for them to load :)", "votes": null }, { "id": "538617", "postDate": "05/28/2019 21:25:13", "content": "It was apparently a bug and they've changed it back. Phew!
", "rawMarkdown": "It was apparently a bug and they've changed it back. Phew!", "votes": null }, { "id": "539427", "postDate": "05/30/2019 03:30:30", "content": "same here I also thought this was happening just to me. Frames of the notebook are also appearing to be empty unless I click onto them.
", "rawMarkdown": "same here I also thought this was happening just to me. Frames of the notebook are also appearing to be empty unless I click onto them.", "votes": null }, { "id": "539631", "postDate": "05/30/2019 10:19:05", "content": "@ian This is what I was trying to describe. The frames white/blank out completely, both inputs and outputs. Naturally I need to reset the entire notebook because I can't just pick up where I thought I left off. There's some weird bug that doesn't quite disconnect but essentially is as good as one because of the frame white outs. All outputs are whited out, so I'd have to guess which block I last executed. Even if I try to pick up where I left off, it would be not be a pleasant experience (not to mention that I may not even have the RAM to re-execute some cells because most of the memory has been used at that point. Not sure if it's a front end thing or back end thing. Please look into this if you can.
", "rawMarkdown": "ian This is what I was trying to describe. The frames white/blank out completely, both inputs and outputs. Naturally I need to reset the entire notebook because I can't just pick up where I thought I left off. There's some weird bug that doesn't quite disconnect but essentially is as good as one because of the frame white outs. All outputs are whited out, so I'd have to guess which block I last executed. Even if I try to pick up where I left off, it would be not be a pleasant experience (not to mention that I may not even have the RAM to re-execute some cells because most of the memory has been used at that point. Not sure if it's a front end thing or back end thing. Please look into this if you can.", "votes": null }, { "id": "539648", "postDate": "05/30/2019 11:00:42", "content": "@ian The whiteout effect is basically like a browser refresh effect (F5). So I'm not sure if myself and others are experiencing this in client end where their browsers automatically refresh the tab for whatever reason. If you manually or accidentally refresh a tab with a kaggle kernel, it will white out all the running kernels but keep running internally, but there is no way of knowing which cell you left off at. So I don't know if it's a browser feature that refreshes every so often or it is an something to do with kaggle's end. All I can say is not all my open kernels whiteout. It's not consistent across other kernels, just an occasional whiteout here and there. There are also instances where if I have too many tabs of kaggle open, a big number say 50+, all of my kaggle tabs display an error of out of memory error and I am forced to refresh the tab.
", "rawMarkdown": "ian The whiteout effect is basically like a browser refresh effect (F5). So I'm not sure if myself and others are experiencing this in client end where their browsers automatically refresh the tab for whatever reason. If you manually or accidentally refresh a tab with a kaggle kernel, it will white out all the running kernels but keep running internally, but there is no way of knowing which cell you left off at. So I don't know if it's a browser feature that refreshes every so often or it is an something to do with kaggle's end. All I can say is not all my open kernels whiteout. It's not consistent across other kernels, just an occasional whiteout here and there. There are also instances where if I have too many tabs of kaggle open, a big number say 50+, all of my kaggle tabs display an error of out of memory error and I am forced to refresh the tab.", "votes": null }, { "id": "539693", "postDate": "05/30/2019 12:13:04", "content": "@ian I was just working on a kernel and it blanked out 12 minutes in. and basically did a screen refresh without me doing anything.
\n\n
@teeyee314 This has happened to me a lot recently. It's possible Kaggle is under unusually heavy load right now as the competition heats up. Kaggle in general is becoming more popular from what I can tell - the number of maximum active kernels seems to have decreased over the past year from 25 to 10.
", "rawMarkdown": "teeyee314 This has happened to me a lot recently. It's possible Kaggle is under unusually heavy load right now as the competition heats up. Kaggle in general is becoming more popular from what I can tell - the number of maximum active kernels seems to have decreased over the past year from 25 to 10.", "votes": null }, { "id": "539808", "postDate": "05/30/2019 14:48:41", "content": "Thank you for the additional info, @teeyee314. I've forwarded it on to our team. They're aware of this sporadic issue and are working on it.
", "rawMarkdown": "Thank you for the additional info, @teeyee314. I've forwarded it on to our team. They're aware of this sporadic issue and are working on it.", "votes": null }, { "id": "539862", "postDate": "05/30/2019 16:10:36", "content": "Bug Reported and Removed. Great work people!!
", "rawMarkdown": "Bug Reported and Removed. Great work people!!", "votes": null }, { "id": "540220", "postDate": "05/31/2019 06:59:31", "content": "Also on refreshing the page from browser and trying to run cells of the notebook, it seems that the cell are running(by the \"*\" mark when cell runs) however cell doesn't executes it just stays like that. This issue is resolved on restarting session.
", "rawMarkdown": "Also on refreshing the page from browser and trying to run cells of the notebook, it seems that the cell are running(by the \"*\" mark when cell runs) however cell doesn't executes it just stays like that. This issue is resolved on restarting session.", "votes": null }, { "id": "540301", "postDate": "05/31/2019 10:21:46", "content": "@justforgags Thats what I'm saying... you don't know where you left off, and which cells are running in the background. It is as good a disconnected and a reboot is in short order.
", "rawMarkdown": "justforgags Thats what I'm saying... you don't know where you left off, and which cells are running in the background. It is as good a disconnected and a reboot is in short order.", "votes": null } ], "comments": [ { "id": 538570, "author_name": "ilu000", "author_url": "", "post_date": "05/28/2019 19:12:44", "content": "and sometimes the frames in a notebook are empty until you click into them...
", "votes": null, "replies": [] }, { "id": 538576, "author_name": "karanjakhar", "author_url": "", "post_date": "05/28/2019 19:18:34", "content": "I thought this is only happening with me due to weak network. I thought kernels are not loading properly. My bad :D \nI was waiting for them to load :)
", "votes": null, "replies": [] }, { "id": 538617, "author_name": "bigironsphere", "author_url": "", "post_date": "05/28/2019 21:25:13", "content": "It was apparently a bug and they've changed it back. Phew!
", "votes": null, "replies": [] }, { "id": 539427, "author_name": "justforgags", "author_url": "", "post_date": "05/30/2019 03:30:30", "content": "same here I also thought this was happening just to me. Frames of the notebook are also appearing to be empty unless I click onto them.
", "votes": null, "replies": [ { "id": 539631, "author_name": "teeyee314", "author_url": "", "post_date": "05/30/2019 10:19:05", "content": "@ian This is what I was trying to describe. The frames white/blank out completely, both inputs and outputs. Naturally I need to reset the entire notebook because I can't just pick up where I thought I left off. There's some weird bug that doesn't quite disconnect but essentially is as good as one because of the frame white outs. All outputs are whited out, so I'd have to guess which block I last executed. Even if I try to pick up where I left off, it would be not be a pleasant experience (not to mention that I may not even have the RAM to re-execute some cells because most of the memory has been used at that point. Not sure if it's a front end thing or back end thing. Please look into this if you can.
", "votes": null, "replies": [] }, { "id": 539648, "author_name": "teeyee314", "author_url": "", "post_date": "05/30/2019 11:00:42", "content": "@ian The whiteout effect is basically like a browser refresh effect (F5). So I'm not sure if myself and others are experiencing this in client end where their browsers automatically refresh the tab for whatever reason. If you manually or accidentally refresh a tab with a kaggle kernel, it will white out all the running kernels but keep running internally, but there is no way of knowing which cell you left off at. So I don't know if it's a browser feature that refreshes every so often or it is an something to do with kaggle's end. All I can say is not all my open kernels whiteout. It's not consistent across other kernels, just an occasional whiteout here and there. There are also instances where if I have too many tabs of kaggle open, a big number say 50+, all of my kaggle tabs display an error of out of memory error and I am forced to refresh the tab.
", "votes": null, "replies": [] }, { "id": 539693, "author_name": "teeyee314", "author_url": "", "post_date": "05/30/2019 12:13:04", "content": "@ian I was just working on a kernel and it blanked out 12 minutes in. and basically did a screen refresh without me doing anything.
\n\n
@teeyee314 This has happened to me a lot recently. It's possible Kaggle is under unusually heavy load right now as the competition heats up. Kaggle in general is becoming more popular from what I can tell - the number of maximum active kernels seems to have decreased over the past year from 25 to 10.
", "votes": null, "replies": [] }, { "id": 539808, "author_name": "ian", "author_url": "", "post_date": "05/30/2019 14:48:41", "content": "Thank you for the additional info, @teeyee314. I've forwarded it on to our team. They're aware of this sporadic issue and are working on it.
", "votes": null, "replies": [] }, { "id": 540220, "author_name": "justforgags", "author_url": "", "post_date": "05/31/2019 06:59:31", "content": "Also on refreshing the page from browser and trying to run cells of the notebook, it seems that the cell are running(by the \"*\" mark when cell runs) however cell doesn't executes it just stays like that. This issue is resolved on restarting session.
", "votes": null, "replies": [] }, { "id": 540301, "author_name": "teeyee314", "author_url": "", "post_date": "05/31/2019 10:21:46", "content": "@justforgags Thats what I'm saying... you don't know where you left off, and which cells are running in the background. It is as good a disconnected and a reboot is in short order.
", "votes": null, "replies": [] } ] }, { "id": 539862, "author_name": "akhileshrai", "author_url": "", "post_date": "05/30/2019 16:10:36", "content": "Bug Reported and Removed. Great work people!!
", "votes": null, "replies": [] } ], "raw_markdown_by_id": { "538556": "Its really irritating and frustrating. \n\nEdit : this has been resolved :)", "538570": "and sometimes the frames in a notebook are empty until you click into them...", "538576": "I thought this is only happening with me due to weak network. I thought kernels are not loading properly. My bad :D \nI was waiting for them to load :)", "538617": "It was apparently a bug and they've changed it back. Phew!", "539427": "same here I also thought this was happening just to me. Frames of the notebook are also appearing to be empty unless I click onto them.", "539631": "ian This is what I was trying to describe. The frames white/blank out completely, both inputs and outputs. Naturally I need to reset the entire notebook because I can't just pick up where I thought I left off. There's some weird bug that doesn't quite disconnect but essentially is as good as one because of the frame white outs. All outputs are whited out, so I'd have to guess which block I last executed. Even if I try to pick up where I left off, it would be not be a pleasant experience (not to mention that I may not even have the RAM to re-execute some cells because most of the memory has been used at that point. Not sure if it's a front end thing or back end thing. Please look into this if you can.", "539648": "ian The whiteout effect is basically like a browser refresh effect (F5). So I'm not sure if myself and others are experiencing this in client end where their browsers automatically refresh the tab for whatever reason. If you manually or accidentally refresh a tab with a kaggle kernel, it will white out all the running kernels but keep running internally, but there is no way of knowing which cell you left off at. So I don't know if it's a browser feature that refreshes every so often or it is an something to do with kaggle's end. All I can say is not all my open kernels whiteout. It's not consistent across other kernels, just an occasional whiteout here and there. There are also instances where if I have too many tabs of kaggle open, a big number say 50+, all of my kaggle tabs display an error of out of memory error and I am forced to refresh the tab.", "539693": "ian I was just working on a kernel and it blanked out 12 minutes in. and basically did a screen refresh without me doing anything.\n\n", "539741": "teeyee314 This has happened to me a lot recently. It's possible Kaggle is under unusually heavy load right now as the competition heats up. Kaggle in general is becoming more popular from what I can tell - the number of maximum active kernels seems to have decreased over the past year from 25 to 10.", "539808": "Thank you for the additional info, @teeyee314. I've forwarded it on to our team. They're aware of this sporadic issue and are working on it.", "539862": "Bug Reported and Removed. Great work people!!", "540220": "Also on refreshing the page from browser and trying to run cells of the notebook, it seems that the cell are running(by the \"*\" mark when cell runs) however cell doesn't executes it just stays like that. This issue is resolved on restarting session.", "540301": "justforgags Thats what I'm saying... you don't know where you left off, and which cells are running in the background. It is as good a disconnected and a reboot is in short order." }, "source": "meta" }