This issue is ideal for anyone new getting started contributing to the development of blogs and wants to learn more about how pelican works. This can be taken up by more than one person and the work can be split up.

MAINTAINERS/EXISTING CONTRIBUTORS please stay away from this issue for the time being (say if by July 1st no new contributors take it up, feel free to fix it yourself).

Knowledge required

1. Python 3
2. Pelican
3. HTML
4. CSS

Steps to reproduce

Setup your development environment according to README $ make serve ... (You will see all the above warnings)

Following are the warnings churned by make serve: ``` WARNING: {filename} used for linking to static content images/sponsors/grofers.png in blog/2019-announcing-grofers-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/instazen.png in blog/2019-announcing-instazen-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/merit.png in blog/2019-announcing-merit-group-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/zilogic.png in blog/2019-announcing-zilogic-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/appviewx.png in blog/2019-announcing-appviewx-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/lti.png in blog/2019-announcing-lti-silver-sponsor.md. Use {static} instead

WARNING: {filename} used for linking to static content imagSteps to reproduce

Setup your development environment according to README $ make serve ... (You will see all the above warnings) es/sponsors/microsoft.png in blog/2019-announcing-microsoft-platinum-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/bloomberg.png in blog/2019-announcing-bloomberg-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/kla.png in blog/2019-announcing-kla-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/airasia.png in blog/2019-announcing-airasia-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/episource.png in blog/2019-announcing-episource-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/reckonsys.png in blog/2019-announcing-reckonsys-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/atonarp.png in blog/2019-announcing-atonarp-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/guvi.png in blog/2019-announcing-guvi-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/mjit.png in blog/2019-announcing-mjit-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/redhat.png in blog/2019-announcing-redhat-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/zeomega.png in blog/2019-announcing-zeomega-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/toyota.jpg in blog/2019-announcing-toyotaconnected-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/cppsecrets.png in blog/2019-announcing-cppsecrets-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/deepsource.png in blog/2019-announcing-deepsource-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/elastic.png in blog/2019-announcing-elastic-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/thoughtworks.png in blog/2019-announcing-thoughtworks-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/ediitn.png in blog/2019-announcing-ediitn-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/lji.png in blog/2019-announcing-lji-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/mavenhive.png in blog/2019-announcing-mavenhive-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/dckap.png in blog/2019-announcing-dckap-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/erpnext.png in blog/2019-announcing-erpnext-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/realpython.png in blog/2019-announcing-realpython-associate-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/xapo.png in blog/2019-announcing-xapo-inkind-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/innovaccer.png in blog/2019-announcing-innovaccer-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/pipal.jpg in blog/2019-announcing-pipal-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/pramati.png in blog/2019-announcing-pramati-silver-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/ericsson.png in blog/2019-announcing-ericsson-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/happyfox.png in blog/2019-announcing-happyfox-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/stickermule.png in blog/2019-announcing-stickermule-inkind-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/indeed.png in blog/2019-announcing-indeed-platinum-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/posters/pysangamam20181.jpg in blog/2019-a-lucent-guide-to-poster-presentation.md. Use {static} instead WARNING: {filename} used for linking to static content images/posters/pysangamam20182.jpg in blog/2019-a-lucent-guide-to-poster-presentation.md. Use {static} instead WARNING: {filename} used for linking to static content images/posters/pysangamam20183.jpg in blog/2019-a-lucent-guide-to-poster-presentation.md. Use {static} instead WARNING: {filename} used for linking to static content images/posters/whyposter.png in blog/2019-a-lucent-guide-to-poster-presentation.md. Use {static} instead WARNING: {filename} used for linking to static content images/posters/posterguide.png in blog/2019-a-lucent-guide-to-poster-presentation.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/madstreetden.png in blog/2019-announcing-madstreetden-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/visiblealpha.png in blog/2019-announcing-visiblealpha-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/asldevi.jpg in blog/2019-announcing-keynote-speaker-for-pycon-india-2019-asldevi.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/aws.png in blog/2019-announcing-aws-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/jetbrains.png in blog/2019-announcing-jetbrains-gold-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/sponsors/aqr.jpg in blog/2019-announcing-aqr-platinum-sponsor.md. Use {static} instead WARNING: {filename} used for linking to static content images/jake-vanderplas.jpg in blog/2019-announcing-keynote-speaker-for-pycon-india-2019-jakevdp.md. Use {static} instead WARNING: {filename} used for linking to static content images/pyladies_aroma.jpg in blog/2019-pyladies-at-pycon-india-aroma-rodrigues.md. Use {static} instead WARNING: {filename} used for linking to static content images/david-beazley.jpg in blog/2019-announcing-keynote-speaker-for-pycon-india-2019-dabeaz.md. Use {static} instead WARNING: {filename} used for linking to static content images/ines.jpg in blog/2019-announcing-keynote-speaker-for-pycon-india-2019-ines-montani.md. Use {static} instead WARNING: {filename} used for linking to static content images/2016-van.jpg in blog/announcing-third-keynote-speaker-for-pycon-india-2016.md. Use {static} instead ```

Our README animation is few versions old, and since then the look of the tool has been updated including new icons, an inline editor for editable text, and an side bar editor.

This animation is also used on gaphor.org.

Since Gaphor looks the best in Linux, we could use someone running default GNOME to create a new animation. Peek can be used to create the animation.

Since helping to update the docs is a great way to get involved, I am would love to have someone new contribute this update. :+1:

I'm submitting a...

• [ ] Bug report <!-- Please search GitHub for a similar issue or PR before submitting -->
• [ ] Feature request
• [X] Documentation issue or request

System Information

OS: - [X] Linux (Please put in notes the specific distro) - [ ] MacOS - [ ] Windows 10 - [ ] Windows 7

NOTES:

The following exchange occurred in our Gitter chat room. A formalized version of this should be incorporated into our documentation as a topic guide on testing:

@tmontes: Given that briefcase leans towards a src-based layout -- which I like, for many reasons -- how are people running tests against their application code? My previous experience, as is the case with briefcase 0.2, is mostly based on setuptools+setup.py where I'd install the application in editable mode (with pip install -e .) and from there, running tests would be "fine" because the application modules/packages would be importable.

@freakboy3742: There’s two options. The first is to change the sources definition. Although the default Briefcase project uses the src prefix for all it’s code, it doesn’t have to; you can specify any folder you want as a source. If you drop the src prefix from the default sources definition, you can use a “prefixless” source.

The other option is to use a test runner that supports different source prefixes. pytest, for example, has a pytest-pythonpath plugin that lets you add a python_paths option in the [tool:pytest] section of setup.cfg so you can add other prefixes to your source path.

We should include details for how to use unittest, pytest and as a stretch goal - trial.

🟥🟩 WINDOWS 10 - Version 1903+ is required for the UWP UI. 🟦🟨 How to setup UWP

🌻 This issue is perfect for developers who are new to Miunie!

Summary

You need to build the UWP application and take a couple of interesting screenshots.

Take inspiration from our current set of screenshots on the MS Store:


How to implement

Post your screenshots in the comments. Don't forget about Windows accent colors, dark/light theme, windows sizes, wallpapers, etc.

You're technically not going to be recognized as a Contributor by GitHub, but commenting is going to count as a contribution on your GitHub profile. After you finish this issue, you'll have the project setup. So that's a great opportunity to take another issue. 🙂

If you really don't want to contribute in any other way, you will be credited in the README.md.

Interested? 😊

If you'd like to help us by solving this issue, just say so in the comments. ❤️ And don't shy away from asking any kind of question you might have.

Should you have any questions at all, feel free to contact either me (@petrspelos) or @DraxCodes on our Discord server:


And of course, thank you so much for contributing! 🎉 It's because of amazing people like yourself that Miunie exists.

Is it your first time contributing to open source? First time coding something? This issue is perfect for you! 🥳

Letra features a small quote about learning a new language along with the word for the day, as shown here: 

This is randomized everyday so that people can see a new quote that inspires them everyday!

How To Contribute

1. Go to the Contributing Guidelines to get started
2. The documentation for adding a new quote can be found here.
3. If at any part of the process you find yourself stuck, tweet me @jayehernandez_, and we can go through it together!

Some Reminders

• No need to wait for a confirmation if you'd like to add a quote.
• Just open up a pull request when you're done and reference this issue.

Originally reported as a PR on beeware

I was following the beeware tutorial and I got the following error

``` (beeware-venv) $ briefcase create iOS xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

Xcode is not installed.

You should be shown a dialog prompting you to install Xcode and the command line tools. Select "Get Xcode" to install Xcode from the app store. You can install Xcode from the macOS App Store. Re-run Briefcase once that installation is complete. ```

It took me a while to figure out how to solve this because I already had Xcode installed.

The solution was: (beeware-venv) $ sudo xcode-select -s /Applications/Xcode.app/Contents/Developer

The problem is that the XCode is installed, but the command line tools are currently the active install.

The error message needs to differentiate between: * XCode command line tools are installed, but XCode isn't installed * XCode command line tools and XCode are installed, but command line tools are active.

and present an appropriate error message in both cases.

This PR adds Firefox to the list of secure browsers by only using internal configuration options.

Before Adding Resources Goto The CONTRIBUTING.md File. So The Resources You have To have To Add In README : 1. Add Resources(Name or link) For Books Section 2. Add Resources(link) For Linux In Open Source World Section 3. Add Resources(link) For Books Section 4. Add Resources(link) For Courses Section 5. Add Resources(link) For Tools and Version Control Systems Section 6. Add Resources(link) For Open Source Contest Section 7. Add Resources(link) For Cheetsheets Section 8. Add Resources(link) For Open Source Projects For Beginners Section

What is to be done?

Hi! You use the translation key Following as for the menu option AND page title to list videos from your subscriptions.

• In french, if we are using the same word, it would need to be plural in this specific case. Which we can't because it would also change the button in a channel that allow you to follow/unfollow.

Alternatively, we could use another word like Subscriptions, which seems to already make more sense in this particular case.

• Using Following also is also misused/would be misunderstood:
  • The french equivalent, in this context, is mainly used to mean "X that are following me". In fact, you mean the opposite, channels that I do follow.
  • The other thing that botter me (in english as well) is that we may think it is the page that will ultimately manage our subscriptions. Which is way off, it will list videos from our subscriptions.

With all those points it could make more sense to use Subscriptions videos or Following channels (which look weird to me in english) if we want to use the same word.

NOTE: I know this is an issue, I don't mean to have the right answer and I'm no way linguistics. Feel free to suggest or/and comment.

:mag_right: Files To Look Into:

For the menu item: https://github.com/lbryio/lbry-desktop/blob/master/ui/component/sideNavigation/view.jsx#L106

For the page title: https://github.com/lbryio/lbry-desktop/blob/master/ui/page/channelsFollowing/view.jsx#L28

Suggested labels

help wanted, level 0, area: subscriptions (I think, otherwise/and channel), good first issue

Possibly: needs: exploration

Expected Behavior

Install toga-demo

Current Behavior

``` ERROR: Command errored out with exit status 1: command: 'c:\program files\python38\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\*\AppData\Local\Temp\pip-install-h9n2linw\pythonnet\setup.py'"'"'; file='"'"'C:\Users\*\AppData\Local\Temp\pip-install-h9n2linw\pythonnet\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users*\AppData\Local\Temp\pip-record-l1lqd2bo\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\program files\python38\Include\pythonnet' cwd: C:\Users*\AppData\Local\Temp\pip-install-h9n2linw\pythonnet\ Complete output (6 lines): usage: setup.py [global_opts] cmd1 [cmd1opts] [cmd2 [cmd2opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help

error: option --single-version-externally-managed not recognized
----------------------------------------

ERROR: Command errored out with exit status 1: 'c:\program files\python38\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\*\AppData\Local\Temp\pip-install-h9n2linw\pythonnet\setup.py'"'"'; file='"'"'C:\Users\*\AppData\Local\Temp\pip-install-h9n2linw\pythonnet\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users****\AppData\Local\Temp\pip-record-l1lqd2bo\install-record.txt' --single-version-externally-managed --compile --install-headers 'c:\program files\python38\Include\pythonnet' Check the logs for full command output. ```

Steps to reproduce

1. (With a fresh install of windows and .net 4.8) pip install --upgrade setuptools wheel pip install --pre toga-demo

Your Environment

• Python Version (list the specific version number) 3.8.3rc1

• Operating System and Version (select from the following and list the specific version number; if your OS is not listed, list that as well)

  • [ ] macOS - version:
  • [ ] Linux - distro: - version:
  • [x] Windows - version: Windows 10 Build 18363
  • [ ] Other - name: - version:

• Toga Version (list the specific version number or git hash) v0.2.15

• Toga Target (the type of app you are trying to generate)

  • [ ] android
  • [ ] cocoa
  • [ ] django
  • [ ] gtk
  • [ ] iOS
  • [ ] tvOS
  • [ ] watchOS
  • [ ] winforms
  • [ ] win32
  • [ ] Other (please specify)

Originally reported as a side effect of #300

If you have previously run briefcase create for a given app, you'll be warned, and prompted to delete the old app: ``` (beeware-venv) lov080@DARKZERO-LN helloworld % briefcase create iOS

Application helloworld already exists; overwrite (y/N)? y ``` Briefcase currently assumes that the app deletion is complete.

However, if something prevents the app from being deleted (e.g., an open terminal session, or the app being currently open, you will get an error: [helloworld] Removing old application bundle... Traceback (most recent call last): File "/Users/lov080/Google Drive/Python/BeeWare/examples/beeware-tutorial/beeware-venv/bin/briefcase", line 12, in <module> sys.exit(main()) File "/Users/lov080/Google Drive/Python/BeeWare/examples/beeware-tutorial/beeware-venv/lib/python3.8/site-packages/briefcase/__main__.py", line 11, in main command(**options) File "/Users/lov080/Google Drive/Python/BeeWare/examples/beeware-tutorial/beeware-venv/lib/python3.8/site-packages/briefcase/commands/create.py", line 610, in __call__ state = self.create_app(app, **full_kwargs(state, kwargs)) File "/Users/lov080/Google Drive/Python/BeeWare/examples/beeware-tutorial/beeware-venv/lib/python3.8/site-packages/briefcase/commands/create.py", line 564, in create_app self.shutil.rmtree(str(bundle_path)) File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/shutil.py", line 730, in rmtree return _rmtree_unsafe(path, onerror) File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/shutil.py", line 612, in _rmtree_unsafe onerror(os.rmdir, path, sys.exc_info()) File "/Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/shutil.py", line 610, in _rmtree_unsafe os.rmdir(path) OSError: [Errno 66] Directory not empty: '/Users/lov080/Google Drive/Python/BeeWare/examples/beeware-tutorial/helloworld/iOS/Hello World' but the create command will continue, resulting in a state where the app hasn't been recreated.

This edge case needs to be caught and corrected - we should check that the deletion completed without error before creating the new app.

Is your feature request related to a problem? Please describe.

Predicate determining if the number is a natural number. Natural numbers according to ISO 80000-2 corresponds to the non-negative integers 0, 1, 2, 3

Describe the solution you'd like js isNaturalNumber(1); //=> true

Describe alternatives you've considered

Excluding zero from the non-negative integers. Though non-negative integers + 0 seems to be more standard set.

Additional context

https://en.wikipedia.org/wiki/ISO/IEC_80000

Documentation for RA.isEven needs to be changed, because it claims that 0 is not a natural number.

🆕🐥☝ 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 💝

🤔 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 will assign you this issue.

• [ ] 👌Once assigned, start working on this issue.

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

``````diff @@ -144,7 +144,7 @@ _There are many beginner level issues to begin with, which include documentation

#### 2. Is this a hardware/IoT project?

-Yes, it is a hardware/IoT + software project. There would be maximum tasks related to frontend, backend, design and documentation of the website and later, it would be integarted with the real-time data from the sensors. +Yes, it is a hardware/IoT + software project. There would be maximum tasks related to frontend, backend, design and documentation of the website and later, it would be integrated with the real-time data from the sensors.

#### 3. How to communicate with us?

``````

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

Consider leaving a ⭐ here.

Environment (please complete the following information): - WebdriverIO version: 6.1.5 - Mode: WDIO Testrunner - If WDIO Testrunner, running sync/async: sync - Node.js version: 14.1.0 - NPM version: 6.14.4 - Browser name and version: Chromium 78.0.3882.0 (installed by Puppeteer) - Platform name and version: Mac OS X 10.15.4 - Additional wdio packages used (if applicable): @wdio/devtools-service v6.1.8 puppeteer v3.0.4

Config of WebdriverIO An example of how you configured WebdriverIO config:

``` capabilities: [{ browserName: 'chrome', 'goog:chromeOptions': { w3c: false, binary: puppeteer.executablePath(), args: [ '--aggressive-cache-discard', '--disable-application-cache', '--disable-cache', '--disable-dev-shm-usage', '--disable-extensions', '--disable-gpu', '--disable-notifications', '--disable-reading-from-canvas', '--disable-offline-load-stale-cache', '--disk-cache-size=0', '--enable-aggressive-domstorage-flushing', '--headless', '--no-sandbox', '--whitelisted-ips', ], }, }],

```

Describe the bug On a variety of occasions, including but not limited to browser.reloadSession(), devtools will check the browser name against a list of acceptable browser names in the constants file and then throw an error because WDIO (presumably) has set the browser name to a value not in that file. It will then often time out with a memory leak.

in node_modules/devtools/build/launcher.js:

function launch(capabilities) { console.log(JSON.stringify({ capabilities }, null, 2)); console.log(new Error().stack);

In log:

``` "capabilities": { "browserName": "Chrome Headless", "browserVersion": "78.0.3882.0", "platformName": "darwin", "platformVersion": "19.4.0", "goog:chromeOptions": { "debuggerAddress": "localhost:60726", "w3c": false, "binary": "/Users/steven/code/webapp/nodemodules/puppeteer/.local-chromium/mac-686378/chrome-mac/Chromium.app/Contents/MacOS/Chromium", "args": [ "--aggressive-cache-discard", "--disable-application-cache", "--disable-cache", "--disable-dev-shm-usage", "--disable-extensions", "--disable-gpu", "--disable-notifications", "--disable-reading-from-canvas", "--disable-offline-load-stale-cache", "--disk-cache-size=0", "--enable-aggressive-domstorage-flushing", "--headless", "--no-sandbox", "--whitelisted-ips" ] } } } [0-0] Error at launch (/Users/steven/code/webapp/nodemodules/devtools/build/launcher.js:117:15) at Function.reloadSession (/Users/steven/code/webapp/nodemodules/devtools/build/index.js:109:49) at Browser.reloadSession (/Users/steven/code/webapp/nodemodules/webdriverio/build/commands/browser/reloadSession.js:25:24) at runMicrotasks () at processTicksAndRejections (internal/process/taskqueues.js:97:5) at async Browser.runCommandWithHooks (/Users/steven/code/webapp/nodemodules/@wdio/sync/build/wrapCommand.js:88:21) [0-0] [WDIO]: The step "should let the new user login" failed [0-0] Error in "User Management Flow should let the new user login" Couldn't identify browserName chrome headless [0-0] Error in ""after all" hook in "{root}"" Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a <--- Last few GCs --->

[34690:0x10411b000] 226491 ms: Scavenge 2043.1 (2047.2) -> 2042.3 (2047.2) MB, 9.2 / 0.7 ms (average mu = 0.297, current mu = 0.318) allocation failure [34690:0x10411b000] 226564 ms: Scavenge 2043.2 (2047.2) -> 2042.5 (2047.8) MB, 8.5 / 0.7 ms (average mu = 0.297, current mu = 0.318) allocation failure [34690:0x10411b000] 226631 ms: Scavenge 2043.3 (2047.8) -> 2042.5 (2047.8) MB, 5.8 / 0.7 ms (average mu = 0.297, current mu = 0.318) allocation failure

<--- JS stacktrace ---> ```

To Reproduce Steps to reproduce the behavior: as above

Expected behavior Either (1) chrome headless is in the constants file, or (2) WDIO (presumably) does not change the name of the browser to Chrome Headless. Either way, there is then (1) no error, (2) no timeout and (3) no memory leak.

We need more encoders/decoders, ie String to Hex, String to MD5 etc.

💡 Here are some ideas https://www.browserling.com/tools/

To add an encoder or decoder, follow the Contributing Guide

Environment (please complete the following information): - WebdriverIO version: 6.1.8 - Mode: WDIO Testrunner - If WDIO Testrunner, running sync/async: sync - Node.js version: v12.16.1 - NPM version: 6.13.4 - Browser name and version: Chrome 81 - Platform name and version: macOS Catalina 10.15.4 (19E287)

package.json "devtool" config { "name": "wdio6", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "wdio" }, "keywords": [], "author": "", "license": "ISC", "devDependencies": { "@wdio/cli": "^6.1.8", "@wdio/allure-reporter": "^6.1.5", "@wdio/devtools-service": "^6.1.8", "@wdio/dot-reporter": "^6.1.5", "@wdio/local-runner": "^6.1.8", "@wdio/mocha-framework": "^6.1.8", "@wdio/sync": "^6.1.8" } } "chromedriver" config ( note only changes - devtools-service replaced by 2 chrome options)

{ "name": "wdio6", "version": "1.0.0", "description": "", "main": "index.js", "scripts": { "test": "wdio" }, "keywords": [], "author": "", "license": "ISC", "devDependencies": { "@wdio/cli": "^6.1.8", "@wdio/allure-reporter": "^6.1.5", "chromedriver": "81.0.0", "wdio-chromedriver-service": "^6.0.3", "@wdio/dot-reporter": "^6.1.5", "@wdio/local-runner": "^6.1.8", "@wdio/mocha-framework": "^6.1.8", "@wdio/sync": "^6.1.8" } }

Config of WebdriverIO only changes here - service ["devtools"] and ["chromedriver"] accordingly

``` exports.config = { runner: "local", maxInstances: 10, logLevel: "info", bail: 0, waitforTimeout: 10000, connectionRetryTimeout: 90000, connectionRetryCount: 3,

specs: [
    "./test/**/*Spec.js"
],
capabilities: [{
    "browserName": "chrome",
    "goog:chromeOptions": {
        excludeSwitches: ["enable-automation"]
    }
}],
services: [
    ["devtools"]
],
framework: "mocha",
reporters: ["dot",
    ["allure", {
        outputDir: "allure-results",
        disableWebdriverStepsReporting: false,
        disableWebdriverScreenshotsReporting: false
    }]
],    mochaOpts: {
    ui: "bdd",
    timeout: 60000
},
afterTest(test, context, { error, result, duration, passed, retries }) {
    if (!passed) {
        browser.takeScreenshot();
    }
}

}; ```

Test ``` const assert = require('assert')

describe('on webdriver.io page', () => { it('this test will fail on purpose', () => { browser.url('https://webdriver.io') browser.takeScreenshot(); const title = browser.getTitle() assert.strictEqual(title, 'Web3verIO · Next-gen browser automation test framework for Node.js') }) }) ```

Describe the bug while running using ["chromedriver"] service - 2 screenshots were created and added to allure report - all GET and POST requests to the browser are logged - the browser has no version in the report resulting xml report https://pastebin.com/efjRQG8X

while running using["devtools"] service - no screenshots were created and added to allure report - no GET and POST requests to the browser are logged - the browser has a weird version in the report - Chrome-19.4.0 resulting xml report https://pastebin.com/Y6Zvbs0E

To Reproduce npm test

Expected behavior to have same behaviour using devtools service as in chromedriver

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/mapmixins/DoubleClickZoom.js file from ES5 to ES6.

Solution

For the 6 L.Map.DoubleClickZoom methods, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/mapmixins/MapMixins.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 2 functions in src/mapmixins/MapMixins.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/util/DomUtil.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 5 functions in src/util/DomUtil.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/util/Utils.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 2 functions in src/util/Utils.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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


When I didn't have WiX installed (or the WIX environment variable is unset), I would have expected the longer error message from here: https://github.com/beeware/briefcase/blob/master/src/briefcase/platforms/windows/msi.py#L39

Divide searched files into batches to speed search time

Currently, we have no documentation of the existing functions, but they are demonstrated in the examples at example/lib/main.dart under the runAFunction method.

Write base level documentation for the same in Sphinx, in the doc/source/index.rst file. Making changes to this file (or the files in this directory) will directly affect the documentation generated at https://flutter-opencv.readthedocs.io/en/latest/

Just fork the code; write the documentation; send across a pull request to this repository. Once the request is accepted, the documentation pages will rebuild. (i.e. you might want to run Sphinx locally in order to ensure everything works fine, but this is an extra step).

Verbatim from the project README: Since you're never going to just implement one function, there's a need to be able to cascade. Inputs & outputs to all functions are common - byte arrays. Hence output from one function can directly be fed to the next.

This means that all functions take the same byte arrays (exceptions include functions that need a grayscale image instead of a binary one, but the grayscale image too is in a byte array form!), e.g. houghCircles. In general, in OpenCV, a lot can be achieved by using 2-3 different functions in succession. For example, something as simple as Canny edge detection (https://opencv-python-tutroals.readthedocs.io/en/latest/pytutorials/pyimgproc/pycanny/pycanny.html) would require one to convert the source image to grayscale, then apply some blur to it, then run the Canny function.

Find any good use case for the same and add your function to the examples in example/lib/main.dart which showcases the demo app.

To add an example to the app: - Simply add a new switch case in runAFunction - Add the string calling this function in the Dropdown Widget After you do this, every time someone selects your new function name from the dropdown and clicks on run, your own cascaded/successive function(s) run in the runAFunction method and throw an output image.

So you want to contribute? That's great!

Kinto now officially uses xkeysnail as its preferred method of key remapping. While you can still install the xkb/kintox11 based method xkeysnail will take priority and is simpler to work with

Clone master or fork master git clone https://github.com/rbreaves/kinto.git

GUI Keys | Value| Description|Mac/Kinto Equivalent| | ----- |:--------:|:--------:| |C,Ctrl|Control|Cmd| |M,Alt| Alt/Option|Alt/Option| |Super | Win/Super|Ctrl|

Terminal Keys | Value| Description|Mac/Kinto Equivalent| | ----- |:--------:|:--------:| |RC,RCtrl|Right Control on Left & Right Alt/Cmd key|Cmd| |M,Alt| Alt/Option|Alt/Option| |Ctrl | Ctrl|Ctrl|

You can define new keymaps for your specific app via this method. You also do not have to cancel out the original keybinding if you do not need or want to, but you can do so with "passthroughkey".

Defining Keymaps Per App

```

Keybindings for Sublime Text

definekeymap(re.compile("Sublimetext"),{ K("C-h"): passthroughkey, # cancel replace K("Ctrl-Alt-f"): K("Ctrl-h"), # replace K("C-M-v"): [K("C-k"), K("C-v")], # pastefromhistory } ```

In the above example I am also showing that you can define a single shortcut to enact multiple shortcut keys if needed by defining an array of shortcuts to trigger.

You can also make changes to the file in your /tmp/kinto/xkeysnail/kinto.py location and see them take affect in real time, but for your changes to be permanent you will need to make your changes in the ~/.config/kinto/kinto.py location.

More information can be seen on the readme page of xkeysnail.

Note on submitting keymaps for consideration

If it is a basic system level keymap then please consult ticket #44 and the excel doc to ensure that you are aware of all of the possibly differing hotkeys between DE's before submission and try to account for them in the setup.py and kinto.py file.

If it is more DE, application or language specific and then considering commenting it out in the kinto.py config file. This will allow me, or you, to create it as an installable option in xkeysnail_service.sh.

An example

# K('Shift-KEY_3'):K('KEY_EURO'), # UK KBD

XKB Shortcut Creation

The older xkb shortcut method info can be read about in ticket #125.

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/edit/actions/ScaleAction.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 2 functions in src/edit/actions/ScaleAction.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/edit/handles/ScaleHandle.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 2 functions in src/edit/handles/ScaleHandle.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for a different method. These ones should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; },

ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

What happens:

On the publliclab dashboard: https://publiclab.org/dashboard, the dropdown caret for the share your work button is black. This causes some unusual hover behavior as it quickly toggles between black and white when you click on it.


Note: (not shown above) that it also toggles between black and white on hover when the dropdown is expanded.

Solution

We can make it stop toggling between black and white by just initially setting it to white.

Where to find the relevant lines of code:

https://github.com/publiclab/plots2/blob/dc6a61f60761eb5731f4e1d27f25ee572352ba44/app/views/sidebar/_dashboard.html.erb#L5

What to change them to:

add the class "fa-white" to the end of the class on the a tag linked above.

Thanks!!

Step by Step

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

Please keep us updated

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

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

💬 Get help

If you need any help - here are some options:

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

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

configparser is a widespread, simple-to-use module that's primarily used to create and manipulate configuration files.

Currently, one can use this bot by entering their Twitter credentials in a file called credentials.py in the src folder in a way that's slightly unorthodox and non-standard and may even be intimidating towards new contributors.

https://github.com/AlwaysLivid/TinyFlowerBeds/blob/856445843b986ff27a1619012332a2cd0b87d539/src/bot.py#L82

The part that loads the credentials for the Twitter bot should be rewritten, so that it loads an *actual** configuration file instead, rather than a Python module. It should contain the same variables and the same functionality. *We shouldn't import a "module" with 4 variables.

You can see how a user can load credentials under normal circumstances in the README file.

You can find official documentation and instructions in the Python docs. Here's a checklist of what you should do; * Have the bot import configparser * Rewrite the lines 79-87 (as of 8564458). * Add a sample configuration file inside of the src folder. * Replace the instructions in the README file file in a separate commit. * Open a pull request :D

• Delete yarn.lock
• Run yarn
• Commit the updated yarn.lock
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Delete yarn.lock
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Delete yarn.lock
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

I initially started TinyFlowerBeds in order to better understand Python's useful (and silly) applications and how to create apps that will interact with social media. After I took a simple approach for it, I made an intro screen that shows the name of the project, a copyright notice for the project's license and also added my name with a copyright sign.

https://github.com/AlwaysLivid/TinyFlowerBeds/blob/ad525983d4a143db1f34802e38ea2460c55bab4d/src/bot.py#L18

I essentially abandoned the project, but I've revived it, because I noticed that it's a simple fun thing to work on and that others could learn some useful stuff by fiddling around with it (just as I did). When I started working on it, however, I did not expect anybody else to improve the thing that I did. There has been some interest revolving around it and there have been people that have contributed their own source code! According to the GNU General Public License v3, the rights to the source code that they wrote belongs to them. I'm not the only copyright holder anymore!

So, here's what should change; * The year should be updated from 2018-2019 to 2018-2020. * Change my alias (AlwaysLivid) to something that includes my name, as well as the contributors, as well as a link that lists all of the people that have contributed to the bot on GitHub. * Make sure that the alignment remains intact. Feel free to make changes all over the string in order to maintain that.

The option "Visit home page" is always disabled.

https://github.com/beeware/toga/blob/b2934d3fc8a67af9e2d16ee95909062939cf9f8f/src/winforms/toga_winforms/app.py#L60

I solved it with "import os" and adding the following anonymous function

toga.Command(lambda s: os.startfile(self.interface._home_page), 'Visit homepage', group=toga.Group.HELP) 

But I need to know if it's possible from Toga without having to edit the source code.

Excuse my English, I'm from Peru!

The page needs to be doublechecked and reviewed.

https://github.com/arduosoft/RawCMS/blob/features/logcollecting/docs/LogCollecting.md

We can definitely increase the number of our premade lifeforms in Seagull. I only started with a few, but in LifeWiki there seems to be a lot more!

Will need some help on this, any takers? You can add 1 or 2 from LifeWiki, I can help you along the way! https://conwaylife.com/wiki/Main_Page

How to start

Choose a fun Lifeform from LifeWiki: https://conwaylife.com/wiki/Main_Page then comment it here. Once I gave the go signal or a thumbs up 👍 , then just make a PR! You can simply copy how other Lifeforms were implemented in Seagull. I can guide you along the way!

Current behavior:

Safari is currently not supported. However, the error message is misleading user to think that Safari is not installed vs it not being supported.

```

npx cypress run --browser "safari"

Can't run because you've entered an invalid browser name.

Browser: 'safari' was not found on your system.

Available browsers found are: chrome, firefox, electron ```

Desired behavior:

Accurate error message. For example:

```

npx cypress run --browser "safari"

Can't run because you've entered an invalid browser name.

Browser: 'safari' is not supported

Supported browsers are: chrome, firefox, electron, edge ```

Test code to reproduce

Run the following on a host with Safari installed. npx cypress run --browser "safari"

Versions

1. Cypress ➜ npx cypress -v Cypress package version: 4.3.0 Cypress binary version: 4.3.0

2. Operating System macOS 10.15.4

3. Browser Safari

Related #6422

Implement front-end test cases for the project

Claim this issue first by commenting here to prevent multiple people working on the same issue.

Raise a PR with a description that says Fixes #1

Steps for completing the task:

1. Fork the repo
2. Make your necessary changes.
3. Submit a PR

Leave a star if you like the project!

First Time?

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

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

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

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

🤔 What you will need to know.

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

The problem

We just added support for ES6 in our library, and would like to start transitioning our code to use this syntax.

Let's update the method creation syntax in the src/util/TrigUtil.js file from ES5 to ES6.

Solution

Where to find the relevant lines of code:

For the 3 functions in src/util/TrigUtil.js, remove the function keyword and attach the method arguments to the method name instead.

Here is an example of how this will look for one of the methods, the rest should follow suit:

ES5 JS radiansToDegrees: function(angle) { return (angle * 180) / Math.PI; }, ES6 JS radiansToDegrees(angle) { return (angle * 180) / Math.PI; },

Thanks!!

Step by Step

• [ ] Claim this issue with a comment here, below, and ask any clarifying questions you need
• [ ] Fork the repository and set it up locally following the main repo README instructions https://github.com/publiclab/Leaflet.DistortableImage
  • [ ] 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

• Delete package-lock.json
• Run npm install
• Commit all the changes
• Create a Pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

Current behavior:

We use --env variable to pass some environment variables to cypress, when it's running both in headless and headed mode.

One of the parameters is a hash (mix of numbers and characters). Surprisingly some specific hash values make cypress to fail reading this value from the command line (e.g. 769e98018). The corresponding environment variable is not set and the Cypress.env() function returns with null.

Desired behavior:

It should not be a problem to read a hash from the command line and put into an environment variable.

Test code to reproduce

A simplified command line call:

node_modules/cypress/bin/cypress open --env WSD_VERSION_HASH=769e98018

Test code showing the issue:

js describe('Hash test.', function() { it('Test 1.', function() { expect(Cypress.env('WSD_VERSION_HASH')).to.equal('769e98018'); }); }); This test fails with: 'expected null to equal 769e98018'

If I remove the 'e' character for example, then the value is read correctly.

Versions

Cypress 4.1.0 OpenSUSE 15.1 and Ubuntu 18.04

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.

ZynAddSubFX has many effects. All effects have a set of presets, which allows users to quickly find good examples of how the effects can sound. One of the effects is the dynamic filter (often only called "DynFilter"). In the DynFilter UI, however, a combo box for the preset is missing. Instead, there are currently two (redundant) combo boxes for the filter category.

Setup:

1. Clone github.com/zynaddsubfx/zynaddsubfx
2. Clone github.com/mruby-zest/mruby-zest-build
3. Compile zynaddsubfx configuring GuiModule in zynaddsubfx to be zest (via ccmake)
4. Compile mruby-zest-build
5. Run zynaddsubfx -U -P 1337 (does not try to launch it's own GUI, listens to port 1337)
6. Run 'make run' within mruby-zest-build

Expected behavior:

Exactly one combo box for the filter category, and exactly one for the preset.

Actual behavior:

Two redundant combo boxes for the filter category, and none for the preset.

To fix:

The fix can be done in a submodule of the mruby-zest-build repo.

1. Find out which qml file is affected (hint, search for one of the names of the knobs). It's not that difficult.
2. Remove the duplicate "Pcategory" widget there.
3. Find out how the category was added for another effect (e.g. Distorsion) and write analog code for the DynFilter.
4. Find out which submodule you changed (git status in the main menu). Make a PR for that submodule.

Because inotify may send multiple events in rapid succession (i.e. INCREATE followed by INATTRIB), duplicate alerts often get logged. Add code to avoid generating identical alerts.

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

```diff - 6:

<%= raw t('usersessions.new.login') %>

<%= raw translation('usersessions.new.login') %>

• 9: <%= raw t('usersessions.new.signup') %> <%= raw t('usersessions.new.tojoin') %>

• 9: <%= raw translation('usersessions.new.signup') %> <%= raw translation('usersessions.new.tojoin') %>

• 28: <%= t('user_sessions.new.username') %>

• 28: <%= translation('user_sessions.new.username') %>

• 32: <%= t('user_sessions.new.password') %>

• 32: <%= translation('user_sessions.new.password') %>

• 47: tabindex="3"><%= t('usersessions.new.login') %>

• 47: tabindex="3"><%= translation('usersessions.new.login') %>

• 51: <%= f.checkbox :rememberme %> <%= t('usersessions.new.rememberme') %>

• 51: <%= f.checkbox :rememberme %> <%= translation('usersessions.new.rememberme') %>

• 57:

  <%= raw t('usersessions.new.resetbyclickinghere', :url1 => "/reset/") %>

• 57:

  <%= raw translation('usersessions.new.resetbyclickinghere', :url1 => "/reset/") %>

  ```

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

```diff - 16: <%= t('notes.notes.moderatefirsttimepost') %>
+ 16: <%= translation('notes.notes.moderatefirsttimepost') %>

• 17: <%= t('notes._notes.views') %>

• 52:

• Total Views: <%= numberwithdelimiter(node.views) %> <%= translation('notes._notes.views') %>

• 57:

• <% if @currentuser && ['admin','moderator'].include?(@currentuser.role) %> <%= t('notes._notes.spam') %><% end %>

• 57:

• <% if @currentuser && ['admin','moderator'].include?(@currentuser.role) %> <%= translation('notes._notes.spam') %><% end %>

• 58:

• <%= t('notes._notes.spam') %>

• 61: <%= translation('notes._notes.spam') %> ```

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

Gitsie lacks proper documentation. there needs to be well-explained docs from both developers' and users' point of view.

4.md

• Give a description and explanation of why and what a cursor is and why we need a class for it.Don't focus on length but on getting the important points down.
• Give a description and explanation of why and what pagination is and why we mention it here.Don't focus on length but on getting the important points down.

2.md

• Add a better explanation and example of OAuth and authentication in general (in the first paragraph) #### 1.md
• Please get a better visual here(one that pertains more to both streaming and cursors in the context of the Twitter API)

Note: The most updated cards are on the Nathan Twitter -New branch

Like every open source project, we are looking for contributors. Any kind of help is welcome. Just a star on the project is a lot for us, to be known. Another big issue for a growing project like our is to have feedbacks.

As the first step, the easy and most important contribution you can give us is to test the tool and share your impression about the project. Please invest 1 minute of your time to fill a quick survey and tell your opinion.

https://forms.gle/c8JKCPWkzQqtig1F8

As this project is shortlisted to accept contributions under RGSoC, it'll be a great idea to include a dedicated FAQ section for RGSoC.

• Check out the project here.
• Check this for more info.

Refer to the FAQ section for GSSoC.

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

diff - <i class="fa fa-question-circle"></i> <span class="d-lg-inline"><%= t('tag.show.questions') %></span> + <i class="fa fa-question-circle"></i> <span class="d-lg-inline"><%= translation('tag.show.questions') %></span> Do this for lines 10 13 14 17 24 26 32 37 40 43 and 46.

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

diff - <p><%= raw t('tag.show.no_results_found', tag: params[:id]) %>:</p> + <p><%= raw translation('tag.show.no_results_found', tag: params[:id]) %>:</p> Do this for lines 7 and 47.

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

diff - <h3><%= t('users._photo.profile_photo') %></h3> + <h3><%= translation('users._photo.profile_photo') %></h3> Do this for lines 13 24 26 and 37.

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

TODO:

On line https://github.com/publiclab/plots2/blob/master/app/views/notes/index.html.erb#L12 AND https://github.com/publiclab/plots2/blob/master/app/views/notes/index.html.erb#L114, replace raw t( to raw translation(

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

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

diff $DIFF

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

(This issue is in continuation of #6206 )

Hi everyone!

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

Reasons being:

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

If you are interested in creating first-timers-only issue, follow these instructions:

Browse through the publiclab.org and see if there's a bug which can be easily solved Solve this issue but don't create a PR this time, instead create a FTO issue Click on this link to start creating a new issue We follow a specific template for FTO issues, so copy the template from here Edit the issue body to add the goal of the issue, code snippet required, file to be updated, add screenshots(if required). Don't add code snippet required to solve in case, the issue just requires minor HTML or CSS change or equivalent. Add a catchy and relevant title to the issue but don't include "FTO" , "first-timers-only" or equivalent in title Get the issue you just created labeled by mentioning @publiclab/reviewers or @publiclab/plots2-reviewers. If you have labeling privileges, feel free to do so yourself but ensure that you have used FTO template. If you are not able to mention the above-mentioned teams, and doesn't have labeling privileges, then drop a line in Gitter channel - https://gitter.im/publiclab/publiclab or mention @jywarren @cesswairimu @emilyashley @SidharthBansal and any one of us will surely follow-up with you. You can also mention any other member, you can think of with labeling privileges. It's time to invite a new contributor to your issue. If there are unchecked names in the below list, then those people are still looking for FTO issue to start with, so mention them in your FTO by writing - This issue is created for @[contributor-name]. Thanks! Also, if you see, a new contributor is looking for an issue, feel free to point them to your FTO

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

• [x] @taysa91 - #7664
• [x] @TroydonAnabolic - https://github.com/publiclab/plots2/issues/7685

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

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

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

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete yarn.lock
• Run yarn
• Commit all the changes
• Create a Pull request

Is your feature request related to a problem? Please describe. Create a design of the landing page using the tool of your choice (it might be Pen/Pencil and Paper)

Describe the solution you'd like Your design should be appealing to the user and must be related to the idea of the Water monitoring system. You should try to put relevant content as required at different places in the design itself but it's okay if you cannot think of some for certain parts of the website. We can refine this later on.

Compare and create the PR into the feature/frontend branch, and not the master.

Additional context Please don't include tank divs here. This info is only for the admins. Time Limit: 2 days

PS: Task will be assigned on an FCFS basis.

• Delete yarn.lock
• Run yarn
• Commit the updated yarn.lock
• Create pull request

Description

As a user, I need to have uniformity in syntax (as in case of 'Skin', 'Eyes', 'Cloth' in Create New Avatar screen), so that I can have better experience of creating new avatar.

Mocks

Before


After


Acceptance Criteria

Update [Required]

• [ ] 'hair' to be changed into 'Hair' in strings.xml file to view its effect on Create New Avatar screen

Definition of Done

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

Estimation

5 minutes

• Delete yarn.lock
• Run yarn
• Commit yarn.lock
• Create pull request

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

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

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

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

diff 4 <a class="ellipsis pull-right" data-toggle="dropdown"><i class="fa fa-ellipsis-h" style="color:#666;font-size:18px;margin-right:10px;"></i></a> This needs to be replace with the following-

diff 4 <a class="ellipsis pull-right" data-toggle="dropdown" style="cursor:pointer"><i class="fa fa-ellipsis-h" style="color:#666;font-size:18px;margin-right:10px;"></i></a>

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

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!

Here is a screenshot showing that the cursor is not changed to pointer on hovering over notes card.The task is to change this cursor into pointer on hovering over the ellipsis button. 

• [ ] 📝 Update the file app/views/notes/_card.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!

Please make changes in the following line- diff 43 <a class="ellipsis bottom-right" data-toggle="dropdown">&nbsp;<i class="fa fa-ellipsis-h" style="color : #666; font-size:15px; float:right;"></i></a> ` Replace it with this line-

diff 43 <a class="ellipsis bottom-right" data-toggle="dropdown" style="cursor:pointer">&nbsp;<i class="fa fa-ellipsis-h" style="color : #666; font-size:15px; float:right;"></i></a>

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

Is your feature request related to a problem? Please describe.

R.filter doesn't expose index to the predicate function. Let's create a function that does and call it filterIndexed.

Describe the solution you'd like js filterIndexed((v, idx) => idx === 0, [1, 2, 3); // => [1] Possible implementation js const filterIndexed = R.addIndex(R.filter); Describe alternatives you've considered

--

Additional context

--

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete package-lock.json
• Run npm install
• Commit the updated package-lock.json
• Create pull request

• Delete yarn.lock
• Run yarn
• Commit the updated yarn.lock
• Create pull request

• Delete yarn.lock
• Run yarn
• Commit yarn.lock
• Create pull request

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

• [ ] 📝 Update the file app/views/tag/_profileCard.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!

In the respective lines, the function t needs to be changed to translation

diff 25<a href="/tag/<%= tag.name %>/author/<%= @profile_user.name %>"><%= t('tag.index.notes', count: Node.find_by_tag_and_author(tag.name, @profile_user.id, 'notes').count) %></a> | 26 <a href="/questions/tag/<%= tag.name %>/author/<%= @profile_user.name %>"><%= t('tag.index.questions', count: Node.find_by_tag_and_author(tag.name, @profile_user.id, 'questions').count) %></a> | 27 <a href="/profile/comments/<%= @profile_user.name %>/tag/<%= tag.name %>"><%= t('tag.index.comments', count: Comment.find_by_tag_and_author(tag.name, @profile_user.id).count) %></a> 33<a style="float: right; width: 100px;" rel="tooltip" title="<%= t('sidebar._post_button.share_your_work') %>" data-placement="bottom" href="/post?tags=<%= tag.name %>" class="btn btn-primary btn-sm">New post <i class="fa fa-plus fa-white"></i></a> 37<a style="width: 100px;" rel="tooltip" title="<%= t('tag.show.unfollow') %>" class="btn btn-light btn-sm active" href="/unsubscribe/tag/<%= tag.name %>"></i> <%= t('tag.index.unfollow') %></a> 39<a style="width: 100px;" class="btn btn-outline-secondary btn-sm index-follow-buttons follow-btn-remote" href="/subscribe/tag/<%= tag.name %>" data-remote="true"><%= t('tag.index.follow') %></a> This needs to be replaced with the following -

diff 25<a href="/tag/<%= tag.name %>/author/<%= @profile_user.name %>"><%= translation('tag.index.notes', count: Node.find_by_tag_and_author(tag.name, @profile_user.id, 'notes').count) %></a> | 26 <a href="/questions/tag/<%= tag.name %>/author/<%= @profile_user.name %>"><%= translation('tag.index.questions', count: Node.find_by_tag_and_author(tag.name, @profile_user.id, 'questions').count) %></a> | 27 <a href="/profile/comments/<%= @profile_user.name %>/tag/<%= tag.name %>"><%= translation('tag.index.comments', count: Comment.find_by_tag_and_author(tag.name, @profile_user.id).count) %></a> 33<a style="float: right; width: 100px;" rel="tooltip" title="<%= translation('sidebar._post_button.share_your_work') %>" data-placement="bottom" href="/post?tags=<%= tag.name %>" class="btn btn-primary btn-sm">New post <i class="fa fa-plus fa-white"></i></a> 37<a style="width: 100px;" rel="tooltip" title="<%= translation('tag.show.unfollow') %>" class="btn btn-light btn-sm active" href="/unsubscribe/tag/<%= tag.name %>"></i> <%= translation('tag.index.unfollow') %></a> 39<a style="width: 100px;" class="btn btn-outline-secondary btn-sm index-follow-buttons follow-btn-remote" href="/subscribe/tag/<%= tag.name %>" data-remote="true"><%= translation('tag.index.follow') %></a>

• [ ] 💾 Commit your changes

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

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

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

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

Please keep us updated

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

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

Is someone else already working on this?

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

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

🤔❓ Questions?

Leave a comment below!

1.md

• what does stream mean in this context?
• please rewrite it so that knowing how to navigate the Tweepy documentation page is less of an optional thing. It is rather important that students get well acquainted with this documentation
• also explain why it is important that they get acquainted with documentation in general
• which of the 4 pillars of OOP programming does documentation play into?

2.md

• "we are going to recreate the Twitter application, which is called Tweepy" what does that mean? as far as I am concerned, Tweepy is a tool/package we are using, not something we are creating. please clarify this
• what does installing tweepy allow us to do?

4.md

• we had only introduced the documentation in card 1 of this activity. You want to explain and go over in more detail what each of these methods that you are using is doing. Every STEP in this card should get it's OWN card in order to try our best to explain a) what the documentation is saying and b) how to use this information to write our own code
• please also explain the significance of each of these steps better. WHY are we doing what we are doing? How do these lines of code add to our eventual goal?

5.md

• why do we need a separate listener class? does the previous class we coded not enable us to view the Tweet stream we want?
• what is a basic listener class? assume student doesn't know what a listener class is
• give code snippet of constructor
• what is this StreamListener class? Is it another package? Do we need to install it? Is it provided by Twitter? Do not just name drop here, please explain the origins and uses of any names
• add comments to code snippets
• why do we need on_error?
• add encouraging message at end. There were lots of technical cards before this; we want to try to keep morale high with congratulations/almost there/we are ready to view our tweet stream messages every once in a while
• code formatting that last print statement is misaligned. we know how badly that goes in python programs

6.md

• Before step 1: what main function? where do we put the main function?
• even though variables are dynamic, please include what the variable would hold. (a list of strings, a list, a set, a dictionary)
• are there any specialities to files in python? in this case will a new file be created if it doesn't exist in the the folder? will it be overwritten everytime we run the function?
• run on terminal with what commands
• please fix code indentation

For Images

• please put the image file in the folder of the lab/activity in a folder named "images" (you have to make this folder yourself)
• please use the RELATIVE PATH of the image when you are referencing them in your lab/activity cards

Dollar signs ($'s) in Swift strings may cause problems when translated directly, since Kotlin uses them as an escape character. It may be possible to always escape them during the translation, which should fix this problem.

If this gets done, it might be possible to simplify the handling of dollar signs in AuxiliaryFileContents.swift, and maybe other files too.

1, 2, 3.md

• merge cards
• write a better intro. as in introduce Twitter API and twitter developer more off the get go. It's not very encouraging to just in by creating an account. You're not telling students why they should surrender some of their info

4, 5.md

• why do we need to create an app?
• why do we "Leave the OAuth Callback URL, TOS and Privacy Policy fields blank."? It is okay to say that it is beyond the scope of this bootcamp

6.md

• assume this is their first interaction with an API. Why, and what are the significances of API keys?
• should we keep them a secret? why or why not? (addressing why the ones in the screenshot have been erased)

For Images

• please put the image file in the folder of the lab/activity in a folder named "images" (you have to make this folder yourself)
• please use the RELATIVE PATH of the image when you are referencing them in your lab/activity cards

Hi there,

I think this can be a good issue for a first-time contributor. It would be great if we can increase documentation for the DatabaseCleaner::Configuration API: https://github.com/DatabaseCleaner/databasecleaner/blob/master/lib/databasecleaner/configuration.rb#L56-L72

Even though methods are pretty self-explanatory, I think it is a good idea to maintain a complete documentation for public methods. If you look at https://rubydoc.info/gems/database_cleaner/DatabaseCleaner/Configuration you will find some TODO comments but not much more than that.

In order to follow the standard defined by YARD, method documentation should follow this guide: https://rubydoc.info/gems/yard/file/docs/GettingStarted.md

If you think this is a good idea, we can create more issues for other classes that are poorly documented.

Best, Ernesto

3.md

• please go over what will be accomplished in the second step: hard cards are supposed to give enough directions to complete the objective of the card, without giving away many implementation details. Currently students cannot accomplish anything by simply working off the hard card. consider: Through calling what methods? (ex: by the end you should have a list of tweets)
• Include a screenshot of what the result of completing card 3 will look like.
• why do we want to remove the URLs?
• link a webpage about regular expressions

31.md

• please go over the format of what you are trying to remove (what do you want to look for)
• please give a brief introduction of regular expressions
• include instructions that we are writing a function, remove_url()

311.md

• remove ([^0-9A-Za-z \t])|(\w+:\/\/\S+) from this card.
• put it in card 3 (we want to try to let them figure it out themselves)
• include a link to one of those regular expression checker websites (introduce it too!)
• it looks like you removed more than just the URL (you removed the @ too) fix this (either explain that you are also removing these, or change the output snippet)

32.md

• append its contents to the end of 311.md and delete this card.

33.md

• how does card 333.md play into this?
• what exactly does "our data list to be unique" mean?

331.md

• why is it important that we turn everything to lower case?

332.md

• why do we use a set?

333.md

• unclear what is going on. rewrite.

For all Easy and Medium cards

• please split the easy and medium cards into steps. these look like Step 1: title of the step
• each medium and easy card has its own set of steps that start from 1. THEY DO NOT CONTINUE ON ANOTHER CARD

For Images

• please put the image file in the folder of the lab/activity in a folder named "images" (you have to make this folder yourself)
• please use the RELATIVE PATH of the image when you are referencing them in your lab/activity cards

2.md

• please go over what will be accomplished in the second step: hard cards are supposed to give enough directions to complete the objective of the card, without giving away many implementation details. Currently students cannot accomplish anything by simply working off the hard card. consider: Through calling what methods? (ex: by the end you should have a list of tweets)
• Include a screenshot of what the result of completing card 2 will look like

21.md

• why is this method called like so: -filter? Why can we not use the dot operator like with the other function we have encountered?
• go over the query string formatting. #climate+change <-- what does the + mean? please also go over other acceptable formats
• why are we creating the variable search_term? mention that we will use this later.

22.md

• through using what methods? THESE ARE HINTS. It is possible to complete a lab solely off of medium and easy cards. Medium cards give more implementation details than hard cards, but do not have any code snippets. They should still have an objective that should be completed by the end of this hint

221.md

• give a more in depth breakdown of what each argument means. At this point, the official twitter documentation was not enough if they need to use the easy card. So please explain things in a more comprehensive, but CUSTOMIZABLE way

222.md

• what is a list comprehension? why is it useful
• please be more explicit about what the final code snippet means. Are you running all_tweets[:5] in IDLE? are you printing it from main()? (if it's the former, please mimic the format with >>>)

For all Easy and Medium cards

• please split the easy and medium cards into steps. these look like Step 1: title of the step
• each medium and easy card has its own set of steps that start from 1. THEY DO NOT CONTINUE ON ANOTHER CARD

For Images

• please put the image file in the folder of the lab/activity in a folder named "images" (you have to make this folder yourself)
• please use the RELATIVE PATH of the image when you are referencing them in your lab/activity cards

Instead of sending static images, send cool animations like this one: https://commentpicker.com/flip-a-coin.php Only for first-time contributors in this repo.

Refer the xkcd module and add a similar option to flip the coin again: https://github.com/the-vision/jarvis-telegram/blob/master/modules.py#L11 Only for first-time contributors in this repo.