【问题标题】:ERROR: (gcloud.app.deploy) Error Response: [3] The following errors occurred while copying files to App Engine错误:(gcloud.app.deploy) 错误响应:[3] 将文件复制到 App Engine 时发生以下错误
【发布时间】:2019-03-19 00:58:12
【问题描述】:

当我尝试部署到谷歌应用引擎时收到此错误: 错误:(gcloud.app.deploy) 错误响应:[3] 将文件复制到 App Engine 时出现以下错误:

File https://storage.googleapis.com/staging.XXXXXXXX.appspot.com/04314f892fba4e2f44a86ab96eeb2a6b72ed93cd failed with: Conflicting SHA1 sum for file. Expected "6ae2b40e_68bc1a25_8cc5408c_bbd37316_fa642477" but received "04314f89_2fba4e2f_44a86ab9_6eeb2a6b_72ed93cd".
File https://storage.googleapis.com/staging.XXXXXXXX.appspot.com/d06cfbf61df973ee19498c5a6d8afd5c3f971cb1 failed with: Conflicting SHA1 sum for file. Expected "cf32ec49_c6023a31_6d3f4788_f187afcb_932d60df" but received "d06cfbf6_1df973ee_19498c5a_6d8afd5c_3f971cb1".

Details: [
  [
    {
      "@type": "type.googleapis.com/google.rpc.ResourceInfo",
      "description": "Conflicting SHA1 sum for file. Expected \"6ae2b40e_68bc1a25_8cc5408c_bbd37316_fa642477\" but received \"04314f89_2fba4e2f_44a86ab9_6eeb2a6b_72ed93cd\".",
      "resourceName": "https://storage.googleapis.com/staging.XXXXXXXX.appspot.com/04314f892fba4e2f44a86ab96eeb2a6b72ed93cd",
      "resourceType": "file"
    },
    {
      "@type": "type.googleapis.com/google.rpc.ResourceInfo",
      "description": "Conflicting SHA1 sum for file. Expected \"cf32ec49_c6023a31_6d3f4788_f187afcb_932d60df\" but received \"d06cfbf6_1df973ee_19498c5a_6d8afd5c_3f971cb1\".",
      "resourceName": "https://storage.googleapis.com/staging.XXXXXXXX.appspot.com/d06cfbf61df973ee19498c5a6d8afd5c3f971cb1",
      "resourceType": "file"
    }
  ]
]

【问题讨论】:

  • 您是否可能正在尝试使用大于 32 mb 的代码部署文件? - cloud.google.com/appengine/quotas#Code 此外,针对这种情况的解决方法可能是删除存储桶暂存。{Your-Project-ID}.appspot.com 位于 storage 下,因为它会删除任何可能导致此错误的临时文件。
  • 感谢@PhilippSh,删除暂存桶对我有用。

标签: google-app-engine gcloud


【解决方案1】:

针对这种情况的适当解决方法可能是删除存储桶 staging.{Your-Project-ID}.appspot.com,因为它会删除任何可能导致此错误的临时文件。

【讨论】:

  • 我清除了 staging.{project-id}.appspot.com 存储桶中的所有内容。但仍然失败。
【解决方案2】:

该错误可能是由于构建后您的应用中出现了临时文件。 (例如,对于 Flutter 应用,您可能会发现意外的 *.cache.dill 文件)

【讨论】:

    猜你喜欢
    • 2017-01-14
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2018-05-07
    • 2018-02-14
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    相关资源
    最近更新 更多