Crashes in 3.2.0 and 3.3.0, have not tried earlier versions
Mac
Reproduction in https://github.com/cypress-io/cypress-test-tiny/tree/no-plugins-export
npm install
npm run cypress:open
and click on spec file
Reproduction
Register undefined event handler in plugins.js file for an event like
js
module.exports = (on, config) => {
// `on` is used to hook into various events Cypress emits
// `config` is the resolved Cypress config
on('file:preprocessor')
}
and get the following crash
Stack trace in the terminal
GET /__cypress/tests?p=cypress/support/index.js-383 200 8.371 ms - 146
TypeError: event.handler is not a function
at invoke (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:17:16)
at /Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:48:16
at tryCatcher (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/bluebird/js/release/util.js:16:23)
at Function.Promise.attempt.Promise.try (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/node_modules/bluebird/js/release/method.js:39:29)
at Object.wrapChildPromise (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:47:28)
at Object.wrap (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/preprocessor.js:25:8)
at execute (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:80:20)
at EventEmitter.ipc.on (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/child/run_plugins.js:136:5)
at emitThree (events.js:136:13)
at EventEmitter.emit (events.js:217:7)
at process.<anonymous> (/Users/gleb/Library/Caches/Cypress/3.3.0/Cypress.app/Contents/Resources/app/packages/server/lib/plugins/util.js:25:29)
at emitTwo (events.js:126:13)
at process.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
GET /__cypress/tests?p=cypress/integration/spec.js-143 200 8.418 ms - 146
It would be nicer to have a much better error message here
2 Mention that baseUrl is used to check your server in cypress run now too
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
We have added leaflet-fullHash library in the bower and included the link to this library on the index page .
Let's add leaflet-fullHash object which makes the URL dynamic in accordance to selected layers of the map .
Add this lines of code after this line https://github.com/publiclab/mapknitter/blob/9aac51944a212e9c1c2cda06406c11f630d9c10a/app/views/maps/index.html.erb#L205 in index.html.erb :
var hash = new L.Hash(Mapknitterunique, allMapLayers);
```
πΎ Commit your changes
π Start a Pull Request. There are two ways how you can start a pull request:
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.
You can also edit files directly in your browser and open a pull request from there.
π Done Ask in comments for a review and also add a screenshot of the address bar of browser showing URL :)
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!
Note: This is a first-timers-only issue designed for individuals unfamiliar with contributing with open source contributions. If you're interested in working on the issue, then follow the details outlined below and communicate through this thread.
Within ZynAddSubFX, plugin parameters can be controlled through a plugin host through one of several automation slots. In the plugin host these slots are defined in a list slot 1 up to slot N. Within ZynAddSubFX however the internal and user configurable names of the various slots are slot 0 up to slot N-1. To make these two listings consistent the internal slot numbering should start with 1.
Setup:
Clone github.com/zynaddsubfx/zynaddsubfx
Clone github.com/mruby-zest/mruby-zest-build
Compile zynaddsubfx configuring GuiModule in zynaddsubfx to be zest (via ccmake)
Compile mruby-zest-build
Run zynaddsubfx -U -P 1337 (does not try to launch it's own GUI, listens to port 1337)
Run 'make run' within mruby-zest-build
Expected behavior:
Go to the 'macro learn' view on the right hand side of the GUI. Observe that slot names start with 'Slot 1'.
Actual behavior:
Slot names start with 'Slot 0'.
To fix:
Within your checkout of zynaddsubfx go into rtosc's folder and find automations.cpp. In that file the user visible slot names are set at https://github.com/fundamental/rtosc/blob/master/src/cpp/automations.cpp#L15 and https://github.com/fundamental/rtosc/blob/master/src/cpp/automations.cpp#L207 . Add the offset of 1 to those lines, recompile zynaddsubfx and verify the fix. Once that's done then you should be able to issue a pull request against fundamental/rtosc for the fix.
Very long selectors in the selector playground text input box can overflow other page elements:
Desired behavior:
When some maximum width of the field is reached (based on the browser's width), the user has to scroll to see the rest of the input. Something like this:
https://codepen.io/Momciloo/pen/bpyMbB
Steps to reproduce: (app code and test code)
Type or paste a very long selector in to the selector playground text input box. And yes, I know that using selectors that look like this is not recommended :)
Versions
Cypress 3.2, Windows 10, Chrome
8 Fix recent contributors list's logic and repository fetching precedence
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!
π¬β° - 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.
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
On the dashboard there is a subscribe button. On clicking on it a menu/modal appears. This modal can only be closed if you click on the subscribe button again. An improvement would be to only show the modal when the mouse in on the subscribe button.
πSolution
[ ] π 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
Go to _subscribe_button.html.erb
Add this trigger : 'hover', to change popover property to hover. Add it below bottom in the code snippet below.
$('#popover_button').popover({
content: $('#mypopcontent').clone().removeClass('d-none'),
placement: 'bottom',
ADD code HERE
html: true
});
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
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 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.
Class Factories
You may have noticed that Leaflet objects are created without using the new keyword. This is achieved by complementing each class with a lowercase factory method:
new L.Map('map'); // becomes:
L.map('map');
What actually does happen:
We use Leaflet's built-in L.LatLng to initialize the starting positions of our images corners, but we don't take advantage of their suggested class factory syntax. Let's update the code in the files indicated below.
Solution
Where to find the relevant lines of code:
Remove the new keyword from the following code blocks and update L.LatLng to L.latLng :
[ ] 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, if there's an additional checklist provided for getting it merged, get those boxes checked off. Either way, mention me @sashadev-sky 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, 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
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 files
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: To complete this PR, you need to match the address bar's color to PublicLab's site, i.e., a #000 black in the steps indicated here
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: To complete this PR, you need to, bring about some simple CSS changes so that the site specifies the criteria window.innerWidth === window.outerWidth, for a better accessibility score overall. Please refer here for more details.
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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 is a quick one, but important for the site's SEO at the same time. Based off the docs here you need to add a meta description to the html files. That's it!
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: Lighthouse indicates that 54.36% of the font right now is too small to read, making users pinch to zoom. To complete this PR, we advise you to read about Legible Font Sizes and accordingly correct the font sizes for different media queries as the one below.
π¬β° - 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.
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: To complete this PR, you need to redesign the index.html and select.html files in order to provide a more engaging and vivid demo to the new comers. What you implement mostly depends on your own acumen, with the essential points that,
Subexamples provided in the html files should cover all cases, i.e., the different manipulations that ime has to offer.
Theme must match the colours used over at https://publiclab.org, i.e., a contrasting combination of black and white (invert maybe?)
You can read about color contrasts, text styling and other best practices here to get you started.
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: Currently, our gh-pages demo doesn't update values. To complete this PR, you need to update replaceUrl fields in our examples/*htmlof the gh-pages branch (and NOT the main) to http://httpbin.org/post as it returns a 200 back on every POST sent to it (see cURL). We'd also appreciate if you could rope in a few lines from the README.mdhere on how to create a simple docker env to use httpbin on you local port.
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: To complete this PR, you need to remove node versions 4 and 6 from the .travis.yml file below, and add node version 10. Also, we'd like if you could add a simple "note" subsection to the README.md that shows the basic commands and workflow of the node version manager in order for a contributor to setup and switch between different node versions on their local. You should mention about basic commands such as nvm exec and nvm ls to quickly switch and list all the installed versions, etc. Refer here for help.
π¬β° - 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.
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: To complete this PR, you need to add an installation section in the README.md file that clearly depicts and covers basic steps needed for a first-timer to setup the lib, much of which can be scooped out from the "contributing" section, but should also include any personal steps you think should be mention-worthy which you might have encountered during the process. We expect you to have atleast setup the development environment once on your local machine before attempting this issue.
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: To complete this PR, you need to,
Remove bower.json
Add the same file and bower_components to .gitignore
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
All Travis CI builds are failing and have been since March 21st. This has happened before, see #177, although the root cause might be different, I haven't investigated it.
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'll need to delete the bower.json in the root folder and exclude bower_components from .gitignore as well.
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
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 test runner fails in after() block with error:
```
CypressError: cy.first() failed because it requires a DOM element.
The subject received was:
undefined
The previous command that ran was:
cy.get()
Because this error occurred during a 'after all' hook we are skipping the remaining tests in the current suite:
```
This happens each time a test step fails. In this case, it happens when the following assertion fails
js
.get('div.header__dob').should('contain', `${patient.birth_date}`)
Desired behavior:
Cleanup step should execute with Cypress commands returning values instead of undefined
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.
TODO: Fix the dropdown width which is not responsive
π 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 image-sequencer 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:
#addStep .labels {
@@ -271,4 +271,8 @@ a.name-header{
margin-bottom:0px;
align:center;
width:100%;
-}
\ No newline at end of file
+}
+
+.selectize-input {
+ width: 100% !important;
+}
``
- [ ] π **Update** the file [examples/index.html](https://github.com/publiclab/image-sequencer/blob/main/examples/index.html) in theimage-sequencer` repository (press the little pen Icon) and edit the line as shown below.
```diff
@@ -140,14 +140,14 @@
-
+
@@ -141,16 +143,16 @@
-
+
@@ -143,18 +143,18 @@
-
@@ -148,16, +148,16 @@
-
+
```
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
π¬β° - 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.
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: Currently, "Public Lab" on the navbar links the user to the rootpath i.e, dashboard. Instead it should link to the https://publiclab.org/home page as we already have a separate dashboard link on the navbar.
Update apps/views/layouts/header.html.erb in the plots2 repository.
Change href="<%= root_path %>" to href="/home" on line 14
[ ] πΎ Commit your changes
[ ] π Start a Pull Request. There are two ways how you can start a pull request:
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.
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!
Describe the bug
I am not able to delete a wrong annotation in Mac using Chrome.
To Reproduce
Steps to reproduce the behavior:
1. Go to imglab.ml/#. Open an image
2. Click on Polygon. Try to make an annotation. And then try to delete it.
3. It fails
Screenshots
<!-- If applicable, add screenshots to help explain your problem. -->
Even after pressing delete key multiple times, it is not working.
Console Errors
<!-- if possible, provide console logs (press F12 to see browser console). -->
None
Device detail
(please complete the following information):
- OS: [e.g. Ubuntu] Mac
- Browser [e.g. chrome, firefox] Chrome
Additional context
<!-- Add any other context about the problem here. -->
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
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!
π Start a Pull Request. There are two ways how you can start a pull request:
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.
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!
Part of #381
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.
ISSUE: The cursor on hovering the toggle text is not the default pointer cursor but the text cursor.
TODO: Add a CSS rule to change the cursor to pointer.
π 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 image-sequencer 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:
π¬β° - 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.
cy.server command has a really useful option onAnyRequest. Which is really practical to inject headers or do other stuff.
Here is blog post describing how it can be used : https://medium.com/agilix/cypress-testing-include-custom-http-header-on-each-http-request-2b3693813e97
This option and apparently a few other ones are not documented and are also not available in the Typescript definition (cli/types/index.d.ts) (so cannot be used when using Typescript).
Desired behavior:
Having at least the Typescript definition updated, and if possible a line in the documentation about this option.
Steps to reproduce: (app code and test code)
js
cy.server({
onAnyRequest: function (route, proxy) {
//...
}
});
This will not work when using typescript, it works with js.
This projects need a website, I would love help on this. Just a website having the information would do (~bumbly/jumbly). This is an easy task if you would like creating the base html(black text on white) code website, writing I will do.
38 Argument parsing crashes badly if passing "spec: {}"
```js
const cypress = require('cypress')
cypress.run({
// this works fine
// spec: 'cypress/integration/spec.js'
// this crashes badly - hanging Cypress
spec: {}
/*
this exits because no specs were found
Can't run because no spec files were found.
We searched for any files matching this glob pattern:
*/
// spec: []
})
```
I have created example in https://github.com/cypress-io/cypress-test-tiny/pull/44
We should document the use of @alias.all and @alias.2 within a couple of documents:
- https://docs.cypress.io/guides/core-concepts/variables-and-aliases.html
- https://docs.cypress.io/api/commands/get.html#Alias
When referencing aliases, you can reference @alias.all or @alias.2 and it will return respectively all of the aliases of that name or the 2nd request matching the name.
Examples:
js
it("does not poll for list again", function() {
cy.wait("@getList");
cy.tick(10000);
// does not poll for another request
cy.get("@getList.all").should("have.length", 1);
});
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 π