-
Notifications
You must be signed in to change notification settings - Fork 210
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
CLI NOT WORKING #645
Comments
GitMate.io thinks the contributor most likely able to help you is @jywarren. Possibly related issues are #213 (Crop Module not working correctly), #557 (GIF generation is not working correctly), #631 (Take a photo feature not working), #100 (Multiple step support for CLI), and #386 (Link in the description does not work as required). |
1 similar comment
GitMate.io thinks the contributor most likely able to help you is @jywarren. Possibly related issues are #213 (Crop Module not working correctly), #557 (GIF generation is not working correctly), #631 (Take a photo feature not working), #100 (Multiple step support for CLI), and #386 (Link in the description does not work as required). |
Does the |
Hi, I believe this was addressed in
#637, but does it still
not work?
What concerns me is that the CLI failure appeared in Travis, but did not
trigger a Travis failure:
https://travis-ci.org/publiclab/image-sequencer/jobs/477001494#L1713
Can we:
1. confirm if the fix worked, and fix it if not
2. change the title of this issue to "CLI failure not causing Travis fail"
and address that issue as well?
Thank you!
…On Thu, Jan 10, 2019 at 9:42 AM HarshKhandeparkar ***@***.***> wrote:
Does the drawRectangle module work in browser on localhost ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#645 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJ1nUYqjIyl8MoRW8JhcrLf1ywGUIks5vB1EhgaJpZM4Z5oAS>
.
|
Thank you, I'd really appreciate that!
…On Thu, Jan 10, 2019, 8:24 PM Mridul97 ***@***.*** wrote:
@jywarren <https://github.com/jywarren> @tech4GT
<https://github.com/tech4GT> I tried it out, this error is not occuring
now. I would like to address the other issue of travis not failing even on
detecting the error. Thanks!
[image: ss_40]
<https://user-images.githubusercontent.com/21158457/51007475-ab3c8700-156d-11e9-9007-3a4ae37592f6.jpg>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#645 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJxtP9vnd5TsElFgV7r5Eo7EF-6Tnks5vB-e5gaJpZM4Z5oAS>
.
|
OK, closing this and opening a new one for why a CLI error didn't trigger a Travis failure! Moving to #659 Thanks, all! |
Glad to know this was fixed! 😄 |
This has been fixed. Closing this |
I am getting this error in the CLI
cc @Mridul97 @jywarren
The text was updated successfully, but these errors were encountered: