{
  "id": 71867,
  "title": "Bug? Feature? Seeing kernels not fully materialised",
  "url": "/competitions/quora-insincere-questions-classification/discussion/71867",
  "author_name": "",
  "post_date": "2018-11-17T14:39:48.348604100Z",
  "votes": 3,
  "comment_count": 3,
  "views": 0,
  "content": "<p>When we examine a public kernel, I think it used to show us the full materialised kernel. I see only a half backed kernels now. Does it mean I have to fork them and run them myself from now. Bug? Deliberately?</p>",
  "messages": [
    {
      "id": "423121",
      "postDate": "11/17/2018 14:39:48",
      "content": "<p>When we examine a public kernel, I think it used to show us the full materialised kernel. I see only a half backed kernels now. Does it mean I have to fork them and run them myself from now. Bug? Deliberately?</p>",
      "rawMarkdown": "When we examine a public kernel, I think it used to show us the full materialised kernel. I see only a half backed kernels now. Does it mean I have to fork them and run them myself from now. Bug? Deliberately?",
      "votes": null
    },
    {
      "id": "424432",
      "postDate": "11/20/2018 05:50:33",
      "content": "<p>Do you have some examples of kernels where you see this? I have noticed myself I have some issues trying to load some of my committed kernels, especially when they get bigger. Sometimes trying a different browser helps.</p>\n\n<p>If you have public examples for whatever behaviour you see, that could be very helpful to help Kaggle fix it.</p>",
      "rawMarkdown": "Do you have some examples of kernels where you see this? I have noticed myself I have some issues trying to load some of my committed kernels, especially when they get bigger. Sometimes trying a different browser helps.\n\nIf you have public examples for whatever behaviour you see, that could be very helpful to help Kaggle fix it.",
      "votes": null
    },
    {
      "id": "424504",
      "postDate": "11/20/2018 08:19:36",
      "content": "<p>A random example. For me it is truncated. When I fork the notebook I see more content. <a href=\"https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification\">https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification</a></p>",
      "rawMarkdown": "A random example. For me it is truncated. When I fork the notebook I see more content. https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification",
      "votes": null
    },
    {
      "id": "424647",
      "postDate": "11/20/2018 13:34:05",
      "content": "<p>This is a known bug. It is supposed to be fixed now. A workaround was using incognito mode on the browser. </p>",
      "rawMarkdown": "This is a known bug. It is supposed to be fixed now. A workaround was using incognito mode on the browser.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 424432,
      "author_name": "donkeys",
      "author_url": "",
      "post_date": "11/20/2018 05:50:33",
      "content": "<p>Do you have some examples of kernels where you see this? I have noticed myself I have some issues trying to load some of my committed kernels, especially when they get bigger. Sometimes trying a different browser helps.</p>\n\n<p>If you have public examples for whatever behaviour you see, that could be very helpful to help Kaggle fix it.</p>",
      "votes": null,
      "replies": [
        {
          "id": 424504,
          "author_name": "abosol",
          "author_url": "",
          "post_date": "11/20/2018 08:19:36",
          "content": "<p>A random example. For me it is truncated. When I fork the notebook I see more content. <a href=\"https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification\">https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification</a></p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 424647,
      "author_name": "afgonczol",
      "author_url": "",
      "post_date": "11/20/2018 13:34:05",
      "content": "<p>This is a known bug. It is supposed to be fixed now. A workaround was using incognito mode on the browser. </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "423121": "When we examine a public kernel, I think it used to show us the full materialised kernel. I see only a half backed kernels now. Does it mean I have to fork them and run them myself from now. Bug? Deliberately?",
    "424432": "Do you have some examples of kernels where you see this? I have noticed myself I have some issues trying to load some of my committed kernels, especially when they get bigger. Sometimes trying a different browser helps.\n\nIf you have public examples for whatever behaviour you see, that could be very helpful to help Kaggle fix it.",
    "424504": "A random example. For me it is truncated. When I fork the notebook I see more content. https://www.kaggle.com/fareise/multi-head-self-attention-for-text-classification",
    "424647": "This is a known bug. It is supposed to be fixed now. A workaround was using incognito mode on the browser."
  },
  "source": "meta"
}