{
  "id": 105895,
  "title": "Mysterious error on kernel commit after kernel \"complete\"s without errors",
  "url": "/competitions/aptos2019-blindness-detection/discussion/105895",
  "author_name": "",
  "post_date": "2019-08-27T03:46:09.317664200Z",
  "votes": 1,
  "comment_count": 3,
  "views": 0,
  "content": "<p>Screenshot attached. </p>\n\n<p>The last code line in my kernel is <code>print(\"finished writing submission.csv\")</code> and when I commit the kernel, the log gets to <code>finished writing submissions.csv</code> without generating any errors. And as shown in the screenshot, the version is marked as \"complete\" in green. However, in the bottom of the screenshot, you can see the version is shown as still processing (the circular dots). That goes on indefinitely. </p>\n\n<p>Then when I open the kernel from a new window to get to the \"submit csv to competition\" button, I get a message that \"You are viewing the last successful run of this kernel. Click here to see the current version with an error.\" Then when I click that link, I'm not shown any error, if I click 'log' on the sidebar I'm not shown any log, and there's no sidebar link for the output csv, even though it should have been generated per the log message above.</p>\n\n<p>This is really confusing to me and I strongly suspect is a bug on kaggle's side, though perhaps I'm wrong. Would really appreciate any clarification as to what's going on.</p>\n\n<p>PS: <img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F320579%2F577bf8e376197cb2fc71b346fc6c3b66%2Fscreenshot%20kaggle%20mysterious%20error.png?generation=1566877446223474&amp;alt=media\" alt=\"\"></p>",
  "messages": [
    {
      "id": "608653",
      "postDate": "08/27/2019 03:46:09",
      "content": "<p>Screenshot attached. </p>\n\n<p>The last code line in my kernel is <code>print(\"finished writing submission.csv\")</code> and when I commit the kernel, the log gets to <code>finished writing submissions.csv</code> without generating any errors. And as shown in the screenshot, the version is marked as \"complete\" in green. However, in the bottom of the screenshot, you can see the version is shown as still processing (the circular dots). That goes on indefinitely. </p>\n\n<p>Then when I open the kernel from a new window to get to the \"submit csv to competition\" button, I get a message that \"You are viewing the last successful run of this kernel. Click here to see the current version with an error.\" Then when I click that link, I'm not shown any error, if I click 'log' on the sidebar I'm not shown any log, and there's no sidebar link for the output csv, even though it should have been generated per the log message above.</p>\n\n<p>This is really confusing to me and I strongly suspect is a bug on kaggle's side, though perhaps I'm wrong. Would really appreciate any clarification as to what's going on.</p>\n\n<p>PS: <img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F320579%2F577bf8e376197cb2fc71b346fc6c3b66%2Fscreenshot%20kaggle%20mysterious%20error.png?generation=1566877446223474&amp;alt=media\" alt=\"\"></p>",
      "rawMarkdown": "Screenshot attached. \n\nThe last code line in my kernel is `print(\"finished writing submission.csv\")` and when I commit the kernel, the log gets to `finished writing submissions.csv` without generating any errors. And as shown in the screenshot, the version is marked as \"complete\" in green. However, in the bottom of the screenshot, you can see the version is shown as still processing (the circular dots). That goes on indefinitely. \n\nThen when I open the kernel from a new window to get to the \"submit csv to competition\" button, I get a message that \"You are viewing the last successful run of this kernel. Click here to see the current version with an error.\" Then when I click that link, I'm not shown any error, if I click 'log' on the sidebar I'm not shown any log, and there's no sidebar link for the output csv, even though it should have been generated per the log message above.\n\nThis is really confusing to me and I strongly suspect is a bug on kaggle's side, though perhaps I'm wrong. Would really appreciate any clarification as to what's going on.\n\nPS: ![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F320579%2F577bf8e376197cb2fc71b346fc6c3b66%2Fscreenshot%20kaggle%20mysterious%20error.png?generation=1566877446223474&amp;alt=media)",
      "votes": null
    },
    {
      "id": "608662",
      "postDate": "08/27/2019 03:58:29",
      "content": "<p>*<em>EDIT : *</em> It seems all of us face commit errors in these 1-2 days. Maybe there're actually problems on the server side.</p>",
      "rawMarkdown": "**EDIT : ** It seems all of us face commit errors in these 1-2 days. Maybe there're actually problems on the server side.",
      "votes": null
    },
    {
      "id": "608673",
      "postDate": "08/27/2019 04:10:23",
      "content": "<p>Great to see its not just me.</p>\n\n<p>It works perfectly fine when I restart and run through in interactive mode, and I can't glean any information from whatever Error it is trying to give.</p>\n\n<p>I have a suspicion its related to the recent caps on GPU usage with instances; perhaps a recent bug in a latest push.</p>",
      "rawMarkdown": "Great to see its not just me.\n\nIt works perfectly fine when I restart and run through in interactive mode, and I can't glean any information from whatever Error it is trying to give.\n\nI have a suspicion its related to the recent caps on GPU usage with instances; perhaps a recent bug in a latest push.",
      "votes": null
    },
    {
      "id": "608871",
      "postDate": "08/27/2019 08:29:41",
      "content": "<p>same problem </p>",
      "rawMarkdown": "same problem",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 608662,
      "author_name": "ratthachat",
      "author_url": "",
      "post_date": "08/27/2019 03:58:29",
      "content": "<p>*<em>EDIT : *</em> It seems all of us face commit errors in these 1-2 days. Maybe there're actually problems on the server side.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 608673,
      "author_name": "haydenmuscat",
      "author_url": "",
      "post_date": "08/27/2019 04:10:23",
      "content": "<p>Great to see its not just me.</p>\n\n<p>It works perfectly fine when I restart and run through in interactive mode, and I can't glean any information from whatever Error it is trying to give.</p>\n\n<p>I have a suspicion its related to the recent caps on GPU usage with instances; perhaps a recent bug in a latest push.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 608871,
      "author_name": "chanhu",
      "author_url": "",
      "post_date": "08/27/2019 08:29:41",
      "content": "<p>same problem </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "608653": "Screenshot attached. \n\nThe last code line in my kernel is `print(\"finished writing submission.csv\")` and when I commit the kernel, the log gets to `finished writing submissions.csv` without generating any errors. And as shown in the screenshot, the version is marked as \"complete\" in green. However, in the bottom of the screenshot, you can see the version is shown as still processing (the circular dots). That goes on indefinitely. \n\nThen when I open the kernel from a new window to get to the \"submit csv to competition\" button, I get a message that \"You are viewing the last successful run of this kernel. Click here to see the current version with an error.\" Then when I click that link, I'm not shown any error, if I click 'log' on the sidebar I'm not shown any log, and there's no sidebar link for the output csv, even though it should have been generated per the log message above.\n\nThis is really confusing to me and I strongly suspect is a bug on kaggle's side, though perhaps I'm wrong. Would really appreciate any clarification as to what's going on.\n\nPS: ![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F320579%2F577bf8e376197cb2fc71b346fc6c3b66%2Fscreenshot%20kaggle%20mysterious%20error.png?generation=1566877446223474&amp;alt=media)",
    "608662": "**EDIT : ** It seems all of us face commit errors in these 1-2 days. Maybe there're actually problems on the server side.",
    "608673": "Great to see its not just me.\n\nIt works perfectly fine when I restart and run through in interactive mode, and I can't glean any information from whatever Error it is trying to give.\n\nI have a suspicion its related to the recent caps on GPU usage with instances; perhaps a recent bug in a latest push.",
    "608871": "same problem"
  },
  "source": "meta"
}