Permission Denied on Heroku about no-carrier HOT 20 OPEN

The Heroku instructions are courtesy of @zxqfox. I don't use Heroku myself.
Perhaps you need to chmod +x your shell script file?

from no-carrier.

Hmm. Maybe the +x permission change wasn't pushed to Heroku? Try git adding, committing, and pushing again.

from no-carrier.

Does
heroku run bash cron.daily.sh
happen to work?

from no-carrier.

I followed the process completely.
Did that too @cvrebert 👍

from no-carrier.

By the way, it lacks a command, git add .
just added that 👍 @cvrebert

Added a git command, if left, that broke the whole deploy process!

from no-carrier.

Great! Glad you got it working. Thanks for the fix!

from no-carrier.

No !!
It was an add-on mistake that was to be pointed out !!

I deployed successfully.
After the deploy process, I ran the command and it failed !

P.S. @cvrebert It's not working, Please open the thread 👍

from no-carrier.

We'd need the error message/log in order to help you.

from no-carrier.

I think, I gave you the log, It was just that only.

from no-carrier.

Again did, made a new app, followed the process.
Got the very same error. 😟

$ heroku run ./cron.daily.sh                                                    Running ./cron.daily.sh on hacke2323uieu23r... starting, run.3628 (Free)
Running ./cron.daily.sh on hacke2323uieu23r... connecting, run.3628 (Free)
Running ./cron.daily.sh on hacke2323uieu23r... up, run.3628 (Free)
bash: ./cron.daily.sh: Permission denied

ID : 3628

from no-carrier.

Hmm, the wiki post doesn't include a shebang line.
Does adding the line:
#!/bin/sh
to the start of cron.daily.sh help?

from no-carrier.

@cvrebert

$ heroku run bash cron.daily.sh
Running bash cron.daily.sh on hacke2323uieu23r... starting, run.1405 (Free)
Running bash cron.daily.sh on hacke2323uieu23r... connecting, run.1405 (Free)
Running bash cron.daily.sh on hacke2323uieu23r... up, run.1405 (Free)
2017-12-29 23:08:05,903 [ERROR] com.jcabi.aspects.aj.MethodValidator - JSR-303 validator failed to initialize: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath. (see http://aspects.jcabi.com/jsr-303.html)
USAGE: no-carrier <owner/repo> <label> <days>

I think it worked, right ?

Please help me in removing the error.

My cron job consists of :

java -jar no-carrier.jar owner/repo "" 1

I don't want to search for labels. 😟

from no-carrier.

Not sure what Heroku instructions but... How can I help you?

from no-carrier.

How to execute the application with label tag ? @zxqfox

from no-carrier.

Well, according to sources it's impossible now: https://github.com/twbs/no-carrier/blob/master/src/main/scala/com/getbootstrap/no_carrier/Main.scala#L32

Try something like space character or minus or !, but feels like you can't use it without passing label

from no-carrier.

I can re-build it from scratch and can modify that, Right @zxqfox ? ✨

from no-carrier.

@0x48piraj Well, always ;-D I'm not very familiar with scala so I can't help with it, but I can wish you a good luck! ;-)

from no-carrier.

Me too 😟
Maybe @cvrebert should treat this discussion as a feature-request 😊

from no-carrier.

Yes, a label is required. Not sure what your use-case is.
The point of the label is to require some type of review before auto-closing. Otherwise, e.g. an issue opened N days ago which no human project maintainer ever read could get auto-closed, which is bad.

from no-carrier.

Also, did #27 (comment) work?

from no-carrier.