{
  "id": 196374,
  "title": "submission error - no additional details",
  "url": "/competitions/riiid-test-answer-prediction/discussion/196374",
  "author_name": "",
  "post_date": "2020-11-10T23:11:33.099688500Z",
  "votes": 2,
  "comment_count": 2,
  "views": 0,
  "content": "<p>Hello Guys,<br>\nI m getting a error when I try to submit. No additional details are provided. Anyone facing same issue?</p>",
  "messages": [
    {
      "id": "1074664",
      "postDate": "11/10/2020 23:11:33",
      "content": "<p>Hello Guys,<br>\nI m getting a error when I try to submit. No additional details are provided. Anyone facing same issue?</p>",
      "rawMarkdown": "Hello Guys,\nI m getting a error when I try to submit. No additional details are provided. Anyone facing same issue?",
      "votes": null
    },
    {
      "id": "1074668",
      "postDate": "11/10/2020 23:18:08",
      "content": "<p>Right now - there's a bug in the API, but assuming that is fixed and is not the problem …..</p>\n<p>Hi - that's deliberate! We never get additional details. It is to prevent us gaming the system by introducing deliberate bugs when certain conditions occur. Of course, you can force a failure deliberately, but that is much more uncertain than being given exact information.</p>\n<p>BTW, there are lists in the Discussions of non-deliberate errors that cause failure. My most elusive error was a trailing tab character in a text file. It ran fine in the Kaggle Notebook window, but crashed the actual submission.</p>",
      "rawMarkdown": "Right now - there's a bug in the API, but assuming that is fixed and is not the problem .....\n\nHi - that's deliberate! We never get additional details. It is to prevent us gaming the system by introducing deliberate bugs when certain conditions occur. Of course, you can force a failure deliberately, but that is much more uncertain than being given exact information.\n\nBTW, there are lists in the Discussions of non-deliberate errors that cause failure. My most elusive error was a trailing tab character in a text file. It ran fine in the Kaggle Notebook window, but crashed the actual submission.",
      "votes": null
    },
    {
      "id": "1075070",
      "postDate": "11/11/2020 11:19:50",
      "content": "<p>many reasons for that, for me after debugging I found that there was no bug in my code, but the problems was that feature engineering takes too much time during submitting, because the test data is divided into more than 2000 patches. after optimizing my code (improving/remove the slow code) the submission was successful.</p>\n<p>also you can check this <a href=\"url\" target=\"_blank\">https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/192124</a> discussion for more reasons</p>",
      "rawMarkdown": "many reasons for that, for me after debugging I found that there was no bug in my code, but the problems was that feature engineering takes too much time during submitting, because the test data is divided into more than 2000 patches. after optimizing my code (improving/remove the slow code) the submission was successful.\n\nalso you can check this [https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/192124](url) discussion for more reasons",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1074668,
      "author_name": "mikel1",
      "author_url": "",
      "post_date": "11/10/2020 23:18:08",
      "content": "<p>Right now - there's a bug in the API, but assuming that is fixed and is not the problem …..</p>\n<p>Hi - that's deliberate! We never get additional details. It is to prevent us gaming the system by introducing deliberate bugs when certain conditions occur. Of course, you can force a failure deliberately, but that is much more uncertain than being given exact information.</p>\n<p>BTW, there are lists in the Discussions of non-deliberate errors that cause failure. My most elusive error was a trailing tab character in a text file. It ran fine in the Kaggle Notebook window, but crashed the actual submission.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 1075070,
      "author_name": "mohamadnawfal",
      "author_url": "",
      "post_date": "11/11/2020 11:19:50",
      "content": "<p>many reasons for that, for me after debugging I found that there was no bug in my code, but the problems was that feature engineering takes too much time during submitting, because the test data is divided into more than 2000 patches. after optimizing my code (improving/remove the slow code) the submission was successful.</p>\n<p>also you can check this <a href=\"url\" target=\"_blank\">https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/192124</a> discussion for more reasons</p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "1074664": "Hello Guys,\nI m getting a error when I try to submit. No additional details are provided. Anyone facing same issue?",
    "1074668": "Right now - there's a bug in the API, but assuming that is fixed and is not the problem .....\n\nHi - that's deliberate! We never get additional details. It is to prevent us gaming the system by introducing deliberate bugs when certain conditions occur. Of course, you can force a failure deliberately, but that is much more uncertain than being given exact information.\n\nBTW, there are lists in the Discussions of non-deliberate errors that cause failure. My most elusive error was a trailing tab character in a text file. It ran fine in the Kaggle Notebook window, but crashed the actual submission.",
    "1075070": "many reasons for that, for me after debugging I found that there was no bug in my code, but the problems was that feature engineering takes too much time during submitting, because the test data is divided into more than 2000 patches. after optimizing my code (improving/remove the slow code) the submission was successful.\n\nalso you can check this [https://www.kaggle.com/c/riiid-test-answer-prediction/discussion/192124](url) discussion for more reasons"
  },
  "source": "meta"
}