-
Notifications
You must be signed in to change notification settings - Fork 70
Publish fails with exception RestClient::InternalServerError
#22
Comments
Hmm, I'm also getting a
|
Hi, this looks like problem with Apiary itself. I can confirm it and we'll take a look. I'm closing this one as it's unrelated to apiary client, but I'll let you know once it's fixed. If you'd write to support@apiary.io, it would be awesome as we can talk about particular API/blueprints should it be related (I don't think so in this case) and we'll let you know immediately after the fix. |
Thanks, Almad. I will email support. You might consider changing the client to handle this case and print a more understandable error message to the user. Just an idea. Thanks your work on this library, by the way—the "publish" feature has saved my team and me a lot of time and headache. :-) |
For anybody encountering this issue in the future: my problem was invalid syntax. When I copied the contents of the |
For what it's worth: You can also validate your blueprints using http://apiblueprint.org or offline with the Alternatively, if you are using Sublime Text 3 make sure to check out the /~https://github.com/apiaryio/api-blueprint-sublime-plugin plugin. |
I've been calling
apiary publish
for a while now, but it recently stopped working.The command I use is:
apiary publish --api-name <redacted>
It now gives the following stack trace:
As you can tell from the stack trace, this is with Ruby version 1.9.2-p136 and Apiary gem version 0.0.8.
The text was updated successfully, but these errors were encountered: