Add below code with other badges code in README [![Contributors](https://img.shields.io/github/contributors/arshadkazmi42/ak-phrase.js.svg)](https://github.com/arshadkazmi42/ak-phrase.js/graphs/contributors)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file (https://github.com/publiclab/mapknitter/blob/main/app/views/layouts/knitter2.html.erb#L44](https://github.com/publiclab/mapknitter/blob/main/app/views/layouts/knitter2.html.erb#L44) in the https://github.com/publiclab/mapknitter repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff - To begin, <b>simply drag images onto the map</b> or click the <code><i class="fa fa-upload"></i> <b>Upload</b></code> button in the left sidebar. + To begin, <b>simply drag images onto the map</b> or click the <code><i class="fa fa-upload"></i> <b>Upload</b></code> button in the right sidebar.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file app/controllers/feeds_controller.rb in the mapknitter repository (press the little pen Icon) and edit the line as shown below.

To get help installing the application on your computer, see the project README and get help at #307

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

```diff @@ -12,8 +12,12 @@ def all end

def clean - @maps = Map.find(:all,:order => "id DESC",:limit => 20, :conditions => {:archived => false, :password => ''},:joins => :warpables, :group => "maps.id") - render :layout => false, :template => "feeds/clean" + @maps = Map.order(id: :desc) + .limit(20) + .where(archived: false, password: '') + .joins(:warpables) + .group("maps.id") + render layout: false, template: "feeds/clean" response.headers["Content-Type"] = "application/xml; charset=utf-8" end

```

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

Broken link: https://medium.com/@kentcdodds/first-timers-only-78281ea47455

Working link: https://kentcdodds.com/blog/first-timers-only

diff - [How to find your first Open Source bug to fix](https://medium.freecodecamp.org/finding-your-first-open-source-project-or-bug-to-work-on-1712f651e5ba#.slc8i2h1l) by [@Shubheksha](https://github.com/Shubheksha) - - [First Timers Only](https://medium.com/@kentcdodds/first-timers-only-78281ea47455) by [@kentcdodds](https://github.com/kentcdodds) + - [First Timers Only](https://kentcdodds.com/blog/first-timers-only) by [@kentcdodds](https://github.com/kentcdodds) - [Bring Kindness Back to Open Source](http://www.hanselman.com/blog/BringKindnessBackToOpenSource.aspx) by [@shanselman](https://github.com/shanselman)

All README files need to be fixed (I believe all of them have this broken link).

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file app/views/subscriptionmailer/senddigest.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff @@ -14,7 +14,7 @@ </div> <div style="float: left;"> <% if n.author.photo? %> - <img style="width:40px;margin-right:8px;border: 1px solid lightgrey;height: 40px;border-radius: 50%;" src="<%= n.author.photo_path(:thumb) %>"/> + <img style="width:40px;margin-right:8px;border: 1px solid lightgrey;height: 40px;border-radius: 50%;" src="https://<%= Rails.root %><%= n.author.photo_path(:thumb) %>"/> <% else %> <img style="width:40px;margin-right:8px;border: 1px solid lightgrey;height: 40px;border-radius: 50%;" src="https://www.gravatar.com/avatar/1aedb8d9dc4751e229a335e371db8058"/> <% end %> @@ -24,15 +24,15 @@ <p style="margin: 0;color: #999;font-weight: 500;">Published <%= n.created_at %>.strftime("%m/%d")</p> </div> <div <% unless n.main_image.present? %> colspan="2" <% end %> style="padding-bottom: 10px;"> - <p style="font-size: 1.1em;line-height: 1.5;text-align: justify;font-weight: 300;"><%= n.body.truncate(175) %><a href="https://publiclab.org<%= n.path %>" style="text-decoration: none;"> Read more</a></p> + <p style="font-size: 1.1em;line-height: 1.5;text-align: justify;font-weight: 300;"><%= n.body.truncate(175) %><a href="https://<%= Rails.root %><%= n.path %>" style="text-decoration: none;"> Read more</a></p> </div> <% if n.main_image.present? %> <div style="padding-bottom: 30px;"> - <img src="<%= n.main_image.path(:default) %>" style="width: 90px;height: 90px;border-radius: 5px;margin-left: 14px;"> + <img src="https://<%= Rails.root %><%= n.main_image.path(:default) %>" style="width: 90px;height: 90px;border-radius: 5px;margin-left: 14px;"> </div> <% elsif n.scraped_image %> <div style="padding-bottom: 30px;"> - <img src="<%= n.scraped_image %>" style="width: 90px;height: 90px;border-radius: 5px;margin-left: 14px;"> + <img src="https://<%= Rails.root %><%= n.scraped_image %>" style="width: 90px;height: 90px;border-radius: 5px;margin-left: 14px;"> </div> <% end %> <div colspan="2" style="padding-bottom: 32px;"> @@ -41,6 +41,6 @@ </tr> <% end %> </table> - <p>Click <a href="https://publiclab.org/subscriptions">here</a> to choose your followed topics</p> - <p>Click <a href="https://publiclab.org/settings">here</a> to change your subscription settings</p> -</div> \ No newline at end of file + <p>Click <a href="https://<%= Rails.root %>/subscriptions">here</a> to choose your followed topics</p> + <p>Click <a href="https://<%= Rails.root %>/settings">here</a> to change your subscription settings</p> +</div>

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

Problem:

I just extractes tids and nids to methods in the tag model https://github.com/publiclab/plots2/blob/master/app/models/tag.rb#L403-L409

📝 Update:

We want to remove wherever else they are defined in the model so that they can use the new methods.

Lets remove this line * https://github.com/publiclab/plots2/blob/master/app/models/tag.rb#L198-L199

After changing run the tests and make sure we didn't break anything - [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Content update:

Based on a conversation with a user who was chaining cy.wait(alias).then(...) I have noticed that our cy.wait page only shows cy.wait(alias).then((request object) => ...) examples, but says nothing how this is not necessary if you just want to wait for the network call to happen.

Commands following cy.wait wait for it to finish automatically, we need to add an example like the one in slide https://gitpitch.com/cypress-io/testing-workshop-cypress?p=slides/05-xhr#/0/7 and link to section of the docs explaining that commands run serially https://on.cypress.io/introduction-to-cypress#Commands-Run-Serially

js it('starts with zero items', () => { // start Cypress network server // spy on route `GET /todos` // THEN visit the page cy.server() cy.route('GET', '/todos').as('todos') cy.visit('/') cy.wait('@todos') // wait for `GET /todos` response // inspect the server's response .its('response.body') .should('have.length', 0) // then check the DOM // note that we don't have to use "cy.wait(...).then(...)" // because all Cypress commands are flattened into a single chain // automatically. Thus just write "cy.wait(); cy.get();" naturally cy.get('li.todo').should('have.length', 0) })

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update .

• The input form for enter tags is unaligned in the section


• Update will be done in plots2/app/views/home/subscriptions.html.erb

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file examples/demo.css in the community-toolbox repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

On line 37 of demo.css,

diff - @media (min-width:768px) { - .row.section img { - margin-left: 10%; - } - }

After removing these lines, save the changes. Then,

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

To Do: The footer of the demo site here has some redundancies and wrong links. It can be improved

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file index.html in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

This is the footer code https://github.com/publiclab/image-sequencer/blob/21ff4866182ce1023c28faed975cd7f09554545f/examples/index.html#L197-L219

see this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

Line 203 has a wrong link

diff - Post a link to this and ask help from other community members on <a href="https://github.com/publiclab/image-sequencer/issues/new">Github Issues</a> + Post a link to this and ask help from other community members on Gitter.

Line 212 has a redundant link diff - This is an open source toolkit which you can help add to and improve on <a href="https://github.com/publiclab/image-sequencer/">Github</a> + This is an open source toolkit which you can help add to and improve on Github. - [ ] 💾 Commit your changes - [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review ### Please keep us updated 💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: You can look here: https://github.com/publiclab/image-sequencer/blob/e5cf6a311f66280186293a6d103631560c07a06a/examples/selectize.default.css#L135 The issue is that the select module functionality added is not responsive enough. What you can do is explore different screen sizes and use media-query to set the margin-left, padding and width of the div which can be found in the above quoted part of css file. You can have a look here.


• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

Problem

Change this:


To this:


• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

I'm submitting a...

[ ] Bug report [x] Content update [ ] Process update (build, deployment, ... )

Type of bug / changes

Link to retry-ability doc from common commands like .get() and .contains()

As noted in this issue: https://github.com/cypress-io/cypress/issues/3745#issuecomment-474236658

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

Update In https://publiclab.org/profile/edit currently, if we want to edit our profile and add an image to it while choosing an image, the cursor must change to a pointer.

Make changes in app/views/users/_photo.html.erb file

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

Current behavior:

Currently, folders are omitted during keyboard navigation in the desktop GUI because onClick event for folders are attached to a non-interactive element (div).

Desired behavior:

It should be possible to interact with folders (collapsing/expanding) with a keyboard.

Steps to reproduce: (app code and test code)

See the gif below. Folders don't participate in keyboard navigation.


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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

To Do: There is an open pr #710 which adds a helper method called scopeQuery to image-sequencer demo code. You have to document it in the CONTRIBUTING.md file.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file CONTRIBUTING.md in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

Add a new part to the table-of-contents here https://github.com/publiclab/image-sequencer/blob/c6457323ccb19297553dedbac7f5caf39e00a078/CONTRIBUTING.md#L10-L14

Add a new section to the CONTRIBUTING.md file about UI helper methods after these lines https://github.com/publiclab/image-sequencer/blob/c6457323ccb19297553dedbac7f5caf39e00a078/CONTRIBUTING.md#L344-L348

Describe the helper method scopeQuery based on the information provided in the pr #710. This PR explains everything including the returned value and a description of the helper method, the available methods and an example about how to use it. You can put this in your own words. Make sure to include example code snippets. If you need help on how to do something, do not hesitate to ask.

see this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

On line 14 and 15 diff + * [UI Helper Methods](#ui-helper-methods) +

At the end, after line 348, add diff + ## UI Helper Methods + ### scopeQuery + ###### Path: `/examples/lib/scopeQuery.js` + [Add some description text here] + + #### Methods Of The Returned Object + * elemAll(): [description] + * elem(): [description] + * [Etc.] + #### Usage + [Give an example of usage here] + +js + [Add code snippet here] + Everything required to be documented is available in the pr #710. Please go through it to get the information and as in the comments below if you have any doubts.

• [ ] 💾 Commit your changes
• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review ### Please keep us updated 💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

To Do: Fix a typo in EdgeDetect module source code which doesn't affect functionality but is better to be fixed.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file Module.js in the image-sequencer repository (press the little pen Icon) and edit the line as shown below.

Change options.hystereis to options.hysteresis Here

https://github.com/publiclab/image-sequencer/blob/c6457323ccb19297553dedbac7f5caf39e00a078/src/modules/EdgeDetect/Module.js#L10

And here

https://github.com/publiclab/image-sequencer/blob/c6457323ccb19297553dedbac7f5caf39e00a078/src/modules/EdgeDetect/Module.js#L30 See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

On line 10 diff - options.hystereis = options.hysteresis || defaults.hysteresis; + options.hysteresis = options.hysteresis || defaults.hysteresis;

And on line 30 diff - pixels = require('./EdgeUtils')(pixels, options.highThresholdRatio, options.lowThresholdRatio, options.hystereis); + pixels = require('./EdgeUtils')(pixels, options.highThresholdRatio, options.lowThresholdRatio, options.hysteresis); - [ ] 💾 Commit your changes - [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review ### Please keep us updated 💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

I'm submitting a...

[x] Bug report 
[ ] Content update
[ ] Process update (build, deployment, ... )

Type of bug / changes

All of the paid plans list a maximum number of users. (https://www.cypress.io/pricing/) I am confused what a user is. I am hoping that the documentation and/or FAQ could be improved to clarify this.

Things a user might be:

• Anyone on your project who might want to run cypress open or cypress run
• Anyone who needs to log in to the dashboard service
• Anyone who needs to view the dashboard service (can this be done anonymously?)
• Anyone who might need to submit runs to the dashboard service (including CI?)
• None of the above? Something else?

I'm submitting a...

[ ] Bug report 
[x] Content update
[ ] Process update (build, deployment, ... )

User tries to set user-agent headers in cy.visit() since we extended it to allow headers, but we implemented settings userAgent within cypress.json for other reasons. https://github.com/cypress-io/cypress/issues/3719 We should put a note in the cy.visit() doc somewhere to explain this and link to the config doc. https://on.cypress.io/visit

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file $FILENAME in the $REPO repository (press the little pen Icon) and edit the line as shown below.

Update co-authored would look better than coauthor. 

Change need to be done: Change this line to <a href="#coauthored" class="btn btn-default" data-toggle="tab">Co-authored <%= "(#{ @coauthored.count })" %></a>

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

Is someone else already working on this?

🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.

👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

🤔❓ Questions?

Leave a comment below!

First Time?

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

The problem

As shown below, the pluralization rules we have in place are incorrect. We want 1 note and 0 research notes.

Solution

The pluralization should look like this:

This is a simple one -- let's change the following code:

1) In the below code, change the <= 1 to just be === 1. We don't want to include 0 in that conditional. This will change 0 research note to 0 research notes

https://github.com/publiclab/plots2/blob/d083415283dd89e0644e5bfe5ceb8e30b75dbecf/app/views/dashboard/_header.html.erb#L16

2) The below code is missing a condition all together:

https://github.com/publiclab/plots2/blob/d083415283dd89e0644e5bfe5ceb8e30b75dbecf/app/views/dashboard/_header.html.erb#L15

We want to change the first half of the line (the entire <a></a> element) to look like this:

```HTML <%= @notecount %> <% if @notecount === 1 %> <%= t('dashboard.header.note') %><% else %> <%= t('dashboard.header.notes') %><% end %>

`` this will update1 notesto instead say1 Note`.

3) Why is the Note capitalized? While in the first fix we were dealing with _header.research_note, in the second we have _header.note

Checking in the en.yml file, we find that: under, _header, there is a notes but no note:

https://github.com/publiclab/plots2/blob/d083415283dd89e0644e5bfe5ceb8e30b75dbecf/config/locales/en.yml#L312-L314

add a note: "note" key-value pair right below notes: "notes"

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/plots2
  • [ ] Create a new feature branch with a unique name descriptive to the issue
• [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
• [ ] Reference this issue in your pull request body
• [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

💬 Get help

If you need any help - here are some options:

• Comment below
• Join our gitter chat at https://gitter.im/publiclab/publiclab

First Time?

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

The problem

Our UI under our Dashboard Activity section needs a little improvement.

Solution

Let's make it look nice and consistent by adding spacing & capitalization, like this:

Where to find the relevant lines of code: 1) The spacing issue. Add a space after the | (pipe symbol) https://github.com/publiclab/plots2/blob/d083415283dd89e0644e5bfe5ceb8e30b75dbecf/app/views/dashboard/_activity.html.erb#L42

2) The capitalization issue. Capitalize the first word of the string. You do not need to change the key. https://github.com/publiclab/plots2/blob/d083415283dd89e0644e5bfe5ceb8e30b75dbecf/config/locales/en.yml#L287

Thanks!!

Bonus

I am not married to the way the text is laid out in general. If you have any additional changes you want to make, add them on to your PR and thank you!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/plots2
  • [ ] Create a new feature branch with a unique name descriptive to the issue
• [ ] Try to fix the issue following the steps above, but even before you're done, you can: commit your changes to your branch and start a pull request (see contributing to Public Lab software) but mark it as "in progress" if you have questions or if you haven't finished
• [ ] Reference this issue in your pull request body
• [ ] Once you submit your pull request, an additional checklist will be provided for getting it merged

Please keep us updated

💬⏰ - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!

If this happens to you, don't sweat it! Grab another open issue.

💬 Get help

If you need any help - here are some options:

• Comment below
• Join our gitter chat at https://gitter.im/publiclab/publiclab

since this is a localhost app, check if internet available when using editor. if not, send error (see main.py append to error list

Describe the bug I've discovered that the example netlink is not longer existing and the functionality is now in the device example

Expected behavior Documentation should be 1:1 with the actual code / examples

Describe the bug The toggle button for Advanced settings in the Settings pages is invisible. Clicking the element works normally, but there's no button that actually displays. Looks like there might be some bug with the js, css, or whatever controls the styling for that element.

To Reproduce

note: this happens on all pages with the Advanced toggle, but this describes just one page.

Steps to reproduce the behavior: 1. Go to /Settings/Radarr 2. Look for the Advanced label 3. Notice that there's no button next to the label 4. You can hover over where the element is, and the cursor changes to a "you can click this" cursor 5. Clicking shows/hides Advanced settings, but nothing displays on the page for the button.

Expected behavior element for the advanced toggle button should be visible.

Screenshots If applicable, add screenshots to help explain your problem. 

Logs (Logs directory where Ombi is located) not sure if this is related, but looking at the logs, it looks like ombi is trying to access stuff in some development path. example: ...at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57

log-20190313.txt: 2019-03-13 09:30:12.975 -04:00 [Error] Something bad happened, ErrorMiddleware caught this System.ArgumentNullException: Value cannot be null. Parameter name: entity at Microsoft.EntityFrameworkCore.Utilities.Check.NotNull[T](T value, String parameterName) at Microsoft.EntityFrameworkCore.DbContext.Remove[TEntity](TEntity entity) at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57 at Ombi.Core.Engine.MovieRequestEngine.RemoveMovieRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi.Core\Engine\MovieRequestEngine.cs:line 420 at Ombi.Controllers.RequestController.DeleteRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi\Controllers\RequestController.cs:line 122 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 51 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24 2019-03-13 09:30:20.309 -04:00 [Error] Something bad happened, ErrorMiddleware caught this System.ArgumentNullException: Value cannot be null. Parameter name: entity at Microsoft.EntityFrameworkCore.Utilities.Check.NotNull[T](T value, String parameterName) at Microsoft.EntityFrameworkCore.DbContext.Remove[TEntity](TEntity entity) at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57 at Ombi.Core.Engine.MovieRequestEngine.RemoveMovieRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi.Core\Engine\MovieRequestEngine.cs:line 420 at Ombi.Controllers.RequestController.DeleteRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi\Controllers\RequestController.cs:line 122 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 51 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24 2019-03-13 09:30:38.846 -04:00 [Error] Something bad happened, ErrorMiddleware caught this System.ArgumentNullException: Value cannot be null. Parameter name: entity at Microsoft.EntityFrameworkCore.Utilities.Check.NotNull[T](T value, String parameterName) at Microsoft.EntityFrameworkCore.DbContext.Remove[TEntity](TEntity entity) at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57 at Ombi.Core.Engine.MovieRequestEngine.RemoveMovieRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi.Core\Engine\MovieRequestEngine.cs:line 420 at Ombi.Controllers.RequestController.DeleteRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi\Controllers\RequestController.cs:line 122 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 51 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24 2019-03-13 09:30:53.965 -04:00 [Error] Something bad happened, ErrorMiddleware caught this System.ArgumentNullException: Value cannot be null. Parameter name: entity at Microsoft.EntityFrameworkCore.Utilities.Check.NotNull[T](T value, String parameterName) at Microsoft.EntityFrameworkCore.DbContext.Remove[TEntity](TEntity entity) at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57 at Ombi.Core.Engine.MovieRequestEngine.RemoveMovieRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi.Core\Engine\MovieRequestEngine.cs:line 420 at Ombi.Controllers.RequestController.DeleteRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi\Controllers\RequestController.cs:line 122 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 51 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24 2019-03-13 09:31:10.152 -04:00 [Error] Something bad happened, ErrorMiddleware caught this System.ArgumentNullException: Value cannot be null. Parameter name: entity at Microsoft.EntityFrameworkCore.Utilities.Check.NotNull[T](T value, String parameterName) at Microsoft.EntityFrameworkCore.DbContext.Remove[TEntity](TEntity entity) at Ombi.Store.Repository.BaseRepository`2.Delete(T request) in C:\projects\requestplex\src\Ombi.Store\Repository\BaseRepository.cs:line 57 at Ombi.Core.Engine.MovieRequestEngine.RemoveMovieRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi.Core\Engine\MovieRequestEngine.cs:line 420 at Ombi.Controllers.RequestController.DeleteRequest(Int32 requestId) in C:\projects\requestplex\src\Ombi\Controllers\RequestController.cs:line 122 at lambda_method(Closure , Object ) at Microsoft.AspNetCore.Mvc.Internal.ActionMethodExecutor.AwaitableResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeActionMethodAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeNextActionFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.InvokeInnerFilterAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeNextResourceFilter() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Rethrow(ResourceExecutedContext context) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted) at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeFilterPipelineAsync() at Microsoft.AspNetCore.Mvc.Internal.ResourceInvoker.InvokeAsync() at Microsoft.AspNetCore.Builder.RouterMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context) at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIIndexMiddleware.Invoke(HttpContext httpContext) at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext) at Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware.InvokeCore(HttpContext context) at Ombi.ApiKeyMiddlewear.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ApiKeyMiddlewear.cs:line 51 at Ombi.ErrorHandlingMiddleware.Invoke(HttpContext context) in C:\projects\requestplex\src\Ombi\ErrorHandlingMiddlewear.cs:line 24

Desktop (please complete the following information): - OS: Windows Server 2019 - Browser: Tested on Mozilla Firefox (65.0.2 64-bit) and Google Chrome (72.0.3626.119 64-bit)

Ombi Version (please complete the following information): - Version 3.0.4256 - Media Server Plex

Additional context Element information: (grabbed from Inspect Element) html <div style="float: right;"> <span style="vertical-align: top;">Advanced</span> <p-inputswitch id="customInputSwitch" class="ng-untouched ng-pristine ng-valid"> <div role="checkbox" class="ui-inputswitch ui-widget" aria-checked="false"> <div class="ui-helper-hidden-accessible"> <input type="checkbox"> </div> <span class="ui-inputswitch-slider"> ::before </span> </div> </p-inputswitch> </div> - ombi is running as a service through nssm. - I have ombi running behind a reverse proxy (base URL: /requests) using nginx. I still see this happen whether I access ombi externally through the reverse proxy (sub.domain.com/requests), locally through the reverse proxy (localhost/requests) or locally via the direct port (localhost:5000). all have the same behavior. - I have tried the basic stuff - clearing cache/cookies, restarting the service, etc. with no difference. - it also is not specific to one device - happens on the server itself and a few other computers I use (all Windows if that matters at all).

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
• [ ] 📝 Update edit thw stylesheets folder to add styles that address this issue. You can check out this article for help.

Current Behavior Visiting the following pages: https://publiclab.org/settings, https://publiclab.org/subscriptions (when you have little or no subscriptions), https://publiclab.org/subscriptions/digest (when you have little or no subscriptions), https://pubiclab.org/:user/likes (when you have little or no liked content) will show a footer that is pushed up and does not stick to the bottom of the page.

   

The above images are the only pages with little content I could find on production, but note that the behaviour will be replicated on any page with little content, as evidenced by this screenshot of a page on development:


Expected Behavior The footer should stick to the bottom of the screen, no matter the height of the content.

 

• [ ] 💾 Commit your changes
• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file app/views/users/profile.html.erb in the plots2 repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

```diff @@ -121,7 +121,12 @@

User tags

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update this line https://github.com/publiclab/plots2/blob/master/app/views/like/_like.html.erb#L3

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

```diff -<% if currentuser && (currentuser.uid == node.uid || currentuser.role == "moderator" || currentuser.role == "admin" || node.hastag("with:#{currentuser.username}")) %>

+<% if currentuser && (currentuser.uid == node.uid || currentuser.role == "admin" || node.hastag("with:#{current_user.username}")) %> ```

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update this line https://github.com/publiclab/plots2/blob/master/app/views/like/_like.html.erb#L5

See this page for some help in taking your first steps!

Below is a "diff" showing in red (and a -) which lines to remove, and in green (and a +) which lines to add:

diff - <a <% if current_user && current_user.uid != node.uid %>data-confirm='Please be aware that you are editing a post by another contributor, a privilege you have only because you are a moderator or admin or co-author.' <% end %> class='btn btn-default btn-sm' href='/notes/edit/<%= node.id %>?t=<%= Time.now.to_i %><% if params[:controller] == "questions" %>&redirect=question&template=question<% end %>'> +<a <% if current_user && current_user.uid != node.uid %>data-confirm='Please be aware that you are editing a post by another contributor, a privilege you have only because you are a admin or co-author.' <% end %> class='btn btn-default btn-sm' href='/notes/edit/<%= node.id %>?t=<%= Time.now.to_i %><% if params[:controller] == "questions" %>&redirect=question&template=question<% end %>'>

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

Refer #5027 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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update the file wiki.css in the plots2 repository to add css for the tooltip. Added css should set the maximun width of the tooltip. Code of this format can be followed -

.tooltip-inner { max-width: 500px }

See this page for some help in taking your first steps!

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update .

• The border and background of buttons in facebook and twitter buttons used is #4267b2 and #1b95e0 which is the main color of palette color followed by facebook and twitter. Let the background color remain same but Change the border hex to #29487d and ##00aced which is also a part of palette too but it shows a difference with background color.


• update will be done in app/views/home/_social.html.erb

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

beware just don't greet everyone who just sends messages. needs to detect joining event

like i-lov3@swimming4lif3 find replacement for normal english letters

Cypress 3.1.5

In our index.d.ts for types we should add better examples to cy.location and should('contain') to show how to check location url. Something like this for both places

js cy.get('.nav-tutorials').click() cy.location('href').should('contain', '/tag/tutorials/')

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update At https://publiclab.org/stats there are two simultaneous and present. There should be only one and.


Update:

Replace https://github.com/publiclab/plots2/blob/master/config/locales/en.yml#L256 with <b>%{notes_count} notes</b> and <b>%{wikis_count} wiki edits</b>

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

This issue can be taken by several devs.

Steps: 1. Get OpenEMR dev environment up and running with PHP 7.2 (PHP 7.3 would be extra credit). 2. Systematically go through as many of the OpenEMR scripts as can possible go through while monitoring the php error log. 3. Fix the PHP Warnings and PHP Deprecated warnings in the php error log.

Recommend just fixing a couple warnings (even fixing just 1 is ok) at a time.

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update .

• The tags goes out of alignment. It would be better if the whole Tags section will be aligned.  The marked portion is below 

• Update will be done in plots2/app/views/tag/_tagging.html.erb

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update .

• Increase the size of tag little bit in Featured Topics.


• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

https://github.com/ukBaz/python-bluezero/blob/2512460f1988e13fa4b5bc1497178872370c8230/bluezero/microbit.py#L458

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

Add the text "Pick a reaction" in reaction dropdown just like GitHub have :point_down: 

Our current reaction dropdown look :point_down: 

Feel free to optimize UI of dropdown further too.

• [ ] 📝 Update You need to update these lines for implementing the change - https://github.com/publiclab/plots2/blob/master/app/views/notes/_comment.html.erb#L96-L106

Also, attach the screenshot of the updated view by going over to any research note/question on localhost and taking a screenshot of the comment posted over there

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

The options on the comment are going out of the parent div as shown :point_down: 

• [ ] 📝 Update: https://github.com/publiclab/plots2/tree/master/app/views/notes/_comment.html.erb

so that options don't overflow out of parent comment

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update .

• Change the UI of Readmore button so that it can be differentiated from individual notes Readmore button.


• Update will be done in plots2/app/views/home/home.html.erb
• Go for a design similar as given image in ask a question button but smaller in size.


• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: On /profile/[username] in the sidebar, links display colored background on hover, let's remove the background color from the links


Update this line of code https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb#L284 so that on hovering over the links, no color is shown.

Also, try to shift the icon in the colored zone and upload the screenshot asking which view is looking better?

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: On /dashboard while viewing wiki changes/updates, you might have hovered over the changes link, the below one 

Update this line of code https://github.com/publiclab/plots2/blob/master/app/views/dashboard/_wiki.html.erb#L40 such that cursor changes to pointer on hovering over the link

After changing the view, also attach the screenshot of the updated view of the dashboard in the PR.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

Hi everyone!

We, at Public Lab, are known for welcoming new contributors into the Open Source world but a number of times, newcomers were not able to find first-timers-only issues to start their journey or face troubles making their first contribution with us.

Reasons being: 1. Lack of first-timers-only issues 2. Struggle in finding a good issue to start and lack of enough support?

We are working on both of the above aspects to support and help the maximum number of people to take their first step in their OSS journey with us, through our various projects but we need more support for this. So, this is a call to all the Public Lab members to try and create a first-timers-issue for someone who wants to start their journey and waiting for an FTO being assigned to them.

If you are interested in creating first-timers-only issue, follow these instructions: 1. Browse through the publiclab.org and see if there's a bug which can be easily solved.

1. Solve this issue but don't create a PR this time, instead create an FTO issue.

2. Click on this link to start creating a new issue.

3. We follow a specific template for FTO issues, so copy the template from here.

4. Edit the issue body to add the goal of the issue, code snippet required, file to be updated, add screenshots(if required). Don't add code snippet required to solve in case, the issue just requires minor HTML or CSS change or equivalent.

5. Add a catchy and relevant title to the issue but don't include "FTO", "first-timers-only" or equivalent in the title.

6. Get the issue you just created labeled by mentioning @publiclab/reviewers or @publiclab/is-reviewers.

• If you have labeling privileges, feel free to do so yourself but ensure that you have used FTO template.

• If you are not able to mention the above-mentioned teams and don't have labeling privileges, then drop a line in Gitter channel - https://gitter.im/publiclab/publiclab or mention @jywarren @tech4GT and any one of us will surely follow-up with you. You can also mention any other member, you can think of with labeling privileges.

note: all of the members of publiclab/is-reviewers team have labelling rights.

1. It's time to invite a new contributor to your issue. If there are unchecked names in the below list, then those people are still looking for FTO issue to start with, so mention them in your FTO by writing - This issue is created for @[contributor-name]. Thanks!

Also, if you see, a new contributor is looking for an issue, feel free to point them to your FTO.

fto-candidate Issues

These are issues which can become good first-timers-only issues but have to be reformatted using the fto issue template. If you feel like reformatting any of these, please feel free to do so. Please let us know if you are going to reformat the issue in the issue comments and link to the new issue in the comments of the original issue and this issue. You can mention @publiclab/is-reviewers to get the new issue labeled and then the old issue closed.

note: please do not reformat fto-candidate issues which have a has-pull-request as well.

note: if somebody is working on one of these issues, please notify the contributor about the reformatted issue.

Contributors looking for first-timers-only (FTO) issues

• [x] @mgroovyank (#874)
• [x] @An0u (#894)
• [x] @Jaya738 (#884)
• [x] @hodbadger (#885)
• [x] @vaarigupta (#898)
• [ ] @teisenhower
• [ ] @ElenaG518
• [ ] @edwd42
• [ ] @rmcorre

To first-time contributors: If you are looking for FTO and want your name to be added to the above list then, feel free to comment below to show your interest. If you are looking for working on specific language/framework, mention that too in your comment.

To Public Lab members who have comment edit privileges: Please add names of newcomers who have shown into for FTO in below comments. Also, add the names of other newcomers who are looking for FTO and shown their interest by commenting on other issues.

Currently open first-timers-only and fto-candidate issues in image-sequencer repo.

See also #879

For any query, feel free to ask below or at Public Lab gitter channel - https://gitter.im/publiclab/publiclab

Thank you!

cc @jywarren @publiclab/reviewers @publiclab/is-reviewers @tech4GT

Original issue template by @gauravano

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: At https://publiclab.org/blog the Read more link with the subscribe button doesn't look good 

so let's change the link to a button matching the subscribe button style

Update https://github.com/publiclab/plots2/blob/master/app/views/tag/blog.html.erb#L63 to do so

After changing the view, also attach the screenshot of updated view in the PR.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: At https://publiclab.org/notes the Spam and Read more buttons are rendering on the different lines as visible in the screen shot 

Update https://github.com/publiclab/plots2/blob/master/app/views/notes/_notes.html.erb#L49-L52 so as to show both buttons in a single line enhancing the page design

After changing the view, also attach the screenshot of updated view in the PR.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

from idea to finish

Cypress 3.1.5 on Mac

js /// <reference types="cypress" /> it('works', () => { Cypress.log('after hook') })

Throws error

Code that throws

js _.defaults(obj, current != null ? current.pick("name", "type") : void 0); if (!parentOrChildRe.test(obj.type)) { obj.type = current.hasPreviouslyLinkedCommand() ? "child" : "parent"; }

https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/cypress/log.coffee#L117

requires some thinking. top tip: see if you can find such functionality in other bots!

not difficult but some works needed

a plugin to write all messages to a text file

no need to draw the man but update user of right or wrong guess and chances remaining

either on wiki or a separate markdown document. add code running instructions on ide with screenshots

describe what the project is about etc

The following script is creating a json file with all the lessons in the platform: https://github.com/breatheco-de/content/blob/master/generate-json.js

This is a sample of the json file being generated: https://content.breatheco.de/static/api/lessons.json json [ { "slug": "[draft]mentoring-guidelines", "status": "draft", "title": "Mentor Guidelines", "date": "2017-09-24", "tags": [ "fale" ] }, ... ]

We need to update that script to also include on the lesson object if the lesson is missing translation to Spanish or not.

Every lesson is supposed to have a spanish version with the same file name but ending on .es.md instead of just .md

For example, the lesson learn-html.md should have a learn-html.es.md alternative.

Current behavior:

When using the Cypress Dashboard with Google Cloud Build, all of the Git information is coming back undefined/null. From looking in the code, and asking on Gitter, it seems that is not currently supported.

Desired behavior:

I would like the Cypress Dashboard to pull that information from Google Cloud Build and display it. https://cloud.google.com/cloud-build/docs/configuring-builds/substitute-variable-values

Versions

Cypress 3.1.5

Due to some API changes, there was a need to update some example notebooks (see #264). These changes now need to be synced with the online documentation.

Status of notebooks: - [x] basicoptimization.ipynb - [x] customoptimizationloop.ipynb - [x] electriccircuitproblem.ipynb (new) - [ ] featuresubsetselection.ipynb (assigned to @gustavovelascoh ) - [ ] inversekinematics.ipynb - [ ] optimizationloop.ipynb - [ ] trainneural_network.ipynb - [ ] visualization.ipynb

Status of documentation: - [x] basicoptimization.rst - [ ] customobjectivefunction.rst - [x] customoptimizationloop.rst - [ ] electriccircuitproblem.rst (to be added?) - [ ] featuresubsetselection.rst - [ ] inversekinematics.rst - [ ] visualization.rst

Current behavior:

When supportFile is pointing to a symlinked path we get the error "Your supportFile is set to /whatever/support/index.js/index.js" Where the "index.js" is repeated

Desired behavior:

supportFile should support symlinked paths

Steps to reproduce: (app code and test code)

• Create the structure "foo/support/index.js"
• Create the a symlink "bar" linking to "foo"
• Set cypress supportFile configuration to "bar/support/index.js"
• Observe the error

Versions

Cypress 3.1.5 Node 11.6.0 Linux Ubuntu 18.04

Additional info

The cause of the problem is https://github.com/cypress-io/cypress/blob/ce3ab55f72527374cfa2a1b942dffedb5d1a232f/packages/server/lib/config.coffee#L367

It assume sf is a path and does not contain the filename.

But that is incorrect. sf is resolved to the full path, including index.js.

The line should probably become obj.supportFile = path.join(path.dirname(sf), path.basename(obj.supportFile))

I see this problem pretty often: user is trying to npm run cy:run --record ... without separating arguments with -- (should be npm run cy:run -- --record ...)

• https://github.com/cypress-io/cypress/issues/3467

We need to put this warning in several places, because people not familiar with NPM's quirks will get stuck and frustrated. I see a couple of places where this warning could be added

• https://docs.cypress.io/guides/getting-started/installing-cypress.html#Adding-npm-scripts
• https://docs.cypress.io/guides/getting-started/installing-cypress.html#Run-binary
• https://docs.cypress.io/guides/guides/continuous-integration.html#To-record-tests
• https://docs.cypress.io/guides/references/configuration.html#Command-Line

In the existing https://docs.cypress.io/guides/guides/command-line.html#How-to-run-commands warning, we need to stress this point by adding "important"

It would be nice to create reusable warning template that we can include on demand, just like @flotwig has done with network stubbing warning in this commit https://github.com/cypress-io/cypress-documentation/commit/50c4c7112c0faff34e564686655a70ee155a34e5

I have existing NPM run warning here: https://github.com/cypress-io/cypress-documentation/blob/develop/source/guides/guides/command-line.md#how-to-run-commands

Maybe we could have a shorter version of the above warning that can be inserted into more places

OpenEMR uses PHPMailer to send email currently. Find where we instantiate a PHPMailer() or MyMailer() object and make sure it sends email securely. Just search for "mailer" in this repo and you should find those instances. There are maybe 30.

Also here is the MyMailer() class, which extends the PHPMailer() class. Make sure the config is properly secured. Maybe we should be adding other options? Validation checks? https://github.com/openemr/openemr/blob/fa9f0bfcfda78561077861a6481fa3f4bfe1186d/library/classes/postmaster.php

Both first-timers and OpenEMR pros welcome :)

Most IDEs have a way to check for functions that are declared but never actually called / used. Download something like PHPStorm, which has a 30 day free trial, and figure out how to use this function.

Then delete all the functions you find and submit a pull request. We'll review them, maybe there will be a couple we actually need and need to save, and then you'll be done.

https://github.com/psecio/parse

Use the above tool. Let us know the results.

Check out line 284 or right around there of this file where the GRANT and INSERT USER statements are called: https://github.com/openemr/openemr/blob/master/library/classes/Installer.class.php

This file is called by setup.php during installation. It creates the initial OpenEMR database user.

Surely this user can be restricted? Do they really need all these privileges? https://dev.mysql.com/doc/refman/8.0/en/privileges-provided.html

Throughout the app we've been combining styles like this client/src/components/background/background.js <div className={[classes.waveWrapper, classes.waveAnimation].join(" ")} style={{ bottom: bottomSpace }} > This is not the proper way to combine classes with css modules. It makes the code bloated and hard to read. Instead of doing this in the JSX we should use the "compose" functionality. For example... client/src/components/background/background.css ```css .waveWrapper { overflow: hidden; position: absolute; left: 0; right: 0; bottom: 40%; top: 0; margin: auto; }

.waveAnimation { composes: waveWrapper /** ...styles specific to waveAnimation**/ } and now our component looks like this `client/src/components/background/background.js` <div className={classes.waveAnimation} style={{ bottom: bottomSpace }}

`` There are some instance where we will need to leave the .join() methods. Any time we are combining font-awesome classes... e.g.` we need to leave them like this so css modules does not dynamically rename the font-awesome classNames.

A workspace looks like this


When you click the arrow on the instructions window it hides the instructions. The desired behavior is for the instructions pane to collapse and for the graph to grow to fill up the remaining space.

Because we're using flexbox I think the best way to accomplish this would be to use flex-grow for the graph so that it fills remaining space and then just change the height of the instructions panel onClick.

The relevant directory is ./client/src/layout/workspace lines 54 - 78 and the corresponding css file.

This element is the instructions panel line 78 <div className={classes.Bottom}>{bottomLeft}</div> And this element is the graph line 54 <div className={[classes.Top, "graph"].join(" ")}>

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

Problem

Multiple types of file can be uploaded in the upload image section.

📋Solution

Change this line:

https://github.com/publiclab/mapknitter/blob/de156283193542b10607542db5544ae400cf48bc/app/views/images/_new.html.erb#L19

To:

<i class="fa fa-plus-circle"></i> Select images <input id="warpable_uploaded_data" name="warpable[uploaded_data]" type="file" accept="image/*" />

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

Value: Auto deployment script, domain settings

Possible solution: Write deploy script https://github.com/vwochnik/jekyll-deploy https://www.digitalocean.com/community/tutorials/how-to-deploy-jekyll-blogs-with-git#add-a-git-remote https://www.digitalocean.com/community/tutorials/how-to-use-git-hooks-to-automate-development-and-deployment-tasks

It would be nice to be able to load and send a fixture file by name like

js it('finds issues mentioned', function () { cy.request('/api', 'fx:pr-opened') })

Currently, have to load fixture and then send

js it('finds issues mentioned', function () { cy.fixture('pr-opened') .then(data => cy.request('/api', data)) })

Cypress 3.1.5

• npx cypress open

• click on "Settings" First problem - since there is "Configuration" only - why is it collapsed by default?

• click "Configuration" There is a blue outline which cuts into the help link and just looks weird.

Current behavior:

The documentation says it is technically possible for cy.writeFile to timeout but it shouldn't, however, it did for me today. I know it was the cy.writeFile that timedout because it is the only cy.Command in my aftereach hook.

The Error Output:

``` 20) EditAndBranching "after each" hook for "Tag And Frog": Error: Cypress command timeout of '4000ms' exceeded.

Because this error occurred during a 'after each' hook we are skipping all of the remaining tests. at http://localhost:5050/_cypress/runner/cypressrunner.js:66264:25 ```

Desired behavior:

I think Cypress should provide a way to override the timeout or fix it so it can't timeout.

I also think Cypress should not stop running the remaining tests when one fails in the aftereach hook. That is a harsh punishment for an intermittent failure. In fact that also is a good case for not failing all tests in the aftereach since one failure does not necessarily mean they all will fail. Perhaps this needs a rethink as well.

Steps to reproduce: (app code and test code)

"Issues without reproducible steps will get closed." -- How am I supposed to give you code to reproduce this? Do I have to write some OS hook to intercept the writeFile command and make it take longer than 4 seconds?

Sorry but I don't have the time to work up some sort of repro steps...this requirement on obvious flaws is an impedance to filing a bug. I've reported the bug, if you all want to just close and do nothing then so be it.

Versions

Cypress package version: 3.0.3 Cypress binary version: 3.0.3 OS Name: Microsoft Windows 10 Enterprise OS Version: 10.0.17763 Build 17763 Browser: Electron 59 (headless)

This is a "Content Box" 

You can toggle the information it displays by clicking the arrow on the right 

Notice when this clicked the title text "jumps" a bit causing a jarring user experience. It's actually hard to see in this GIF because the frame rate is low and it happens fast. You can kind of make it out on the first click but it is definitely noticeable to a real user.

The relevant code to fix this is in ./client/src/Components/UI/ContentBox It is probably a CSS issue related to flex-box.

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: You need to add a accept="image/*"attribute to the code segment below so that the main image upload imports nothing other than an image from the user. https://github.com/publiclab/PublicLab.Editor/blob/94a549c6e6fcbc0d5ef8e6e3ebbf6322b46e748a/examples/index.html#L108

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

Cypress 3.1.5

Currently, we only check if the server defined in baseUrl is responding when we start Cypress. If the user starts their server AFTER Cypress the message is very confusing and scary - and wrong

It would be nicer to (a few alternatives)

• retry the server periodically and remove the error message when the server responds
• have a Retry button to test again. If the server responds, remove the message
• at least add to the message text like "If you have started the server after Cypress, ignore this error"

Readme.md files across the repo are not updated. A check is necessary.

English level is of variable quality across the repo. Any help under the linguistic aspect is warmly welcome.

Check, revise and complete diagrams regarding software.

To avoid duplicate content, before starting please contact us.

During the brainstorming phase, we often need to play around with 3D models and render. Blender is welcome. The idea is to provide some graphical follow up. The final models will be published during the release phase.

Run a systematic test: ISAALTITUDE function in AirDC Library It is necessary to develop a test function that can test the correctness of the ISAALTITUDE implementation. The test function will compare the ISAALTITUDE output with the expected output for a set of input data. If the differences are within 1/1000, then ISAALTITUDE function passes the test.

Run a systematic test: RhoAir function AirDC Library It is necessary to develop a test function that can test the correctness of the RhoAir implementation. The test function will compare the RhoAir output with the expected output for a set of input data. If the differences are within 1/1000, then RhoAir function passes the test.

To have a test function is helpful!

We wish to improve the documentation. Any help is welcome!

After releasing v0.4.0, it seems that we already had some API changes that were not reflected in the notebook. What you need to do is just rerun all the notebooks in this link and update the code as necessary to account for API changes :+1:

docs for https://github.com/cypress-io/cypress/pull/3219

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: Add a CODE_OF_CONDUCT.md to this repository by referencing the document found here and submitting the same in your PR.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: Add a CODE_OF_CONDUCT.md to this repository by referencing the document found here and submitting the same in your PR.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: In this fto, you will need to design a mainfest.json for a mobile-rich experience of the PL.Editor. Take some time to understand the theme and design of the Editor, and design a mainfest.json file that you think will suit best to the Editor.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Create the file named [Dangerfile.md] in the mapknitter repository (press the little pen Icon) and edit the line as shown below.

See this page for some help in taking your first steps!

The file needs to be created at the root of the repository and copy the dangerfile from https://github.com/publiclab/plots2/blob/master/Dangerfile.md

into newly created file.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: All we need to do here is add the following line in the <head>, <meta name="theme-color" content="#000">. This would help the mobile chrome viewscreens to adapt to a better contrast theme for the Editor, hence improving readability and user engagement.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

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!

We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

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

🤔 What you will need to know.

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.

📋 Step by Step

• [ ] 🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

• [ ] 📝 Update: this will fix #241. All that needs to be done is replace this line

https://github.com/publiclab/PublicLab.Editor/blob/94a549c6e6fcbc0d5ef8e6e3ebbf6322b46e748a/examples/index.html#L134

With this line <p class="ple-map-content"><b>By place name:</b></p>. This line https://github.com/publiclab/PublicLab.Editor/blob/94a549c6e6fcbc0d5ef8e6e3ebbf6322b46e748a/examples/index.html#L139 With this line <p class="ple-map-content"><b>By entering co-ordinates:</b></p>.

And finally, paste the following line (with the same indentation/format of the rest of the code)

.ple-map-content { font-size: 16px; }

on the file named PublicLab.Editor/dist/PublicLab.Editor.css, just after line number 36.

• [ ] 💾 Commit your changes

• [ ] 🔀 Start a Pull Request. There are two ways how you can start a pull request:

1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

2. You can also edit files directly in your browser and open a pull request from there.

• [ ] 🏁 Done Ask in comments for a review :)

🤔❓ Questions?

Leave a comment below!

Is someone else already working on this?

We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!

(This issue was created by First-Timers-Bot.)

Related to this issue: https://github.com/openemr/openemr/issues/2145

Clean up XSS prevention in scripts in library/customtemplate/ directory: https://github.com/openemr/openemr/tree/master/library/customtemplate (part of this issue: https://github.com/openemr/openemr/issues/2145)

Task

If the cloneobject function is not NULL and the cloneobject returns NULL for any reason it should terminate, free all the memory allocated so far for the clone and return NULL

Method

When invoking the clone_object, check if the return value is NULL. If it is, then simply terminate and return NULL. You will have to check if the return value from the recursive call is NULL because of an error or because the leafs of the trees have been reached.

Prototype

/** * cranbtree_t*, void* (*)(void*) -> cranbtree_t* * EFFECTS: clones the given cranbtree_t and clones the user objects if the * the passed function pointer is not NULL * RETURNS: a pointer to the clone, or NULL if the given cbt is not valid or on failure * NOTE: if the function is NULL, clone will copy the original object pointers to the new * clone . This you must be careful in this case when manipulating the objects and destroying * them. Otherwise, the tree will store copies of the objects */ cranbtree_t *cbt_clone(cranbtree_t * cbt)

Where to code

You will need to modify the following functions - cbtclone in src/cranbtree.c - cbtcopy_nodes in src/lib/clone.c

Tests

1. write a new test that passes a helper that fails when being called to copy an object and make sure the return value of cbt_clone is NULL. Run valgrind to make sure there are no memory leaks

Perfectly hardened example script: https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php

Hardens text - text(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L680

Hardens code in html tags / attributes - attr(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L824

Hardens code in text that also is language / location specific - xlt(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L758

Hardens code in html tags / attributes that also is language / location specific - xla(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L581

Unknown - jsescape(): https://github.com/openemr/openemr/blob/master/interface/reports/patledger.php#L945

Unknown - xlj(): https://github.com/openemr/openemr/blob/master/interface/reports/pat_ledger.php#L383

Here's the documentation that covers this: https://www.open-emr.org/wiki/index.php/CodebaseSecurity#Cross-ScriptingPrevention

Here's the library with these functions: https://github.com/openemr/openemr/blob/master/library/htmlspecialchars.inc.php

Memory allocation in Assignments 1 and 2A in CS2233 Data Structures is syntactically wrong. The *s inside malloc must be removed.

Also, the submitted version must be checked with the inputs mentioned in the pdf file and Valgrind(memory leak checker for c/c++).

Is this a Feature or Bug?

I believe this to be a bug with Cypress dashboard where truncation of the output makes debugging issues via the dashboard or CI very difficult for developers. It is useful for instance to see body and url parameters when using something like cy.request however the output on failure is formatted in a way which inhibits the ability to debug issues.

Current behavior:

the output in the cypress dashboard for a 404 (any sufficiently large output will do) looks like

``` 1) toolbar layer style "before all" hook for "should edit style name": CypressError: cy.request() failed on:

http://xyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxy/api/customer?token=uy9aG2yVRlyPAcWxvTZEXlTvRm6O4u

The response we received from your web server was:

404: Not Found

This was considered a failure because the status code was not '2xx' or '3xx'.

If you do not want status codes to cause failures pass the option: 'failOnStatusCode: false'

The request we sent was:

Method: POST URL: http://xyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxyxy/api/customer?token=uy9aG2yVRlyPAcW_xvTZEXlTvRm6... Headers: { "user-agent": "E2E", "accept": "/", "accept-encoding": "gzip, deflate", "content-type": "application/json", "content-length": 74 } Body: {"clusterId":"Dev-Alpha-Cluster","name":"Fin Fang Foom e2e20190116163428","OtherStuff":"ThisIsSomeDa... ```

see that the body and url are being truncated in this final block of the log. For small payloads it's fine, but when payloads become larger (or other cy methods that produce longer lines) the truncation makes the output almost useless. This is more of a problem when the errors are only produced on the CI server.

Desired behavior:

I would like some control over the output here, several options:

• Download the raw output (unmodified)
• Wrap long lines preserving the entire line
• Have an option to open raw in the browser

Steps to reproduce: (app code and test code)

Simply perform a cy.request with a sufficiently large url or body e.g.

JavaScript cy.request({ method: 'POST', url: 'http://myreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallylong.url', })

Versions

Cypress: 3.1.3

I don't believe the browser to be an issue in this specific issue.