After the maintenance, starting an R notebook looks like an Infinite cycle of \n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n[Stopped]\n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]
\n\nMeanwhile python notebooks start within 5 seconds. Any explanation or similar experiences?
", "messages": [ { "id": 477664, "postDate": "2019-02-25T03:53:48.953Z", "content": "Opposite to you, I had difficulties to run and commit python notebooks. They were crashing all the time. During committing a red error note appears in the background, next to the notebook name. After longer wait all the changes seem saved, but I had to stop the kernel from my kernels list and run it again. I have one of the since before the shutdown and it was running smoothly most of the times.
", "rawMarkdown": "Opposite to you, I had difficulties to run and commit python notebooks. They were crashing all the time. During committing a red error note appears in the background, next to the notebook name. After longer wait all the changes seem saved, but I had to stop the kernel from my kernels list and run it again. I have one of the since before the shutdown and it was running smoothly most of the times.\n\n", "votes": 1, "replies": [ { "id": 478835, "postDate": "2019-02-26T17:35:00.850Z", "content": "I have found that sometimes, enabling the GPU on the kernel helps to sort out issues. This is for Python Notebooks. I haven't use R for Kaggle yet.
", "rawMarkdown": "I have found that sometimes, enabling the GPU on the kernel helps to sort out issues. This is for Python Notebooks. I haven't use R for Kaggle yet." } ] }, { "id": 477462, "postDate": "2019-02-24T16:18:53.173Z", "content": "Follow the following steps -\n1. If you're copying and pasting raw R code, I'd say a use a script rather than a notebook. If you're copying from a notebook, your best bet is to start a notebook kernel and then copy cell-by-cell. If you already have a full notebook, you can start a notebook kernel and then upload your notebook by clicking on the little cloud with an up arrow button at the top of the notebook.\n2. If you're pasting all the code for your notebook, scripts will throw a bit of a fit (although RMarkdown will work fine). Notebook kernels are a Jupyter notebook already, so pasting the code for making a notebook inside it will end up confusing it.\n3. Huh. Nooooot entirely sure what's going on there.
", "rawMarkdown": "Follow the following steps -\n1. If you're copying and pasting raw R code, I'd say a use a script rather than a notebook. If you're copying from a notebook, your best bet is to start a notebook kernel and then copy cell-by-cell. If you already have a full notebook, you can start a notebook kernel and then upload your notebook by clicking on the little cloud with an up arrow button at the top of the notebook.\n2. If you're pasting all the code for your notebook, scripts will throw a bit of a fit (although RMarkdown will work fine). Notebook kernels are a Jupyter notebook already, so pasting the code for making a notebook inside it will end up confusing it.\n3. Huh. Nooooot entirely sure what's going on there.\n", "votes": 1, "replies": [ { "id": 477575, "postDate": "2019-02-24T22:06:59.067Z", "rawMarkdown": "", "isDeleted": true } ] }, { "id": 477437, "postDate": "2019-02-24T14:51:30.273Z", "content": "After the maintenance, starting an R notebook looks like an Infinite cycle of \n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n[Stopped]\n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]
\n\nMeanwhile python notebooks start within 5 seconds. Any explanation or similar experiences?
", "rawMarkdown": "After the maintenance, starting an R notebook looks like an Infinite cycle of \n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n[Stopped]\n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n\nMeanwhile python notebooks start within 5 seconds. Any explanation or similar experiences?" } ], "comments": [ { "id": 477664, "author_name": "petyaAngelova", "author_url": "", "post_date": "2019-02-25T03:53:48.953000", "content": "Opposite to you, I had difficulties to run and commit python notebooks. They were crashing all the time. During committing a red error note appears in the background, next to the notebook name. After longer wait all the changes seem saved, but I had to stop the kernel from my kernels list and run it again. I have one of the since before the shutdown and it was running smoothly most of the times.
", "votes": 1, "replies": [ { "id": 478835, "author_name": "DevilEars", "author_url": "", "post_date": "2019-02-26T17:35:00.850000", "content": "I have found that sometimes, enabling the GPU on the kernel helps to sort out issues. This is for Python Notebooks. I haven't use R for Kaggle yet.
", "votes": 0, "replies": [] } ] }, { "id": 477462, "author_name": "Shobhit Srivastava", "author_url": "", "post_date": "2019-02-24T16:18:53.173000", "content": "Follow the following steps -\n1. If you're copying and pasting raw R code, I'd say a use a script rather than a notebook. If you're copying from a notebook, your best bet is to start a notebook kernel and then copy cell-by-cell. If you already have a full notebook, you can start a notebook kernel and then upload your notebook by clicking on the little cloud with an up arrow button at the top of the notebook.\n2. If you're pasting all the code for your notebook, scripts will throw a bit of a fit (although RMarkdown will work fine). Notebook kernels are a Jupyter notebook already, so pasting the code for making a notebook inside it will end up confusing it.\n3. Huh. Nooooot entirely sure what's going on there.
", "votes": 1, "replies": [ { "id": 477575, "author_name": "", "author_url": "", "post_date": "2019-02-24T22:06:59.067000", "content": "", "votes": 0, "replies": [] } ] } ], "raw_markdown_by_id": { "477664": "Opposite to you, I had difficulties to run and commit python notebooks. They were crashing all the time. During committing a red error note appears in the background, next to the notebook name. After longer wait all the changes seem saved, but I had to stop the kernel from my kernels list and run it again. I have one of the since before the shutdown and it was running smoothly most of the times.\n\n", "477462": "Follow the following steps -\n1. If you're copying and pasting raw R code, I'd say a use a script rather than a notebook. If you're copying from a notebook, your best bet is to start a notebook kernel and then copy cell-by-cell. If you already have a full notebook, you can start a notebook kernel and then upload your notebook by clicking on the little cloud with an up arrow button at the top of the notebook.\n2. If you're pasting all the code for your notebook, scripts will throw a bit of a fit (although RMarkdown will work fine). Notebook kernels are a Jupyter notebook already, so pasting the code for making a notebook inside it will end up confusing it.\n3. Huh. Nooooot entirely sure what's going on there.\n", "477437": "After the maintenance, starting an R notebook looks like an Infinite cycle of \n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n[Stopped]\n[Initializing]\n[Waiting for an instance to become available... Done]\n[Error]\n\nMeanwhile python notebooks start within 5 seconds. Any explanation or similar experiences?" } }