{
  "id": 172663,
  "title": "Error while extracting GCS Path link",
  "url": "/competitions/siim-isic-melanoma-classification/discussion/172663",
  "author_name": "",
  "post_date": "2020-08-06T02:30:29.684751300Z",
  "votes": 10,
  "comment_count": 5,
  "views": 0,
  "content": "<p>I am not sure if i am the one who is facing this issue. While I was trying to retrieve the gcs path for SIIM Melanoma competition, i was getting the below error. I didn't face this error till yesterday night. </p>\n\n<p>Update: Getting the same error for all image sizes. Tried with 384, 512 and 768. </p>\n\n<p>Tagging kaggle team <a href=\"/juliaelliott\">@juliaelliott</a> , <a href=\"/inversion\">@inversion</a> </p>",
  "messages": [
    {
      "id": "959894",
      "postDate": "08/06/2020 02:30:29",
      "content": "<p>I am not sure if i am the one who is facing this issue. While I was trying to retrieve the gcs path for SIIM Melanoma competition, i was getting the below error. I didn't face this error till yesterday night. </p>\n\n<p>Update: Getting the same error for all image sizes. Tried with 384, 512 and 768. </p>\n\n<p>Tagging kaggle team <a href=\"/juliaelliott\">@juliaelliott</a> , <a href=\"/inversion\">@inversion</a> </p>",
      "rawMarkdown": "I am not sure if i am the one who is facing this issue. While I was trying to retrieve the gcs path for SIIM Melanoma competition, i was getting the below error. I didn't face this error till yesterday night. \n\nUpdate: Getting the same error for all image sizes. Tried with 384, 512 and 768. \n\nTagging kaggle team @juliaelliott , @inversion",
      "votes": null
    },
    {
      "id": "959931",
      "postDate": "08/06/2020 03:14:41",
      "content": "<p>same for me <img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1614008%2F4918b8b45a207fe43455c77f5a72f808%2FScreenshot%20(8\" alt=\"\">.png?generation=1596683679958976&amp;alt=media)</p>",
      "rawMarkdown": "same for me ![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1614008%2F4918b8b45a207fe43455c77f5a72f808%2FScreenshot%20(8).png?generation=1596683679958976&amp;alt=media)",
      "votes": null
    },
    {
      "id": "959982",
      "postDate": "08/06/2020 04:16:47",
      "content": "<p>Same for me.</p>\n\n<p><code>\nBackendError: Unexpected response from the service. Response: {'errors': ['Unauthenticated'], 'error': {'code': 16}, 'wasSuccessful': False}.\n</code></p>\n\n<p>Something went wrong with Kaggle's backend?</p>",
      "rawMarkdown": "Same for me.\n\n```\nBackendError: Unexpected response from the service. Response: {'errors': ['Unauthenticated'], 'error': {'code': 16}, 'wasSuccessful': False}.\n```\n\nSomething went wrong with Kaggle's backend?",
      "votes": null
    },
    {
      "id": "959985",
      "postDate": "08/06/2020 04:18:46",
      "content": "<p>Yeah, seems like so. Hope Kaggle team resolves it at the earliest. </p>",
      "rawMarkdown": "Yeah, seems like so. Hope Kaggle team resolves it at the earliest.",
      "votes": null
    },
    {
      "id": "960004",
      "postDate": "08/06/2020 04:37:52",
      "content": "<p><a href=\"/manojprabhaakr\">@manojprabhaakr</a> , <a href=\"/coolcoder22\">@coolcoder22</a> , <a href=\"/code1110\">@code1110</a> \nSorry about that. Please, switch to the latest docker image (\"Always use latest environment\" option) by clicking on Preferences under Settings section of the notebook. We had to make some changes to <code>KaggleDatasets</code> which are not backwards compatible and which unfortunately can only be obtained if you are using the latest docker image.</p>",
      "rawMarkdown": "manojprabhaakr , @coolcoder22 , @code1110 \nSorry about that. Please, switch to the latest docker image (\"Always use latest environment\" option) by clicking on Preferences under Settings section of the notebook. We had to make some changes to `KaggleDatasets` which are not backwards compatible and which unfortunately can only be obtained if you are using the latest docker image.",
      "votes": null
    },
    {
      "id": "960014",
      "postDate": "08/06/2020 04:49:09",
      "content": "<p>Many thanks <a href=\"/ifigotin\">@ifigotin</a> . The issue has been resolved. Thanks once again. </p>",
      "rawMarkdown": "Many thanks @ifigotin . The issue has been resolved. Thanks once again.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 959931,
      "author_name": "coolcoder22",
      "author_url": "",
      "post_date": "08/06/2020 03:14:41",
      "content": "<p>same for me <img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1614008%2F4918b8b45a207fe43455c77f5a72f808%2FScreenshot%20(8\" alt=\"\">.png?generation=1596683679958976&amp;alt=media)</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 959982,
      "author_name": "code1110",
      "author_url": "",
      "post_date": "08/06/2020 04:16:47",
      "content": "<p>Same for me.</p>\n\n<p><code>\nBackendError: Unexpected response from the service. Response: {'errors': ['Unauthenticated'], 'error': {'code': 16}, 'wasSuccessful': False}.\n</code></p>\n\n<p>Something went wrong with Kaggle's backend?</p>",
      "votes": null,
      "replies": [
        {
          "id": 959985,
          "author_name": "manojprabhaakr",
          "author_url": "",
          "post_date": "08/06/2020 04:18:46",
          "content": "<p>Yeah, seems like so. Hope Kaggle team resolves it at the earliest. </p>",
          "votes": null,
          "replies": []
        }
      ]
    },
    {
      "id": 960004,
      "author_name": "ifigotin",
      "author_url": "",
      "post_date": "08/06/2020 04:37:52",
      "content": "<p><a href=\"/manojprabhaakr\">@manojprabhaakr</a> , <a href=\"/coolcoder22\">@coolcoder22</a> , <a href=\"/code1110\">@code1110</a> \nSorry about that. Please, switch to the latest docker image (\"Always use latest environment\" option) by clicking on Preferences under Settings section of the notebook. We had to make some changes to <code>KaggleDatasets</code> which are not backwards compatible and which unfortunately can only be obtained if you are using the latest docker image.</p>",
      "votes": null,
      "replies": []
    },
    {
      "id": 960014,
      "author_name": "manojprabhaakr",
      "author_url": "",
      "post_date": "08/06/2020 04:49:09",
      "content": "<p>Many thanks <a href=\"/ifigotin\">@ifigotin</a> . The issue has been resolved. Thanks once again. </p>",
      "votes": null,
      "replies": []
    }
  ],
  "raw_markdown_by_id": {
    "959894": "I am not sure if i am the one who is facing this issue. While I was trying to retrieve the gcs path for SIIM Melanoma competition, i was getting the below error. I didn't face this error till yesterday night. \n\nUpdate: Getting the same error for all image sizes. Tried with 384, 512 and 768. \n\nTagging kaggle team @juliaelliott , @inversion",
    "959931": "same for me ![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F1614008%2F4918b8b45a207fe43455c77f5a72f808%2FScreenshot%20(8).png?generation=1596683679958976&amp;alt=media)",
    "959982": "Same for me.\n\n```\nBackendError: Unexpected response from the service. Response: {'errors': ['Unauthenticated'], 'error': {'code': 16}, 'wasSuccessful': False}.\n```\n\nSomething went wrong with Kaggle's backend?",
    "959985": "Yeah, seems like so. Hope Kaggle team resolves it at the earliest.",
    "960004": "manojprabhaakr , @coolcoder22 , @code1110 \nSorry about that. Please, switch to the latest docker image (\"Always use latest environment\" option) by clicking on Preferences under Settings section of the notebook. We had to make some changes to `KaggleDatasets` which are not backwards compatible and which unfortunately can only be obtained if you are using the latest docker image.",
    "960014": "Many thanks @ifigotin . The issue has been resolved. Thanks once again."
  },
  "source": "meta"
}