rails-assets icon indicating copy to clipboard operation
rails-assets copied to clipboard

Published 20 hours ago • verified publisher icon tenex

500 error upon POSTing new version to /components

Open drusepth opened this issue 6 years ago • 3 comments

In trying to trigger a fetch of a new version from GitHub with the following code:

curl -H "Content-Type: application/json" \
     -X POST \
     -d "{ \"component\": { \"name\": \"formrenderer-base\", \"version\": \"1.2.9\" } }" \
     "https://rails-assets.org/components"

I am receiving the following response:

<!DOCTYPE html>
<html>
<head>
  <title>We're sorry, but something went wrong (500)</title>
  <style>
  body {
    background-color: #EFEFEF;
    color: #2E2F30;
    text-align: center;
    font-family: arial, sans-serif;
  }

  div.dialog {
    width: 25em;
    margin: 4em auto 0 auto;
    border: 1px solid #CCC;
    border-right-color: #999;
    border-left-color: #999;
    border-bottom-color: #BBB;
    border-top: #B00100 solid 4px;
    border-top-left-radius: 9px;
    border-top-right-radius: 9px;
    background-color: white;
    padding: 7px 4em 0 4em;
  }

  h1 {
    font-size: 100%;
    color: #730E15;
    line-height: 1.5em;
  }

  body > p {
    width: 33em;
    margin: 0 auto 1em;
    padding: 1em 0;
    background-color: #F7F7F7;
    border: 1px solid #CCC;
    border-right-color: #999;
    border-bottom-color: #999;
    border-bottom-left-radius: 4px;
    border-bottom-right-radius: 4px;
    border-top-color: #DADADA;
    color: #666;
    box-shadow:0 3px 8px rgba(50, 50, 50, 0.17);
  }
  </style>
</head>

<body>
  <!-- This file lives in public/500.html -->
  <div class="dialog">
    <h1>We're sorry, but something went wrong.</h1>
  </div>
  <p>If you are the application owner check the logs for more information.</p>
</body>
</html>

I've tried this on two separate machines that have released previous versions successfully and receive the same response on both. I can see that the 1.2.9 tag exists. I don't see a failed build for the project on the rails-assets status page, so I'm assuming it's not even making it to the build stage. I can also see that the latest version available on rails-assets is 1.2.8.

Could someone provide guidance on perhaps what might be happening, or what I might need to be doing differently to get releases working again?

drusepth avatar Dec 07 '17 01:12 drusepth