[![Github Repo Size](https://img.shields.io/github/repo-size/arshadkazmi42/ak-phrase.js.svg)](https://github.com/arshadkazmi42/ak-phrase.js)

Add the above line in readme with other badges

I was planning on working on #803, but I got distracted and @yehia67 beat me to it.

However, unless I'm mistaken, the portion of code addressed by #803 doesn't seem to be correct. An exception is being thrown if the class being checked IS a subclass of PdhCounterProperty, which seems to be the opposite of the intent.

Also, the class passed to isAssignableFrom is the class containing the "property enum" (which, as you noted, is null if the enum is a top-level class) instead of the enum's class itself. Instead, I believe it should be the following:

if (!PdhCounterProperty.class.isAssignableFrom(propertyEnum)) {

This causes another problem as the PerfCounterWildcardQuery constructor also invokes the PdhCounterProperty constructor. The end result is that a property enum passed to PerfCounterWildcardQuery would be required to implement both PdhCounterProperty and PdhCounterWildcardProperty.

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.

I'm submitting a...

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

We have a lot more content in the testing workshop https://github.com/cypress-io/testing-workshop-cypress#content- so we should update the documentation page

I'm submitting a...

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

Type of bug / changes

Our debugging page http://on.cypress.io/debugging is very good. Recently I wrote a section on debugging for testing workshop https://github.com/cypress-io/testing-workshop-cypress/blob/master/slides/15-debugging/PITCHME.md with a few clarifications, which we can bring back into this page

• debugging with DEBUG= per package
• how to disable DEBUG messages in the browser
• isolating the problem by splitting
• debugging thrown error
• using cypress-failed-log plugin

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.

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: Remove newline between the FB and Twitter buttons 

Let's shift them on the same line by updating file. Also, there's a typo in the comment (at line 42) in the file, please remove that too. https://github.com/publiclab/plots2/blob/master/app/views/sidebar/_dashboard.html.erb#L42-L47

Also, attach the screenshot of the updated view.

• [ ] 💾 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 moderate buttons Approve and Spam appear on comments and notes listing on the dashboard only visible to the moderators and admin.


These butttons appear on same line as Moderate first time comment for comment but for note, the buttons are shown in next line. Let's shift them on the same line by updating file https://github.com/publiclab/plots2/blob/master/app/views/dashboard/nodemoderate.html.erb

Also, attach the screenshot of the updated view by creating a post as a user and then login as a moderator on localhost for clicking the screenshot.

• [ ] 💾 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 the sidebar, alert notifying the user that note is marked as activity looks like this: 

The correct text should be This is marked as an activity for others to try.

Update this line - https://github.com/publiclab/plots2/blob/e3cf2112469c8be284e541579d2bc02b62d39e7a/app/views/tag/_replication.html.erb#L4

and add the screenshot of the 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!

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.

The video and slides from https://twitter.com/nikolalsvk/status/1095409664005689344

There's so much API change that even the documentation in the README will not work right away. Any help here would really be appreciated. The goal is to just try out the code samples in the docs, and correct them into our new version.

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!

Clicking on a locked unit should only show the cards of a unit but not try to load the cardboard, because most likely that unit is not yet playable. I've removed all the cardboard placeholders for units that aren't due for v0.4 in patch 9dd4748

Value: SSL for web and improving SEO/

Possible solution: yaml url: https://username.github.io enforce_ssl: username.github.io https://blog.webjeda.com/jekyll-ssl/

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 a beneficial enhancement to have setup check required write permissions on the documents directory and it's sub-directories, as write permissions are required for saving patient documents, and encryption routines. It would also be beneficial to develop an administrative "System Health" page that would display a table of your php and openemr settings that could potentially diagnose permissions errors, or dependency errors.

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!

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 that needs to be done is replace this line https://github.com/publiclab/image-sequencer/blob/fa047ce6a9c9993ffd6ae2aeb65ed2589c81ad6a/examples/index.html#L66

With this line <button type="button" id="take-photo" class="btn btn-default btn-md">Take a Photo</button>

• [ ] 💾 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.)

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

These are "crumbs" 

They let the user know where they are. Right now, if you click MyVMT it redirects to /myVMT/courses. The desired behavior is for it to redirect to /myVMT/rooms when you're on a room page, /myVMT/activities when you're on an activity page and /myVMT/courses when you're on a course page.

The place to change these redirects would be in the render methods of Containers/Room, Containers/Activity (Containers/Course already has the desired behavior.

If you're feeling ambitious you could also add some tests to /cypress/integration/navigation.js to confirm the changes you've made work.

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: 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.)

First timers only

This issue is reserved for people who have never contributed to the GOV.UK Design System before, please only pick this up if you're a new contributor.

Description

After updating sass-exports (npm install sass-exports@1.0.3), when you try run npm test or npm start the following error appears:

TypeError: Cannot read property 'reduce' of undefined

paletteMap is returning undefined and therefore on this line reduce method fails.

If you remove .mapValue (https://github.com/alphagov/govuk-design-system/blob/master/lib/colours.js#L25), paletteMap returns a value but not in the correct format.

Step by Step

1. Claim this issue

Comment below to let other people know that you're working on this issue.

2. Fork the repository

3. Edit colours.js file

palette should set to

json { "black":"#0b0c0c", "blue":"#005ea5", "bright-purple":"#912b88", "bright-red":"#df3034", "brown":"#b58840", "green":"#006435", "grey-1":"#6f777b", "grey-2":"#bfc1c3", "grey-3":"#dee0e2", "grey-4":"#f8f8f8", "light-blue":"#2b8cc4", "light-green":"#85994b", "light-pink":"#f499be", "light-purple":"#6f72af", "orange":"#f47738", "pink":"#d53880", "purple":"#2e358b", "red":"#b10e1e", "turquoise":"#28a197", "white":"#ffffff", "yellow":"#ffbf47" }

4. Create a Pull Request

5. Done

We'll review the Pull Request and let you know if any changes are needed.

Questions

If you’ve got a question, you can comment in this issue or email the Design System team on govuk-design-system-support@digital.cabinet-office.gov.uk

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.)

Add to https://github.com/cypress-io/cypress-documentation/blob/develop/source/api/commands/type.md#L44

Dependent on PR being released: https://github.com/cypress-io/cypress/pull/3071

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

We should allow for a @Bean of type ReactiveOAuth2AccessTokenResponseClient<OAuth2AuthorizationCodeGrantRequest> to be discovered by OAuth2LoginSpec.

This will allow the user to register a WebClientReactiveAuthorizationCodeTokenResponseClient @Bean with a configured WebClient via WebClientReactiveAuthorizationCodeTokenResponseClient.setWebClient().

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)

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: Remove the following snippet that currently generates an unnecessary log.


https://github.com/publiclab/leaflet-blurred-location/blob/369274989869515579d567e1c3376d9db2321dfe/src/core/Geocoding.js#L60 - [ ] 💾 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: There are many instances of code containing "&" to implement the "&" character in the website, but instead it renders the "&" string itself.


In order to resolve this, we can replace the following "&" instances by "and".

```` ./app/views/editor/_editor.html.erb: 17: Drag & drop to add an image or file, or

./app/views/editor/mainimage.html.erb: 17: Drag & drop to add an image, or

./config/locales/views/comments/edit/en.yml: 7: dragand_drop: "Drag & drop to add an image or file, or"

./config/locales/views/comments/form/en.yml: 7: dragand_drop: "Drag & drop to add an image or file, or"

./config/locales/views/users/photo/en.yml: 7: draganddropimage: "Drag & drop to add an image, or" ````

• [ ] 💾 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!

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++).

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 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.

Once claimed we add you as contributor to this repository.

• [ ] 👌 Accept our invitation to this repository. Once accepted, assign yourself to this issue

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

diff @@ -0,0 +1,4 @@ +### First Timers Test +* [ ] Test this probot out +* [ ] Make observations +* [ ] Take notes

• [ ] 💾 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 edit files directly in your browser

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

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

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.

OidcIdTokenValidator.setClockSkew() should assert that the clockSkew is >= 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: This will resolve #228. All that needs to be done is remove the following line, https://github.com/publiclab/PublicLab.Editor/blob/ffcb496c6be2abf813c7e38f8ef3d72a8426251d/src/modules/PublicLab.RichTextModule.js#L251

• [ ] 💾 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!

Hello!

Would be super useful to have cypress available here https://eslint.org/docs/user-guide/configuring#specifying-environments, so that we do not have to configure globals manually or use something like https://github.com/standard/eslint-config-standard which adds extra complexity.

Expected If I add in package.json: json { "standard": { "env": ["cypress"] } } I should not be getting /cypress/integration/examples/location.spec.js:3:1: 'context' is not defined. and similar.

Cheers!

Task

set the op_errorno appropriately when a NULL function pointer is provided or if the number of visited entries does not match the number of entries in the tree. The error codes can be found in include/cranbtree.h

Method

check for errors before and after the tree traversal

Where to code

• src/cranbtree.c

Tests

1. cbtvisitall_test1
2. cbtvisitall_test2 Make sure to uncomment this tests in test/test.c, compile, the run and make sure all the tests passes and nothing is broken

Moved this issue from the Docker repo to here. Much better to do this at the app level if it is going to be done.

Maybe add this at some point, would be really cool but low priority.

Here is code I have that gets the MaxMindDB GeoIP2 database. Can be executed daily via cron to update or can just make a function in PHP instead of bash to do it. You read the MMDB file by using MaxMind's PHP GeoIP2 library.

wget https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.tar.gz \ && tar -xvf GeoLite2-Country* && mkdir /usr/local/share/GeoIP \ && mv GeoLite2-Country*/GeoLite2-Country.mmdb /usr/local/share/GeoIP

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

You can see our Brazilian Portuguese version

About First Timers Only.

🤔 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.

Once claimed we add you as contributor to this repository.

• [ ] 👌 Accept our invitation to this repository. Once accepted, assign yourself to this issue

• [ ] 📝 Update the file README.md in the gitpay repository (press the little pen Icon) and edit the line as shown below.

`````diff @@ -89,5 +89,8 @@ Then you can access at http://localhost:8082 ##### Test environment - Rundocker-compose -f docker-compose.test.yml up`

+### First timers +Here you can start to learn how to create your first pull request and start to be a contributor: +https://github.com/worknenjoy/gitpay/issues/247 +Your name

``````

• [ ] 💾 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 edit files directly in your browser

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

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

A big way to improve the security of iframes is by using the sandbox policy. Example:

https://html.spec.whatwg.org/multipage/origin.html#sandboxed-modals-flag https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe

<iframe sandbox="allow-forms allow-top-navigation allow-scripts">

sandbox Applies extra restrictions to the content in the frame. The value of the attribute can either be empty to apply all restrictions, or space-separated tokens to lift particular restrictions: allow-forms: Allows the resource to submit forms. If this keyword is not used, form submission is blocked. allow-modals: Lets the resource open modal windows. allow-orientation-lock: Lets the resource lock the screen orientation. allow-pointer-lock: Lets the resource use the Pointer Lock API. allow-popups: Allows popups (such as window.open(), target="_blank", or showModalDialog()). If this keyword is not used, the popup will silently fail to open. allow-popups-to-escape-sandbox: Lets the sandboxed document open new windows without those windows inheriting the sandboxing. For example, this can safely sandbox an advertisement without forcing the same restrictions upon the page the ad links to. allow-presentation: Lets the resource start a presentation session. allow-same-origin: If this token is not used, the resource is treated as being from a special origin that always fails the same-origin policy. allow-scripts: Lets the resource run scripts (but not create popup windows). allow-storage-access-by-user-activation : Lets the resource request access to the parent's storage capabilities with the Storage Access API. allow-top-navigation: Lets the resource navigate the top-level browsing context (the one named _top). allow-top-navigation-by-user-activation: Lets the resource navigate the top-level browsing context, but only if initiated by a user gesture.

@bradymiller Going to keep this issue open/recurring to ask about non-used old code and if it can be deleted.

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 fa fa-icon for store

code link - https://github.com/publiclab/plots2/blob/master/app/views/layouts/_header.html.erb#L70

now add this line of code <i class="fa fa-shopping-cart" style="color: white" aria-hidden="true"></i> inside <a> tag


• [ ] 💾 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!

• [ ] 📝 add logo of Public Lab along with heading

code link - https://github.com/publiclab/plots2/blob/master/app/views/layouts/_header.html.erb#L14


• [ ] 💾 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.)

My steps: 1) Run java program with listener 2) adb connect ip:port 3) We get nothing

If i create new thread with while loop and delay printing connection.getDevices().size() - it updated and print me newer devices list. But to listener it doesn't go.

Using the runner-resizer, the top of the AUT get covered up when the top bar overflows to another row

Using the window resizer, the AUT correctly adjusts, and is not coverd

See below ---------------------------v incorrect-----------------------------------------------------------------v--- correct 

Contributing to open source for the first time can be scary and a little overwhelming. I'm willing to hold your hand so you can make your first PR. The tasks mentioned in this issue are rather a bit easier than normal. And anyone who's already contributed to open source isn't allowed to touch them!

Okay, here we go! The aim of this project is to extend http://github.com/swapagarwal/JARVIS-on-Messenger functionalities to other platforms (like Telegram). Head over to http://m.me/J.A.R.V.I.S.on.Messenger and try out the features. Pick any one simple feature and we'll add it to https://t.me/jarvis_chatbot Join the conversation on Discord: https://discord.gg/MsZ9N9n 👈

I'd highly encourage you to document the process, blog and tweet about it and encourage other first timers to do the same! https://www.firsttimersonly.com/

Ombi build Version:

V 3.0.3988

Update Branch:

Master

Media Sever:

Plex

Problem Description:

It would be nice to have the episode(s) air date in the Newsletter next to the respective episode. Currently it only shows the Show launch release year.

Badly edited example:


Reproduction Steps:

Look at a generated newsletter with new TV episodes.

Thank you for everything!

Hi, this is a first-timers-only issue made from #4163. 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 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!

Issue

The navbar tabs are currently spread out in 2 lines, whereas it should be on the one same horizontal line.


Code link

https://github.com/publiclab/plots2/blob/master/app/views/users/profile.html.erb#L43-L119

Solution

This can be solved by using Bootstrap classes to hide the text (leaving only the icon) for narrower width screens!

You can visit https://getbootstrap.com/docs/3.3/ for reference.

• [ ] 💾 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!

Description

Extend functionality of plotfriends.py to specify from and to period. Currently doing for all time. Something of the type: `python plotfriends.py --from 2018-12-01, should support both--fromand--to` flags, both optional.

Mocks

Steps to reproduce (Incase of a bug)

NA

Acceptance Criteria

Update [Required]

• [ ] Support --from and --to flags in plot_friends.py ### Enhancement to Update [Optional]
• [x] [LIST ITEMS]

Definition of Done

• [ ] All of the required items are completed.
• [ ] Approval by 1 mentor.

Estimation

4-5 hours after having an idea of original code

Current behavior:

When I open Cypress and there's a new update, the update instructions tell me to use npm install --save-dev cypress@3.1.2 rather than saying yarn add --dev cypress@3.1.2.

Desired behavior:

If a yarn.lock file is detected instead of a package-lock.json file, the message should given you the yarn instructions.

The location of the update code is found at: - packages/desktop-gui/src/update/update-banner.jsx

The location of the code that tests the update banner: - integration/update_banner_spec.coffee

Steps to reproduce:

I assume you should be able install Cypress 3.1.1, run it with `cypress open and see the update button / with instructions.

Versions

• 3.1.1

Operating System

Windows 10

Played around a bit with border-collapse and 100% width but couldn't get it quite right.

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 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.

Once claimed we add you as contributor to this repository.

• [ ] 👌 Accept our invitation to this repository. Once accepted, assign yourself to this issue

• [ ] 📝 Update the file README.md in the welcome repository (press the little pen Icon) and edit the line as shown below.

diff @@ -0,0 +1,2 @@ +# welcome +first-timers-test

• [ ] 💾 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 edit files directly in your browser

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

🤔❓ Questions

Leave a comment below!

Ombi build Version:

V 3.0.3981

Update Branch:

Open Beta

Media Sever:

Emby

Operating System:

Windows 10 x64

Problem Description:

iPad Air 2 Safari: submenus do not get moved down in landscape mode

Current behavior:

Cypress currently emits an <Error: <svg> attribute height: A negative value is not valid. ("-45") when you hover over the pin icon in the sidebar, see: 

Desired behavior:

Don't emit an error when hovering over step in the sidebar

Steps to reproduce:

Run a test using Electron, and wait for it to complete, hover over the steps with the Developer Console open and see the errors come flying through

Versions

Cypress: 3.1.2 Operation System: Mac OS High Sierra Browser: Electron

We don't currently explain that when using .click() you can utilize meta keys from a previous .type('{meta}, { release: false })

An example of a confused user: https://github.com/cypress-io/cypress/issues/2795

In the .click() docs we need to give usage examples / notes of this specific use case.

We do explain this behavior in the .type() API, but unless you're aware of that you'll likely miss this entirely.

As of #168 we can now display hints when a user has entered an incorrect answer several times. This is awesome, but almost every rebus is currently lacking the hint property so lets go ahead and add some hints 🙂

This issue is very beginner friendly, just follow these steps: - Open the file src/js/rebuses.js - Have a look at the rebuses and see if you can think of any good hints - Add your hint to the rebus object: hint: 'Your hint text'

This repository will contain a lot of markdown documents and maybe some json or txt files.

We need a small script in any language that you like that scraps all the files and checks for broken links (404).

This task is not hard, the script will take no more than 100 lines, maybe it can be done in 5 lines depending on the programming language.

We will use the small script to automate the deployment of new manuals.

If you know PHP

I know this library does the job and here is a sample script that actually used it.

Note: There other libraries in other languages if you search for "broken link checker" or something like that.

🆕🐥☝ First Timers Only.

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝

About First Timers Only.

🤔 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.

Once claimed we add you as contributor to this repository.

• [ ] 👌 Accept our invitation to this repository. Once accepted, assign yourself to this issue

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

``````diff @@ -1,5 +1,7 @@ # Docker-1.12.6 Deploy

+测试 bot + Docker 容器引擎从 1.13 版本开始内置了 swarm 容器调度引擎，因此最新版本的 Kubernetes 目前只支持到Docker 1.12版本。

## 配置 ansible.cfg ``````

• [ ] 💾 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 edit files directly in your browser

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

🤔❓ Questions

Leave a comment below!

This issue was created by First-Timers-Bot.

It would be nice to ship at least basic Flow definitions in addition to TypeScript definitions. From my experiments, we can just add index.js.flow file for example to the NPM package, something like this

```js // to point flow at these type declarations in .flowconfig set // // [libs] // node_modules/cypress/index.js.flow

// Mocha functions declare function describe(name:string, callback:Function):void; declare function before(callback:Function):void; declare function beforeEach(callback:Function):void; declare function it(name:string, callback:Function):void; declare function after(callback:Function):void; declare function afterEach(callback:Function):void;

// Cypress own types declare interface subject { should(x: string, y: any): void; should('have.length', n: number): void // a lot more }

declare interface cypress { visit(url: string): cypress; wrap(x: any): subject // a lot more }

declare var cy: cypress ```

Then user projects has to include in .flowconfig

``` [ignore]

[include]

[libs] node_modules/cypress/index.js.flow

[lints]

[options]

[strict] ``` and it gets IntelliSense and type checks

Of course it is a lot of work to properly describe all available API functions and assertions, but if we get the ball rolling, users can contribute.

open http://imglab.ml/ > Open left top menu > Settings > General tab

We have to add an option in settings to set the default zoom level when an image loads. It should not impact current functionality. Settings should also saved in browser's cache.

Watch for changes, or Bookmark for easy discovery. Fund this project for new features and maintenance. [Showcase] your project with us by raising an issue

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

we should note restarting the Typescript server (Cmd+Shift+P and then type "restart TS server) or restart VS Code (or whatever editor is used).

https://github.com/cypress-io/cypress/issues/1236#issuecomment-423824058

Snap CI is no longer available: https://snap-ci.com/

They recommend looking at GoCD: https://www.gocd.org

Should be updated in our CI Provider file here: https://github.com/cypress-io/cypress/blob/develop/packages/server/lib/util/ci_provider.coffee#L31

Standard GoCD environment variables listed here: https://docs.gocd.org/current/faq/environment_variables.html#standard-gocd-environment-variables

@stufinn added a feature that will randomly generate a new Halloween custom idea.

Adding a new costume idea is a very easy addition that is beginner or first-timer friendly.

• Open scripts.js and look for // Script for Random Costume Picker
• Add an object to the costumes array with the costume name and a link to an image (or tutorial) in the following format

["Octocat", "https://twitter.com/ryanlanciaux/status/659415196058918912"],

• Please keep your suggested customs PG / SFW
• Include a source for your custom in your pull request if you can
• Limit costume additions to three to help keep the array from getting too long

Reach out if you have a question

@brandonstinson added a list of random Halloween facts that generate on page load.

The facts (strings) are stored in a facts array. Adding a new item to this array is an easy, first-timer-friendly pull request.

• Within script.js, look for the comment // Array of Halloween facts.
• Add a new fact to the facts array (try to keep them 1-2 lines long)
• Open a pull request with your new fact(s) and I'll get them added in.

Reach out if you have any questions.

Edit: Wow, there's been an explosion of pull requests relating to this template in the past 12 hours! To keep this array and JS file from getting out of hand, please limit your facts to no more than 3 lines total.

Given CYPRESS_IS_TRAVIS=true cypress open, when I run Cypress.env() in the developer tools it returns:

{ IS_TRAVIS: true }

I would expect it to instead return this based on the docs:

{ IS_TRAVIS: 'true' }

Because the documentation does not mention that string values like "true" are parsed into boolean values.

Hi Open source contributors,

Check my resources and if there is something missing send me pull request!

Have a nice day!

Add the implementation of red-black tree. It can be in any programming language though preferred ones are Java, C, Cpp or python.

first-timers-only

This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to simplify one of our tests.

The Issue

We currently do not have unit testing set up for src/drone-charging/NeedParams.ts. Please create Jest tests for the serialize() and deserialize() methods.

A good reference point for the serialize() test would be src/ride-hailing/NeedFilterParams.test.ts and src/ride-hailing/MissionParams.test.ts for the deserialize() test. Customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint. Also, you can reach out to our gitter channel with any questions 😄

The test you write will be similar to this:

```javascript import NeedParams from './NeedParams';

describe('NeedParams class', () => { let needParams: NeedParams; let serializedNeedParams: any;

beforeEach(() => { needParams = new NeedParams({ location: { lat: undefined, long: undefined }, davId: undefined, id: undefined });

serializedNeedParams = {
  ttl: undefined,
  protocol: 'drone_charging',
  type: 'need',
  location: {
    lat: undefined,
    long: undefined
  },
  davId: undefined,
  id: undefined
};

});

describe('serialize method', () => { it('should return serialized NeedParams object with the current values', () => { expect(needParams.serialize()).toEqual(serializedNeedParams); }); });

describe('deserialize method', () => { it('should return a NeedParams instance', () => { const needParamsObject = new NeedParams(); needParamsObject.deserialize(serializedNeedParams); expect(needParamsObject).toBeInstanceOf(NeedParams); });

it('should return deserialize NeedParams instance with the current parameters', () => {
  const needParamsObject = new NeedParams();
  needParamsObject.deserialize(serializedNeedParams);
  expect(needParamsObject).toEqual(needParams);
});

}); }); ```

After making your changes, run npm run jest to make sure our tests are passing.

Contributing to dav-js

• [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
• [ ] Comment in this issue that you would like to do it.
• [ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
• [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
• [ ] Install dependencies by running npm install
• [ ] Code Code Code
• [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
• [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
• [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
• [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

first-timers-only

This issue is tagged :octocat: first-timers-only. It is only for people who have never contributed to open source before, and are looking for an easy way take their first steps.

Consider this your chance to dip your toe into the world of open-source, and get some bragging rights for writing code that makes drones fly, lets cars find charging stations, helps people and goods get from place to place, and more.

Find more first-timers-only issues from DAV Foundation here.

Thank you for your help :heart:

What is this project?

DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.

As an organization that believes in building a large community of open-source contributors, we often create issues like this one to help people take their first few steps into the world of open source.

dav-js

This repo contains the DAV JavaScript SDK. This SDK allows developers to build applications and servers that connect to the DAV network. For example, allowing a drone to find charging stations, or an autonomous car to ask for traffic data.

How you can help

In order to foster a community that is welcoming for open source contributions, it is important for us to have good test coverage. And good tests are simple, readable tests.

Here is a good opportunity to simplify one of our tests.

The Issue

We currently do not have unit testing set up for src/drone-charging/MessageParams.ts. Please create Jest tests for the serialize() and deserialize() methods.

A good reference point would be src/ride-hailing/MissionParams.test.ts and customize it to the expected parameters and properties. If you are unsure what is expected, run npm run jest in the terminal and it should give you a hint. Also, you can reach out to our gitter channel with any questions 😄

The test you write will be similar to this:

```javascript import MessageParams from './MessageParams';

describe('MessageParams class', () => { let messageParams: MessageParams; let serializedMessageParams: any;

beforeEach(() => { messageParams = new MessageParams({ senderId: undefined });

serializedMessageParams = {
  protocol: 'drone_charging',
  type: 'message',
  senderId: undefined,
  ttl: undefined
};

});

describe('serialize method', () => { it('should return serialized MessageParams object with the current values', () => { expect(messageParams.serialize()).toEqual(serializedMessageParams); }); });

describe('deserialize method', () => { it('should return a MessageParms instance', () => { const messageParamsObject = new MessageParams(); messageParamsObject.deserialize(serializedMessageParams); expect(messageParamsObject).toBeInstanceOf(MessageParams); });

it('should return deserialize MessageParams instance with the current parameters', () => {
  const messageParamsObject = new MessageParams();
  messageParamsObject.deserialize(serializedMessageParams);
  expect(messageParamsObject).toEqual(messageParams);
});

}); });

```

After making your changes, run npm run tslint and npm run jest to make sure our tests are passing.

Contributing to dav-js

• [ ] Make sure this issue is labeled up-for-grabs and not labeled claimed, to verify no one else is working on it.
• [ ] Comment in this issue that you would like to do it.
• [ ] Open dav-js GitHub page and click the ★ Star and then ⑂ Fork buttons.
• [ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/dav-js.git
• [ ] Install dependencies by running npm install
• [ ] Code Code Code
• [ ] Once you've made sure all your changes work correctly and committed all your changes, push your local changes back to github with $ git push -u origin master
• [ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/dav-js) and create a pull request for your changes.
• [ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #7)
• [ ] Please do not fix more than one issue at a time. Your pull request should only fix what is described in this issue.

Asking for help

We appreciate your effort in taking the time to work on this issue and help out the open source community and the foundation. If you need any help, feel free to ask below or in our gitter channel. We are always happy to help 😄

It can be a good user experience if the library can return the list of registered routes. They can be useful for debugging purpose as well.

Please describe the problem (or idea)

Subscribe button collapsing in mobile view in mailing list.

What happened just before the problem occurred? Or what problem could this idea solve?


What did you expect to see that you didn't?

Add some margin to the subscribe button

Please show us where to look

https://publiclab.org/lists

What's your PublicLab.org username?

vikul1234

This can help us diagnose the issue:

Browser, version, and operating system

chrome, win10

Many bugs are related to these -- please help us track it down and reproduce what you're seeing!

Thank you!

Your help makes Public Lab better! We deeply appreciate your helping refine and improve this site.

To learn how to write really great issues, which increases the chances they'll be resolved, see:

https://publiclab.org/wiki/developers#Contributing+for+non-coders

I am looking for a collaborator for this repository with following conditions: - Never a collaborator before - Make me collaborator of their owned repository to expand Github knowledge

This request is for

[x] Beginners [x] First Timers [x] Non-Coders (Markdown knowledge needed)

I'm submitting a...

[ ] Bug report  
[ ] Feature request
[X] Documentation issue or request

Current behavior

Currently, the New features link on CONTRIBUTING.md (line 32, as of this writing) links to the very first issue I created last year. This doesn't work anymore as that issue has been closed (it was made for the 2017 version / branch) and there are no uses of a tag named "New Features"

Expected behavior

I think this link should either be removed entirely or replaced with a link to a different issue label

For example,

Instead of this [New features](https://github.com/scrabill/how-many-days-until-halloween/issues/1)

Something like this [Discussion](https://github.com/scrabill/how-many-days-until-halloween/issues?q=is%3Aissue+is%3Aopen+label%3Adiscussion)

Other examples would be to link to the Hacktoberfest tag

Important

Before you make a pull request, please comment on issue that you would like to work on it. That way, we can avoid duplicate PRs and a first-timer can work on this.

Add your favourite programming language to support TcSO: https://github.com/gautamkrishnar/tcso#contributing

Please see a list of currently available languages: https://github.com/gautamkrishnar/tcso#available-languages

Please comment on this issue and let the world know you are working on it.

In cy.request() and also main configuration doc, make it clearer that responseTimeout applies to mocked as well as non-mocked requests.

docs.cypress.io:

current (css width 100px)


expected (css width 102px)


docs cypress logo looks blurred because it's scaled to 100px. We should consider using an image already sized.