Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bash script fails #2603

Open
green-arrow opened this issue Oct 3, 2016 · 2 comments
Open

bash script fails #2603

green-arrow opened this issue Oct 3, 2016 · 2 comments

Comments

@green-arrow
Copy link

When verifying my PGP key, I opted to go the bash script route. I copied and pasted the command that popped up in the modal, but it failed when pasted in the terminal:

Error in your post
-------------------

Code: 100
Name: INPUT_ERROR
Description: bad base 64 string

I had to end up pasting the contents in a bash script and getting rid of some extraneous newlines at the beginning of the command to get it to work correctly.

@maxtaco
Copy link
Contributor

maxtaco commented Oct 3, 2016

Yeah likely the post was truncated due to shell limits.

On Monday, October 3, 2016, Andrew Walton notifications@github.com wrote:

When verifying my PGP key, I opted to go the bash script route. I copied
and pasted the command that popped up in the modal, but it failed when
pasted in the terminal:

Error in your post

Code: 100
Name: INPUT_ERROR
Description: bad base 64 string

I had to end up pasting the contents in a bash script and getting rid of
some extraneous newlines at the beginning of the command to get it to work
correctly.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2603, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AA05_zrxTqffN2yQ06w2kBglLGd8L4IUks5qwYlngaJpZM4KNIwH
.

@S0AndS0
Copy link

S0AndS0 commented Oct 13, 2016

I've run into this issue on every operation that I've tried and found that till it is fixed there's one good option. But first a possible solution.

Possible solution

Perhaps the browser prompt is using markdown rendering rules, in which case removing the syntax language from the triple backtick that opens the code block should fix this issue. See the second code block verses the first within this comment in raw formatting mode.

Option one

Save browser's copy/past to terminal text editor

nano /tmp/validate.sh

paste into the above new document, then correct mangled new-lines. Hint every line but the last should have an escape (\) at the end.

change execution permission for the above file.

chmod 700 /tmp/validate.sh
### hey devs, special note for you all here. Looks like new lines (especially on mobile) get modified when
### using [```bash] for markdown rendering of code. This comment however didn't use [bash] or anything else but three back ticks to open and close
### so this comment should have a scroll bar at the bottom.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants