I am getting this error for a while,the kernel is definitely running to end and then it fails. The log says
\n\nFailed validating 'additionalProperties' in markdown_cell:\n5637.2s119\n5637.2s120On instance['cells'][0]:\n5637.2s121{'cell_type': 'markdown',\n5637.2s122 'execution_count': None,\n5637.2s123 'metadata': {},\n5637.2s124 'source': '## About this notebook\\n'\n5637.2s125 '\\n'\n5637.2s126 '*[Jigsaw Multilingual Toxic Comment Clas...'}\n5638.4s127[NbConvertApp] Writing 385216 bytes to __results__.html\n5638.4s128\n5638.4s130Failed. Exited with code 1.\n
Can someone help me fix this ?
", "messages": [ { "id": "845162", "postDate": "05/13/2020 04:48:20", "content": "I am getting this error for a while,the kernel is definitely running to end and then it fails. The log says
\n\nFailed validating 'additionalProperties' in markdown_cell:\n5637.2s119\n5637.2s120On instance['cells'][0]:\n5637.2s121{'cell_type': 'markdown',\n5637.2s122 'execution_count': None,\n5637.2s123 'metadata': {},\n5637.2s124 'source': '## About this notebook\\n'\n5637.2s125 '\\n'\n5637.2s126 '*[Jigsaw Multilingual Toxic Comment Clas...'}\n5638.4s127[NbConvertApp] Writing 385216 bytes to __results__.html\n5638.4s128\n5638.4s130Failed. Exited with code 1.\n
Can someone help me fix this ?
", "rawMarkdown": "I am getting this error for a while,the kernel is definitely running to end and then it fails. The log says\n\n`Failed validating 'additionalProperties' in markdown_cell:\n5637.2s119\n5637.2s120On instance['cells'][0]:\n5637.2s121{'cell_type': 'markdown',\n5637.2s122 'execution_count': None,\n5637.2s123 'metadata': {},\n5637.2s124 'source': '## About this notebook\\n'\n5637.2s125 '\\n'\n5637.2s126 '*[Jigsaw Multilingual Toxic Comment Clas...'}\n5638.4s127[NbConvertApp] Writing 385216 bytes to __results__.html\n5638.4s128\n5638.4s130Failed. Exited with code 1.\n`\n\nCan someone help me fix this ?", "votes": null }, { "id": "845166", "postDate": "05/13/2020 04:51:18", "content": "I got a similar error. @martingorner Could you please help? It happend multiple times today.
", "rawMarkdown": "I got a similar error. @martingorner Could you please help? It happend multiple times today.", "votes": null }, { "id": "845193", "postDate": "05/13/2020 05:05:09", "content": "It happened twice to me yesterday.I hope he can help.
", "rawMarkdown": "It happened twice to me yesterday.I hope he can help.", "votes": null }, { "id": "845206", "postDate": "05/13/2020 05:13:23", "content": "yeah brother @shahules me too facing issues with kernels since yesterday! I am getting
\n\n\n", "rawMarkdown": "yeah brother @shahules me too facing issues with kernels since yesterday! I am getting\n > failed to mount data: ContainerExecInspect: Cannot connect to the Docker daemon at tcp://172.21.64.137:2375. Is the docker daemon running? \n@kaggleteam please look into this issues. Thank you", "votes": null }, { "id": "845238", "postDate": "05/13/2020 05:30:46", "content": "failed to mount data: ContainerExecInspect: Cannot connect to the Docker daemon at tcp://172.21.64.137:2375. Is the docker daemon running? \n @kaggleteam please look into this issues. Thank you
\n
@ratan123 I was not active in the competition,but I was surprised that no one raised this issue yesterday itself.
", "rawMarkdown": "ratan123 I was not active in the competition,but I was surprised that no one raised this issue yesterday itself.", "votes": null }, { "id": "845255", "postDate": "05/13/2020 05:44:40", "content": "I have the same error from yesterday! I find the error come from \ntokenizer = transformers.XLMRobertaTokenizer.from_pretrained('xlm-roberta-large') \nBut I don't know how to deal with it. I think it isn't a unique problem for me, perhaps it' s kaggle's error.
@shahules I am pretty sure it's an offical problem, because my kernel which run successfully a month ago failed with code 1 now.
", "rawMarkdown": "shahules I am pretty sure it's an offical problem, because my kernel which run successfully a month ago failed with code 1 now.", "votes": null }, { "id": "845334", "postDate": "05/13/2020 06:59:25", "content": "It has been running when i am debugging after when commiting i got the problem. Now its commiting smoothly i guess. waiting for full version of my kernel to run. @shangweichen
", "rawMarkdown": "It has been running when i am debugging after when commiting i got the problem. Now its commiting smoothly i guess. waiting for full version of my kernel to run. @shangweichen", "votes": null }, { "id": "845512", "postDate": "05/13/2020 08:50:19", "content": "@shangweichen check out this link: https://www.kaggle.com/product-feedback/150542
\n\ndisabling progress bar worked:\n\nimport logging\nlogging.getLogger().setLevel(logging.NOTSET)\n
@junlingoh Thank you very much! It seems that it works.😊
", "rawMarkdown": "junlingoh Thank you very much! It seems that it works.😊", "votes": null }, { "id": "846186", "postDate": "05/13/2020 16:04:01", "content": "@ratan123 The docker daemon error is a transient issue I'm looking into, retrying fixes that.
\n\nThe additionalProperties issue is something we are looking into, we haven't released a new image in a couple weeks so it's strange that we're suddenly seeing issues like the tqdm one.
", "rawMarkdown": "ratan123 The docker daemon error is a transient issue I'm looking into, retrying fixes that.\n\nThe additionalProperties issue is something we are looking into, we haven't released a new image in a couple weeks so it's strange that we're suddenly seeing issues like the tqdm one.", "votes": null }, { "id": "846195", "postDate": "05/13/2020 16:07:01", "content": "Ah got it @herbison . Yeah me too facing issues with tqdm. Hope it resolves soon.Thank you
", "rawMarkdown": "Ah got it @herbison . Yeah me too facing issues with tqdm. Hope it resolves soon.Thank you", "votes": null }, { "id": "846300", "postDate": "05/13/2020 17:03:13", "content": "@shangweichen didn't work for me.What about you?
", "rawMarkdown": "shangweichen didn't work for me.What about you?", "votes": null }, { "id": "846357", "postDate": "05/13/2020 17:48:10", "content": "The disabling progress bar trick worked for me. Thanks for sharing.
", "rawMarkdown": "The disabling progress bar trick worked for me. Thanks for sharing.", "votes": null }, { "id": "846360", "postDate": "05/13/2020 17:51:18", "content": "We've found the issue, our nbformat version regressed to a version known to have trouble with widgets (like tqdm). We're working on rolling out a corrected version right now.
", "rawMarkdown": "We've found the issue, our nbformat version regressed to a version known to have trouble with widgets (like tqdm). We're working on rolling out a corrected version right now.", "votes": null }, { "id": "846575", "postDate": "05/13/2020 21:10:20", "content": "The problem has been fixed. Unfortunately, you may have to recreate the notebook which contains some wrong metadata.
", "rawMarkdown": "The problem has been fixed. Unfortunately, you may have to recreate the notebook which contains some wrong metadata.", "votes": null }, { "id": "846729", "postDate": "05/14/2020 00:58:36", "content": "@gphilmod Thanks for fixing the issue !\nDo you mean recreate the entire notebook or just launch again a commit ? Because the issue was not here few days ago, so I do not understand if we need to recreate a new notebook ?
", "rawMarkdown": "gphilmod Thanks for fixing the issue !\nDo you mean recreate the entire notebook or just launch again a commit ? Because the issue was not here few days ago, so I do not understand if we need to recreate a new notebook ?", "votes": null }, { "id": "846772", "postDate": "05/14/2020 02:03:25", "content": "It's possible the cells of existing notebooks now have metadata that nbconvert can't handle, you'll need to at least recreate the cells I believe, creating a new notebook is one way to accomplish that, deleting/recreate cells is another way.
", "rawMarkdown": "It's possible the cells of existing notebooks now have metadata that nbconvert can't handle, you'll need to at least recreate the cells I believe, creating a new notebook is one way to accomplish that, deleting/recreate cells is another way.", "votes": null } ], "comments": [ { "id": 845166, "author_name": "luohongchen1993", "author_url": "", "post_date": "05/13/2020 04:51:18", "content": "I got a similar error. @martingorner Could you please help? It happend multiple times today.
", "votes": null, "replies": [ { "id": 845193, "author_name": "shahules", "author_url": "", "post_date": "05/13/2020 05:05:09", "content": "It happened twice to me yesterday.I hope he can help.
", "votes": null, "replies": [] } ] }, { "id": 845206, "author_name": "ratan123", "author_url": "", "post_date": "05/13/2020 05:13:23", "content": "yeah brother @shahules me too facing issues with kernels since yesterday! I am getting
\n\n\n", "votes": null, "replies": [ { "id": 845238, "author_name": "shahules", "author_url": "", "post_date": "05/13/2020 05:30:46", "content": "failed to mount data: ContainerExecInspect: Cannot connect to the Docker daemon at tcp://172.21.64.137:2375. Is the docker daemon running? \n @kaggleteam please look into this issues. Thank you
\n
@ratan123 I was not active in the competition,but I was surprised that no one raised this issue yesterday itself.
", "votes": null, "replies": [] }, { "id": 845255, "author_name": "shangweichen", "author_url": "", "post_date": "05/13/2020 05:44:40", "content": "I have the same error from yesterday! I find the error come from \ntokenizer = transformers.XLMRobertaTokenizer.from_pretrained('xlm-roberta-large') \nBut I don't know how to deal with it. I think it isn't a unique problem for me, perhaps it' s kaggle's error.
@shahules I am pretty sure it's an offical problem, because my kernel which run successfully a month ago failed with code 1 now.
", "votes": null, "replies": [] }, { "id": 845334, "author_name": "ratan123", "author_url": "", "post_date": "05/13/2020 06:59:25", "content": "It has been running when i am debugging after when commiting i got the problem. Now its commiting smoothly i guess. waiting for full version of my kernel to run. @shangweichen
", "votes": null, "replies": [] }, { "id": 845512, "author_name": "junlingoh", "author_url": "", "post_date": "05/13/2020 08:50:19", "content": "@shangweichen check out this link: https://www.kaggle.com/product-feedback/150542
\n\ndisabling progress bar worked:\n\nimport logging\nlogging.getLogger().setLevel(logging.NOTSET)\n
@junlingoh Thank you very much! It seems that it works.😊
", "votes": null, "replies": [] }, { "id": 846186, "author_name": "herbison", "author_url": "", "post_date": "05/13/2020 16:04:01", "content": "@ratan123 The docker daemon error is a transient issue I'm looking into, retrying fixes that.
\n\nThe additionalProperties issue is something we are looking into, we haven't released a new image in a couple weeks so it's strange that we're suddenly seeing issues like the tqdm one.
", "votes": null, "replies": [] }, { "id": 846195, "author_name": "ratan123", "author_url": "", "post_date": "05/13/2020 16:07:01", "content": "Ah got it @herbison . Yeah me too facing issues with tqdm. Hope it resolves soon.Thank you
", "votes": null, "replies": [] }, { "id": 846300, "author_name": "shahules", "author_url": "", "post_date": "05/13/2020 17:03:13", "content": "@shangweichen didn't work for me.What about you?
", "votes": null, "replies": [] }, { "id": 846357, "author_name": "luohongchen1993", "author_url": "", "post_date": "05/13/2020 17:48:10", "content": "The disabling progress bar trick worked for me. Thanks for sharing.
", "votes": null, "replies": [] }, { "id": 846360, "author_name": "herbison", "author_url": "", "post_date": "05/13/2020 17:51:18", "content": "We've found the issue, our nbformat version regressed to a version known to have trouble with widgets (like tqdm). We're working on rolling out a corrected version right now.
", "votes": null, "replies": [] } ] }, { "id": 846575, "author_name": "gphilmod", "author_url": "", "post_date": "05/13/2020 21:10:20", "content": "The problem has been fixed. Unfortunately, you may have to recreate the notebook which contains some wrong metadata.
", "votes": null, "replies": [ { "id": 846729, "author_name": "ludovick", "author_url": "", "post_date": "05/14/2020 00:58:36", "content": "@gphilmod Thanks for fixing the issue !\nDo you mean recreate the entire notebook or just launch again a commit ? Because the issue was not here few days ago, so I do not understand if we need to recreate a new notebook ?
", "votes": null, "replies": [] }, { "id": 846772, "author_name": "herbison", "author_url": "", "post_date": "05/14/2020 02:03:25", "content": "It's possible the cells of existing notebooks now have metadata that nbconvert can't handle, you'll need to at least recreate the cells I believe, creating a new notebook is one way to accomplish that, deleting/recreate cells is another way.
", "votes": null, "replies": [] } ] } ], "raw_markdown_by_id": { "845162": "I am getting this error for a while,the kernel is definitely running to end and then it fails. The log says\n\n`Failed validating 'additionalProperties' in markdown_cell:\n5637.2s119\n5637.2s120On instance['cells'][0]:\n5637.2s121{'cell_type': 'markdown',\n5637.2s122 'execution_count': None,\n5637.2s123 'metadata': {},\n5637.2s124 'source': '## About this notebook\\n'\n5637.2s125 '\\n'\n5637.2s126 '*[Jigsaw Multilingual Toxic Comment Clas...'}\n5638.4s127[NbConvertApp] Writing 385216 bytes to __results__.html\n5638.4s128\n5638.4s130Failed. Exited with code 1.\n`\n\nCan someone help me fix this ?", "845166": "I got a similar error. @martingorner Could you please help? It happend multiple times today.", "845193": "It happened twice to me yesterday.I hope he can help.", "845206": "yeah brother @shahules me too facing issues with kernels since yesterday! I am getting\n > failed to mount data: ContainerExecInspect: Cannot connect to the Docker daemon at tcp://172.21.64.137:2375. Is the docker daemon running? \n@kaggleteam please look into this issues. Thank you", "845238": "ratan123 I was not active in the competition,but I was surprised that no one raised this issue yesterday itself.", "845255": "I have the same error from yesterday! I find the error come from \n`tokenizer = transformers.XLMRobertaTokenizer.from_pretrained('xlm-roberta-large')` \nBut I don't know how to deal with it. I think it isn't a unique problem for me, perhaps it' s kaggle's error.", "845326": "shahules I am pretty sure it's an offical problem, because my kernel which run successfully a month ago failed with code 1 now.", "845334": "It has been running when i am debugging after when commiting i got the problem. Now its commiting smoothly i guess. waiting for full version of my kernel to run. @shangweichen", "845512": "shangweichen check out this link: https://www.kaggle.com/product-feedback/150542\n\ndisabling progress bar worked:\n```\nimport logging\nlogging.getLogger().setLevel(logging.NOTSET)\n```", "845536": "junlingoh Thank you very much! It seems that it works.😊", "846186": "ratan123 The docker daemon error is a transient issue I'm looking into, retrying fixes that.\n\nThe additionalProperties issue is something we are looking into, we haven't released a new image in a couple weeks so it's strange that we're suddenly seeing issues like the tqdm one.", "846195": "Ah got it @herbison . Yeah me too facing issues with tqdm. Hope it resolves soon.Thank you", "846300": "shangweichen didn't work for me.What about you?", "846357": "The disabling progress bar trick worked for me. Thanks for sharing.", "846360": "We've found the issue, our nbformat version regressed to a version known to have trouble with widgets (like tqdm). We're working on rolling out a corrected version right now.", "846575": "The problem has been fixed. Unfortunately, you may have to recreate the notebook which contains some wrong metadata.", "846729": "gphilmod Thanks for fixing the issue !\nDo you mean recreate the entire notebook or just launch again a commit ? Because the issue was not here few days ago, so I do not understand if we need to recreate a new notebook ?", "846772": "It's possible the cells of existing notebooks now have metadata that nbconvert can't handle, you'll need to at least recreate the cells I believe, creating a new notebook is one way to accomplish that, deleting/recreate cells is another way." }, "source": "meta" }