Skip to content

503 on publishing a crate #10098

Closed
Closed
@alexjg

Description

@alexjg

Current Behavior

I'm running cargo publish from within the crate I'm trying to publish (automerge_repo_rs) and I consistently get a 503 back from crates.io. I've tried refreshing my API token just in case that's the issue to no avail.

Here's an example response:

error: failed to publish to registry at https://crates.io

Caused by:
  failed to get a 200 OK response, got 503
  headers:
  	HTTP/2 503
  	content-type: text/html; charset=utf-8
  	content-length: 506
  	cache-control: no-cache, no-store
  	server: Cowboy
  	date: Thu, 28 Nov 2024 14:23:30 GMT
  	report-to: {"group":"heroku-nel","max_age":3600,"endpoints":[{"url":"https://nel.heroku.com/reports?ts=1732803811&sid=af571f24-03ee-46d1-9f90-ab9030c2c74c&s=9dHZ0W9GZnop99SEhzT0Dw2wrnjV3uEV9NgaUgnJvIM%3D"}]}
  	reporting-endpoints: heroku-nel=https://nel.heroku.com/reports?ts=1732803811&sid=af571f24-03ee-46d1-9f90-ab9030c2c74c&s=9dHZ0W9GZnop99SEhzT0Dw2wrnjV3uEV9NgaUgnJvIM%3D
  	nel: {"report_to":"heroku-nel","max_age":3600,"success_fraction":0.005,"failure_fraction":0.05,"response_headers":["Via"]}
  	x-cache: Error from cloudfront
  	via: 1.1 78ddfb54ad788c32ecf2935db37685b8.cloudfront.net (CloudFront)
  	x-amz-cf-pop: LHR62-C4
  	x-amz-cf-id: bbu6Bb5oolK_Vxd0YxQLuADCXI8wNm22AIElvoKaUFga_pntIclrdQ==
  	strict-transport-security: max-age=31536000; includeSubDomains
  	
  body:
  <!DOCTYPE html>
  	<html>
  	 <head>
  		<meta name="viewport" content="width=device-width, initial-scale=1">
  		<meta charset="utf-8">
  		<title>Application Error</title>
  		<style media="screen">
  		 html,body,iframe {
  			margin: 0;
  			padding: 0;
  		 }
  		 html,body {
  			height: 100%;
  			overflow: hidden;
  		 }
  		 iframe {
  			width: 100%;
  			height: 100%;
  			border: 0;
  		 }
  		</style>
  	 </head>
  	 <body>
  		<iframe src="//www.herokucdn.com/error-pages/application-error.html"></iframe>
  	 </body>
  	</html>

Expected Behavior

I expect cargo publish to successfully publish the crate to crates.io.

Steps To Reproduce

Obviously this will only work for me, but the steps I take are:

  1. Clone https://github.com/automerge/automerge-repo-rs
  2. git checkout v0.2.0
  3. cargo publish

Environment

  • OS: Arch Linux
  • rustup show

    Default host: x86_64-unknown-linux-gnu
    rustup home:  /home/alex/.rustup
    
    installed toolchains
    --------------------
    
    stable-x86_64-unknown-linux-gnu (default)
    nightly-x86_64-unknown-linux-gnu
    1.78-x86_64-unknown-linux-gnu
    1.81-x86_64-unknown-linux-gnu
    
    installed targets for active toolchain
    --------------------------------------
    
    wasm32-unknown-unknown
    x86_64-unknown-linux-gnu
    
    active toolchain
    ----------------
    
    stable-x86_64-unknown-linux-gnu (default)
    rustc 1.82.0 (f6e511eec 2024-10-15)

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions