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

Output not generated if contents of output folder are deleted #170

Closed
6 tasks done
tech4GT opened this issue Feb 13, 2018 · 10 comments
Closed
6 tasks done

Output not generated if contents of output folder are deleted #170

tech4GT opened this issue Feb 13, 2018 · 10 comments

Comments

@tech4GT
Copy link
Member

tech4GT commented Feb 13, 2018

Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.

If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!

If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!😁

The problem

If the output folder is an empty directory (if you delete the contents of the ouput folder) the sequencer output will not get exported since callback is not called in that case
This line should be fixed

if(typeof(files)=="undefined") {

Solution
Add a check which enables the callback being called in the case the length of the files array is 0

Steps to fix

  • claim this issue with a comment
  • set up a repository locally and make sure that all tests pass
  • start a pull request (see contributing to Public Lab software) but mark it as "in progress"
  • fix the issue following the steps above
  • make sure all tests pass
  • alert someone via either the developers list (see below) to have your pull request merged. This may take a few extra steps depending on when you do it, but we'll help you out!

Please email the developers list (see https://publiclab.org/developers) if you have questions!

@tech4GT
Copy link
Member Author

tech4GT commented Feb 13, 2018

@jywarren this will make a good first timer issue please add the label😁

@jywarren
Copy link
Member

This does look like a good first-timers issue! Before we label it as such, would you mind reformatting it following some of these suggestions?

https://publiclab.org/n/13667

Thank you! It'll be exciting to see more people join in :-) 👍

@tech4GT
Copy link
Member Author

tech4GT commented Feb 16, 2018

@jywarren done, please have a look😁

@mayank1010
Copy link

i will give it a go

@tech4GT
Copy link
Member Author

tech4GT commented Feb 18, 2018

Sure mayank go ahead😁

@danielleshwed
Copy link

i am interested in working on this if it is available

@jywarren
Copy link
Member

@danielleshwed we'd love to have your help, @tech4GT maybe we could make another first timers issue since @mayank1010 is already working on this one?

Thanks!

@tech4GT
Copy link
Member Author

tech4GT commented Feb 19, 2018

@jywarren sure I'll do that right away
@danielleshwed welcome to the community 😁

@tech4GT
Copy link
Member Author

tech4GT commented Feb 20, 2018

@danielleshwed Jeff is busy right now, start with #177, just go through the contributing.md file to make a basic module and add the line referenced in the issue for the blur module, don't worry about the labels it's a relatively simple issue😁

@tech4GT
Copy link
Member Author

tech4GT commented Feb 22, 2018

@jywarren closing this issue now, thanks

@tech4GT tech4GT closed this as completed Feb 22, 2018
@jywarren jywarren mentioned this issue Mar 1, 2018
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants