What would you like?

js cy.tick(2000, { log: false }); Currently there is no log option on tick, as I had expected while working on customizing my log. Was wondering if it was an oversight or on purpose?

Why is this needed?

To align with the feature set surrounding allowing you to customize your log, most commands support this option so I was expecting this one to have it too, and would be nice to silence this one in a specific custom command I'm building though I'll of course live without it

Current Behavior 1. The new source and deployment target locations need updating in the contributor guide. See https://github.com/layer5io/layer5/blob/9e24d81e0e4883ab3413bc3cf79f2e639c198349/.github/workflows/gatsby.yml#L18-L19 for details.

1. The Chore/Task Issue template needs updated to remove layer5-ng reference.

Desired Situation - No references to layer5-ng should remain.

Contributor Resources

The layer5.io website uses Gatsby, Strapi, and GitHub Pages. Site content is found under the layer5-ng branch. - See layer5-ng contributing instructions

Current State: Each of the bulleted lists here are not sorted.

Desired State: Ideally, each list is alphabetically sorted.

Contributor Resources - Meshery documentation site - Meshery documentation source - Instructions for contributing to documentation

Current Behavior @navendu-pottekkat recently gave an introduction and walkthrough on what mesheryctl is and how it fits on the Meshery project. It is on YouTube. https://www.youtube.com/watch?v=hh_kFLZx3G4

Desired Behavior This tutorial should be added to the /community/newcomers table of recordings

Contributor Resources The layer5 repo contains two websites. The current generation and the next-generation of the layer5.io site.

If the layer5-ng label is absent on this issue, then this issue pertains to the current generation of the layer5.io website, which uses Jekyll and GitHub Pages. Site content is found under the master branch. - See layer5 contributing instructions

If the layer5-ng label is present on this issue, then this issue pertains to the next-generation of the layer5.io website, which uses Gatsby, Strapi, and GitHub Pages. Site content is found under the layer5-ng branch. - See layer5-ng contributing instructions - See Layer5 site designs in this Figma project.

Add rclone

We want to add rclone because it's a nice cross-platform alternative to rsync that can do most of the same things, plus many more, and is more performant for local copies (at least in my testing).

This could be as simple as copying _example, updating the github releases info, and doing a find and replace on a few file system path names.

How to create a webi installer


Skills required

• Basic Command Line knowledge (mkdir, mv, ls, tar, unzip, variables)

Steps

1. Clone and setup the webi packages repo bash git clone git@github.com:webinstall/packages.git pushd packages/ npm install
2. Copy the example template and update with info from Official Releases: https://github.com/___CHANGE/ME___/releases bash rsync -av _example/ CHANGE-ME/
   • [ ] update CHANGE-ME/release.js to use the official repo
   • [ ] Learn how CHANGE-ME unpacks (i.e. as a single file? as a .tar.gz? as a .tar.gz with a folder named CHANGE-ME?)
   • [ ] find and replace to change the name
     • [ ] update CHANGE-ME/install.sh (see bat and jq as examples)
     • [ ] update CHANGE-ME/install.ps1 (see bat and jq as examples)
3. Needs an updated tagline and cheat sheet
   • [ ] update CHANGE-ME/README.md
     • [ ] official URL
     • [ ] tagline
     • [ ] Switch versions
     • [ ] description / summary
     • [ ] General pointers on usage (and perhaps "gotchas")

It's also okay to have multiple people work on part of this (i.e. the Cheat Sheet can be done independently from the install.sh)

Cheat sheet Ideas

Copy files locally, ignoring common caches, and copying efficiently

bash rclone sync -vP --transfers=1 --order-by name --check-first --exclude 'node_modules/**' --exclude '.Spotlight-*/**' --exclude '.cache*/**' ~/ /Volumes/Backup/

(This issue is in continuation of #7683 )

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] @antorobo - https://github.com/publiclab/plots2/issues/8508
• [ ] @harshdhonchak

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

Describe the bug At the moment, not all widgets can be set with a font in Windows, even though the font setting implementation is quite easy. For example, toga.Selection widget can not be set with fonts at the moment.

This raised a flag that maybe we should reconsider how to implement font settings in all of our platforms. See conversation in PR #1177

Environment: - Operating System: Windows - Python version: 3.8.7 - Toga: latest

add comments make codes more descriptive add spaces

Hi! I am pursuing my Bachelor's degree in Software Engineering and am looking for a project to contribute to so that I can learn new things and improve my skills.

My education mainly focused on full-stack web development. I also know Java and C++.

Hi my name is Shoaib Kamal Khan and I am a recent Front End Web Development Techdegree graduate from Treehouse. I would love to contribute to any open issues you have as a first timer. Please let me know if you have any issues that I can work on. I am proficient in the following:

HTML, CSS, JavaScript Mobile-First Responsive Web Design Flexbox Grid Layout jQuery Ajax Fetch API JSON Sass Media Element.js Bootstrap SEO(Search Engine Optimization) Semantic HTML Front End Optimization Git Wireframing and Prototyping Adobe XD Sketch Figma Graphic Design Adobe Illustrator Adobe Photoshop(PSD to HTML)

Here is the link to my portfolio:

https://shoaibkamalkhan.github.io/

as we all know, patterns are an effective way to build concept of loops please add more patterns to the readme file

we all have printed patters during learning coding, here are some more complicated and challenging patterns to deal with.

With the WebDriver protocol Chrome flags don't need to be prefixed with --. With DevTools this won't work and will result in Chrome opening a tab for every flag used, e.g.


Let's make this consistent and ensure that in DevTools all args are prefixed with -- when launching the browser.

What language do you want to program in and state your idea. What operating system and package manager do you use?

After updating @wdio/allure-reporter to version 6.8.1, test retries are no longer shown properly in the allure report. This is also the case with the latest version of allure-reporter (v6.10.6).

Expected behaviour - version 6.7.2:

The "retries" tab shows the retries and clicking on a specific retry shows the steps, screenshots, and errors from the first try. 

Actual behaviour - version 6.8.1 & 6.10.6

Logging info from the first test run is shown on the main page of the test. The retries tab is empty. 

Analyses

The problem seems the be, that the XML output in allure-results changed. When comparing the output from version 6.7.2 and 6.8.1/6.10.6, the newer versions only output one <test-case> tag including both, the information from the first and the second run, where as there are two separate <test-case> tags for both runs using version 6.7.2.

v6.7.2 xml <?xml version='1.0'?> <ns2:test-suite xmlns:ns2='urn:model.allure.qatools.yandex.ru' start='1609754094280' stop='1609754096429'> <name>Failure tests</name> <title>Failure tests</title> <test-cases> <test-case start='1609754094281' status='undefined'> <name>test should not fail with retries enabled</name> <title>test should not fail with retries enabled</title> <labels> <label name='language' value='javascript'/> <label name='framework' value='wdio'/> <label name='thread' value='0-6'/> </labels> <parameters> <parameter kind='argument' name='browser' value='chrome-83.0.4103.61'/> <parameter kind='environment-variable' name='QA Environment:' value='qa01'/> </parameters> <steps/> <attachments> <attachment title='Info:' source='94cc5ed4-7ae9-439b-ac0e-e2e8883cdf09-attachment.txt' type='text/plain' size='74'/> <attachment title='Screenshot' source='283a0afe-302d-42e7-a504-969d1b7bad0d-attachment.png' type='image/png' size='57911'/> <attachment title='Failure URL' source='d4f09549-192c-493b-b065-5de8679482f3-attachment.txt' type='text/plain' size='23'/> </attachments> </test-case> <test-case start='1609754095793' status='passed' stop='1609754096272'> <name>test should not fail with retries enabled</name> <title>test should not fail with retries enabled</title> <labels> <label name='language' value='javascript'/> <label name='framework' value='wdio'/> <label name='thread' value='0-6'/> </labels> <parameters> <parameter kind='argument' name='browser' value='chrome-83.0.4103.61'/> <parameter kind='environment-variable' name='QA Environment:' value='qa01'/> <parameter kind='environment-variable' name='Parallel Instances' value='7'/> <parameter kind='environment-variable' name='Device:' value='desktop'/> <parameter kind='environment-variable' name='Headless:' value='true'/> <parameter kind='environment-variable' name='Run tests:' value='all'/> </parameters> <steps/> <attachments> <attachment title='Info:' source='76a4e730-89ff-422f-9dbf-53a1e5bcf8aa-attachment.txt' type='text/plain' size='74'/> </attachments> </test-case> </test-cases> </ns2:test-suite>

v6.8.1 xml <?xml version='1.0'?> <ns2:test-suite xmlns:ns2='urn:model.allure.qatools.yandex.ru' start='1609755277661' stop='1609755279863'> <name>Failure tests</name> <title>Failure tests</title> <test-cases> <test-case start='1609755277661' status='passed' stop='1609755279693'> <name>test should not fail with retries enabled</name> <title>test should not fail with retries enabled</title> <labels> <label name='language' value='javascript'/> <label name='framework' value='wdio'/> <label name='thread' value='0-6'/> <label name='language' value='javascript'/> <label name='framework' value='wdio'/> <label name='thread' value='0-6'/> </labels> <parameters> <parameter kind='argument' name='browser' value='chrome-83.0.4103.61'/> <parameter kind='environment-variable' name='QA Environment:' value='qa01'/> <parameter kind='argument' name='browser' value='chrome-83.0.4103.61'/> <parameter kind='environment-variable' name='QA Environment:' value='qa01'/> </parameters> <steps/> <attachments> <attachment title='Info:' source='1bc524c4-b1b7-40c2-b166-7a31392b9800-attachment.txt' type='text/plain' size='74'/> <attachment title='Screenshot' source='56b37694-c44e-497a-83cf-97c9d577083c-attachment.png' type='image/png' size='57911'/> <attachment title='Failure URL' source='aca7987a-ee8e-430c-bec4-32cd0cf4a776-attachment.txt' type='text/plain' size='23'/> <attachment title='Info:' source='cd3109cb-e337-4490-ab9a-c4411ed22ae9-attachment.txt' type='text/plain' size='74'/> </attachments> </test-case> </test-cases> </ns2:test-suite>

Environment

• All other npm packages are up to date:
  • WebdriverIO v6.10.11/6.10.13
  • allure-commandline v2.13.8

Would be great to get this fixed. Being abled to properly inspect retries is very important when fighting unstable tests.

Hi! I'm Syl. A recent Front End Web Dev graduate. I'm always looking for new ways to learn, and I'd love to work on an issue :) Thanks!

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

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

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

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

🤔 What you will need to know.

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

📋 Step by Step

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

• [ ] 📝 Update the file app/views/map/index.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 @@ -31,7 +31,7 @@ var baselayer = L.tileLayer('https://api.mapbox.com/styles/v1/jywarren/ckj06ujnc1nmi19nuelh46pr9/tiles/{z}/{x}/{y}?access_token=pk.eyJ1Ijoianl3YXJyZW4iLCJhIjoiVzVZcGg3NCJ9.BJ6ArUPuTs1JT9Ssu3K8ig', { tileSize: 512, zoomOffset: -1, - attribution: '© Mapbox © OpenStreetMap' + attribution: '© Mapbox © OpenStreetMap' }).addTo(map) ; map.options.minZoom = 1.5 ;

```

• [ ] 💾 Commit your changes

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

• If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

1. 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!

Is your feature request related to a problem? Please describe. This is not a problem. I want people to add projects to this repo.

Describe the solution you'd like Come up a small project idea for a language for us and others to contribute.

Describe alternatives you've considered Current Contributors add to the project but they are working on documentation.

Additional context I will teach you how to create a branch and a project for you. Say hi and I will create an issue for you.

Is your feature request related to a problem? Please describe. This is not a problem, I just needed person to be my documentation maintainer.

Describe the solution you'd like A person who has never contributed to a project to write readme files.

Describe alternatives you've considered Have a person who has contributed to write the readmes.

Additional context This is a first-timer-only issue. The owner will teach Markdown and how to fork, committing, and have a pull request to this repository. Say hello then a new issue will be created.

See https://github.com/brave/brave-browser/releases

The generic instructions for how to add a new installer to Webi are here: https://github.com/webinstall/webi-installers/issues/130

On Mac this would be more similar to the iTerm2 installer in that it will go into ~/Applications: https://github.com/webinstall/webi-installers/tree/master/iterm2

What would you like?

As discussed here cypress checks for the sever running at baseUrl. If this check fails it exits. The number of retries is not configurable, nor can the check be bypassed.

• An option to suppress this check (nice to have -- ability to change it a "warning")
• An option to configure the number of retries (nice to have -- retry-until-success).
  

Why is this needed?

• So that other mechanisms for ensuring that the server is already running during test are not superseded by this non-optional check.

• Avoid introducing dependencies on, e.g. wait-on, start-server-and-test

A number of EddieBot features have got super long recently, so this could be split off to other things (Create issues!)

There is quite a lot of space used when the bio command is used and this may fill entire screens (think iPad, small screen laptops with less than 800px height

Proposed use of embed inlining:

or

There's an improvement available here (ideal for first-timers with Promise)

https://github.com/EddieJaoudeCommunity/EddieBot/blob/develop/src/commandHandlers/tips/opensource.ts

```ts /** * Set the given embed message with a curated list of tips and resources that help members of the community to * contribute to open-source software (OSS). */ export const createTip = async (embed: MessageEmbed) => { const tips = await Promise.all( config.TIPS.tips.map((file) => readMarkdown(file)) ); const resources = await Promise.all( config.TIPS.resources.map((file) => readMarkdown(file)) );

tips.forEach((tip) => embed.addField('Tips :bulb:', tip)); resources.forEach((resource) => embed.addField('Links and Resources :link:', resource) ); ```

It is possible to do something like:

ts // Use ES6 deconstructing. // This is actually totally untested and might not actually work, however Promise.all() can work in harmony. const { tips, resources } = await Promise.all([ config.TIPS.tips.map((file) => readMarkdown(file)), config.TIPS.resources.map((file) => readMarkdown(file)) ]);

Describe the bug Can't do >> 'briefcase create' ..

Hi Guys! When I try to 'briefcase create' command, I've got - [helloworld] Installing support package... Using support package https://briefcase-support.org/python? platform=linux&version=3.6&arch=i686 ... using most recent revision Unable to download https://briefcase-support.org/python? platform=linux&version=3.6&arch=i686; is the URL correct?

Environment: - Operating System: linux mint/xfce(same ubuntu 18.10, but better..)) - Python version: python 3.6.9 - Software versions: ThinkPad R60(Yeah, it's alive!)) - Briefcase: 0.3.3 - Toga: toga-core==0.3.0.dev25 toga-gtk==0.3.0.dev25 - ...

Additional context Hey Guys!) I love your tech, also like one of my old ThinkPad 32 bit, would be appreciated for possibility create apps on 32 bit soft. too, thanks..)

DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead

def makesubprocess_transport(self, protocol, args, shell,

DeprecationWarning: Gtk.Window.set_wmclass is deprecated

self.native.setwmclass(app.interface.name, app.interface.name) [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: Widget.set_hidden()

DeprecationWarning: Gtk.Misc.set_alignment is deprecated

self.native.setalignment(*gtkalignment(value)) [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setalignment() [GTK+] Not implemented: TextInput.clearerror() [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setfont() [GTK+] Not implemented: TextInput.setalignment() [GTK+] Not implemented: TextInput.clearerror() [GTK+] Not implemented: Widget.sethidden() [GTK+] Not implemented: Button.setbackground_color()

Describe the bug Adding a non-existing or no longer existing blog silently fails without error message or the like.

To Reproduce Steps to reproduce the behavior: 1. Enter a no longer existing blog address in the url field (e.g. urmeimu.tumblr.com) 2. Click on 'Add Blog' 3. Nothing visible happens

Expected behavior At least a message should be shown, some error label, a log entry or the like.

Desktop (please complete the following information): - TumblThree version: 1.0.11.13 - OS: Windows 10 - Browser: Chrome - Version [e.g. 22]

Additional context

At present, PySide2 and PPB appear in Briefcase's new project wizard. However, Briefcase can't deploy PySide2 or PPB to Android or iOS, as those toolkits don't support Android or iOS. This has caused repeated confusion by users who try to deploy PySide2 apps to mobile, and get confusing errors (e.g., #536, #537).

We should add a mechanism that warns users when the platform they've chosen can't be deployed to mobile.

Describe the solution you'd like

1) The new project wizard should advise on platform compatibility of GUI toolkits. 2) We should add a platform verification step for iOS/Android that confirms if the GUI toolkit in use is compatible with those platforms. This could be done with a metadata attribute in pyproject.toml that annotates unsupported platforms. For example, the PySide template could generate:

[tool.briefcase.app.foobar.iOS] supported = False

If the platform isn't supported, validation would fail during briefcase create iOS with an appropriate error message.

Browser Name and website

Brave

Version

1.16.75 Chromium: 86.0.4240.193 (Official Build) (64-bit)

Operating System used

Linux (Pop!_OS 20.10)

Operating Systems supported

Linux, Windows, OS X

Notes

I have tested this on mobile and on Desktop. It is able to track me on my phone (iPhone 6, iOS 12), though not on my laptop. There is an issue which shows that it is unable to track on Brave with Tor enabled, I want to note that this is with default private browsing, not Tor.

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 test/integration/loginflowtest.rb 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 @@ -64,6 +64,16 @@ class LoginFlowTest < ActionDispatch::IntegrationTest assert_equal '/questions', path end

• test 'should redirect to dashboard when logging in from /login' do
• get '/login'
• assert_response :success +
• post '/usersessions', params: { returnto: request.path, user_session: { username: users(:jeff).username, password: 'secretive' } } +
• follow_redirect!
• assert_equal '/dashboard', path

• end + test 'google login routing' do assertrouting '/auth/googleoauth2/callback', {controller: 'usersessions', action: 'create',provider: 'googleoauth2'} end ```

• [ ] 💾 Commit your changes

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

• If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

1. 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!

Describe the bug This tumblr used to work a few months ago: https://protobacillus.tumblr.com/ But now it fails.

To Reproduce Steps to reproduce the behavior: 1. Add https://protobacillus.tumblr.com/ 2. Try to Crawl. 3. Nothing happens.

Expected behavior It should start downloading.

Desktop (please complete the following information): - TumblThree version: 1.0.11.12 - OS: Windows 10 - Browser: Chrome - Version [e.g. 22]

Additional context Alternative URL: https://www.protobacillus.com/ Also doesn't work anymore.

Reverts Xcov19/mycovidconnect#132

This change is  <!-- Reviewable:end -->

Describe the bug/problem Often times when a blog (with the option "dump crawler data") is crawled a few files inside the blog's folder have a new time stamp even if the blog hasn't had any post for a while.

To Reproduce Steps to reproduce the behavior: 1. Enable "Dump crawler data" for some blogs and crawl them completely once 2. Inspect the files in the blog's folder 3. Crawl one or more of the above blogs again 4. Check the json files in blog folders

Expected behavior For old blogs which don't have a new post the crawler should not have to update any files after one complete crawl, because there is nothing to download and even the crawler dump data (the post data) itself shouldn't change unless you enable the "Force rescan" option.

Desktop (please complete the following information): - TumblThree version: 1.0.11.12 - OS: Win 10

Does anyone know what is going wrong in the code? Do you know how to solve it?

[//]: # NOTE: This repository only maintains packages that are listed in the Readme. Please make sure that your issue is directly caused by one of these packages and if not file an issue in the correct 3rd party package repository.

Environment (please complete the following information): - WebdriverIO version: 6.7.2 - Mode: Standalone (not really sure) - Node.js version: 10.16.3 - NPM version: 6.9.0 - Browser name and version: not relevant - Platform name and version: Fedora Linux 29 - Additional wdio packages used (if applicable): @wdio/sauce-service

Config of WebdriverIO Relevant saucelabs configuration values: user: 'xxx', key: 'xxx-xx-xxx', region: 'eu', sauceConnect: false,

global-agent is configured as per https://webdriver.io/docs/proxy.html running the tests using: GLOBAL_AGENT_HTTP_PROXY=http://corporate-proxy:8080 wdio wdio.conf.js

Describe the bug The tests connect remotely to saucelabs using an URL like: https://user:pass@ondemand.eu-central-1.saucelabs.com:443/wd/hub. Our company network is behind a http-only proxy, so the https request needs to be tunneled through the proxy. This does not work, the tests fail with the following error message:

``` [1-0] 2020-11-06T11:29:56.864Z ERROR webdriver: RequestError: write EPROTO 140336396121920:error:1408F10B:SSL routines:ssl3getrecord:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

at ClientRequest.request.once (/home/xxx/node_modules/webdriver/node_modules/got/dist/source/core/index.js:953:111)
at Object.onceWrapper (events.js:286:20)
at ClientRequest.emit (events.js:203:15)
at ClientRequest.EventEmitter.emit (domain.js:448:20)
at ClientRequest.origin.emit.args (/home/xxx/node_modules/@szmarczak/http-timer/dist/source/index.js:39:20)
at TLSSocket.socketErrorListener (_http_client.js:392:9)
at TLSSocket.emit (events.js:203:15)
at TLSSocket.EventEmitter.emit (domain.js:448:20)
at errorOrDestroy (internal/streams/destroy.js:107:12)
at onwriteError (_stream_writable.js:436:5)
at WriteWrap.afterWrite (net.js:788:14)

[1-0] 2020-11-06T11:29:56.864Z ERROR @wdio/runner: Error: Failed to create session. write EPROTO 140336396121920:error:1408F10B:SSL routines:ssl3getrecord:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

at Object.startWebDriverSession (/home/xxx/node_modules/webdriver/build/utils.js:35:15)
at process._tickCallback (internal/process/next_tick.js:68:7)

[1-0] Error: Failed to create session. write EPROTO 140336396121920:error:1408F10B:SSL routines:ssl3getrecord:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332: ```

Additional context Running the tests outside the corporate network, without a proxy setting, works correctly. I am not sure which package is causing this error, I've spent the last 3 days tring to understand which of wdio/sauce-service, webdriver, got, global-agent does not handle this situation properly, but I could not.

Please use the correct markdown

Build Sequence

By Id

• [x] Id exists
• [ ] Id does not exist

By Tower Id

• [ ] Tower Id does not exists
• [ ] Tower Id exists but is not level 4 tower
• [x] Tower Id exists and is a level 4 tower

By Tower Name

• [ ] Tower name does not exists
• [ ] Tower name exists but is not level 4 tower
• [x] Tower name exists and is a level 4 tower

(Verbose)Towers By Id

• [ ] does not exist
• [ ] exists, not level 4, barracks
• [x] exists, not level 4, not barracks
• [ ] exists, level 4, barracks
• [ ] exists, level4, not barracks

Describe the bug The sidebar headers are centered, while the content of each category is left-aligned. This results in a pretty weird layout:


I think left-aligning the headers would make the layout feel a lot less disjointed and easier to scan.

OS - [x] Linux (Fedora 33)

Version Version of Gaphor: 2.0.1 from Flathub

The descriptions of the tower abilities are a mess, and it needs your help! The description for each ability of each tower could be greatly improved. You can checkout Kingdom Rush TD fandom for ideas to make it better, it contains more information about each ability.

Please checkout the Good First Issue document

https://github.com/mithi/kingdom-rush-graphql/blob/main/docs/GOODFIRSTISSUE.md

Files to update

The current description of each ability can be found in these yaml files - https://github.com/mithi/kingdom-rush-graphql/blob/main/data/raw/KR/abilities.yml - https://github.com/mithi/kingdom-rush-graphql/blob/main/data/raw/KRF/abilities.yml - https://github.com/mithi/kingdom-rush-graphql/blob/main/data/raw/KRO/abilities.yml - https://github.com/mithi/kingdom-rush-graphql/blob/main/data/raw/KRV/abilities/abilities.yml

Currently when people wrap their code with ask {} when using the command line CLI tool, they get the following error:

``` marcin@Marcins-MacBook-Pro-2 askql % npm run cli

askql@1.2.2 cli /Users/marcin/Repositories/askql node dist/cli.js

Welcome to AskQL CLI!

For multi-line mode please type: .editor 🦄 ask {} Uncaught: Error [SyntaxError]: Expected " ", "(", ".", "//", ":", ";", "=", "[", "\n", "\r", "\t", "}", [/], or [-!<>+*^%=&|] but "{" found. Location: { "start": { "offset": 10, "line": 2, "column": 5 }, "end": { "offset": 11, "line": 2, "column": 6 } } 🦄 ```

Then command line should allow wrapping code in ask {} and not show this confusing error.

When I run rubocop -a app/controllers/notes_controller.rb or rubocop -a <any other file> I receive a series of errors from that show that the .rubocop_shopify_styleguide.yml has obsolete configurations.

Should it be updated?


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 rubocopshopifystyleguide.yml in the PLOT2 repository (press the little pen Icon) and update any errors that show that rubocop_shopify_styleguide.yml contains deprecated lines of configuration.

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

• [ ] 💾 Commit your changes

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

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

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

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

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 will be a running issue to let people know how to add events to `historicalevents.py`_

NOTE: this issue is only for you if you'd consider yourself a Code Newbie.

Have you seen a typo you'd like to fix? Go ahead and fix it.

Need help? Check out this article on using the github website to navigate git or use this repo as an example to use the command line. You're also welcome to comment on this issue and I'll be happy to help.

Proposed workflow:

1. Fork this repo
2. Find the file with spelling errors and fix them.
3. Once you are done and checked for typos, commit it & push your work to your fork
4. Submit a PR against this repo

Someone will look it over and, if deemed appropriate, will merge your PR.

Thanks for contributing!

Don't forget to follow the bot on Twitter to see the hard work you put in.

Add a new company to already existing list of companies, by adding following details:

• website of company
• start year
• remote jobs (Yes/No)
• degree required(Yes/No)

A friendly guide to create a pull request:

1. Star this repository (you must be logged on to your GitHub account, duh!)
2. Fork this repository
3. To add a company you need to modify the following files:
   • the main file (List.md) (add a company in ascending alphabetic order)
   • company file (company_name.md) in the list directory
4. This can be done in either of the two ways:
   • Method 1: clone the repo locally on your PC
   • Method 2: or make changes online on GitHub

Method 1:

This is the not-so beginner friendly way (or hard way, to say the least). But you got to do it if you really want to learn Git. Follow this guide.

Method 2:

This is the easy-peasy way. You just: * create a new file with the company's name(suffixed by .md) and all the following details * company website * company's career page * start year * remote work * no degree required * any other detail you find relevant * modify the List.md to add the company's name to the original list with few more details

P.S:

Try combining multiple companies into a single pull request, instead of creating separate pull for every company.

After your PR has been successfully merged with the main branch, you will be automatically added to our Contributors list!!! (if, for whatever reason you find yourself missing from the contributors list, let us know and we'll be more than happy to add you.)

Add a configuration.rst to sphinx_source. Write how config is handled in Shopyo.

Currently when a user leaves the application the UI just freezes for the person and does not remove the placeholder for the client.

Requirements 1.) The other clients should know that the User has left by receiving an event 2.)The UI should also reflect the left client.

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/models/answer.rb 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 @@ -1,35 +0,0 @@ -class Answer < ApplicationRecord - include CommentsShared - include NodeShared

- extend RawStats

• belongsto :node, foreignkey: 'nid'
• belongsto :user, foreignkey: 'uid'
• hasmany :answerselections, foreign_key: 'aid'

- hasmany :comments, foreignkey: 'aid', dependent: :destroy

- validates :content, presence: true

• scope :pastweek, -> { where("createdat > ?", (Time.now - 7.days)) }

- scope :pastmonth, -> { where("createdat > ?", (Time.now - 1.months)) }

• def body
• finder = content.gsub(Callouts.constget(:FINDER), Callouts.constget(:PRETTYLINKMD))
• finder = finder.gsub(Callouts.constget(:HASHTAGNUMBER), Callouts.constget(:NODELINKMD))
• finder.gsub(Callouts.constget(:HASHTAG), Callouts.constget(:HASHLINKMD))

- end

• def body_markdown
• RDiscount.new(body, :autolink).to_html

- end

• # users who like this answer
• def likers
• answer_selections
• .joins(:user)
• .references(:rusers)
• .where(liking: true)
• .where('rusers.status': 1)
• .collect(&:user)

• end -end ```

• [ ] 💾 Commit your changes

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

• If you are not familiar with GitHub or the pull request model, here is a guide you can follow on how GitHub works.

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

1. 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!

Acceptance Criteria

The Select demo viewed on sui-studio is not following the agreements. It can be previewed on the following link: sui-studio Select DEMO

Definition Of DONE

• [ ] in English
• [ ] Sort by
  • [ ] Size
  • [ ] Styles
  • [ ] Options

Jira Task

SUIC-321

Develop a simple registration/login portal front end. You can refer to the repository for more. You can choose any language or framework for front-end

Is your feature request related to a problem? Please describe. We have various github actions to check for integrity, ci and lint checks. What's missing is thorough unit test coverage which tests code logic.

Features like #106 must be testable.

Describe the solution you'd like Add jest testing framework;

See; https://jestjs.io/docs/en/getting-started.html ; In the deps in package.json add ONLY latest versions "dependencies": { "babel-core" "babel-jest" "babel-preset-env" "jest" }

Add presents like: ```javascript

// babel.config.js module.exports = { presets: [ ['@babel/preset-env', {targets: {node: 'current'}}], + '@babel/preset-typescript', ], }; ```

Make sure to follow our README guide and see how to run tsc runner once you have set this up;

Describe alternatives you've considered alternatives considered were karma, jasmine. but jest has a good OSS backing as well and looks easy to use.

Additional context We need to make sure developer productivity is not hindered while adopting a new test framework.

Hi,

We have already written amazing documentation on how to connect the 2 projects here , however it requires us to do yarn install --force in plots2 every time we do change in PL.editor.

Let's use yarn link instead and make it seamless 😄

Resources: https://classic.yarnpkg.com/en/docs/cli/link/

Current behavior

Aliases are not Typescript friendly. When using aliases to share values between hooks/tests, the alias value is automatically typed as any because TS has no way of following the chained .as method through to its new value on this. This results in needing to revert to using the let method to share context if one wants TS to keep track of the variables.

Desired behavior

I think there are a few different options here. Ideally, it would be great if the alias method, .as, could determine the type of the passed in value and somehow let TS know that this property now exists on this. I'm not sure how one would do that, so if that is not possible then I think we might need a way of passing a variable to .as that is used instead of this and gives us more control over its type. As a final option, if Cypress could expose or make typeable (maybe as a type param for describe?) this, then we could just append our custom variables manually.

All that said, I'm very open to suggestions for other ways of approaching making Aliases TS friendly.

There are two ways labels are handled in the platform, depending on the markup of the form:

<label for="username">Username</label> <input id="username" type="text" /> and

<label>Username <input id="username" type="text" /> </label>

Go through the following forms and make sure the element is either using the for-attribute to associate the form-control or is encapsulating the form-control like the second example:

Categories The code is found here:

https://github.com/ushahidi/platform-client/blob/develop/app/settings/categories/categories-edit.html

You find the view by logging in as an admin, then click on Settings and select "Categories", then click the "+" icon:

Data export The code is found here: https://github.com/ushahidi/platform-client/blob/develop/app/settings/data-export/data-export.html

You find the view by logging in as an admin, then click on Settings and select "Export and tag data". Then click on "Select fields".

Users The code is found here: https://github.com/ushahidi/platform-client/blob/develop/app/settings/users/users-edit.html

You find the view by logging in as an admin, click on Settings and select "Users", then click the "+" icon.

If no adjustments is needed, just comment in this issue that you have worked through the issues and checked, if any adjustment is needed, make the necessary changes and create a PR 🎉 If changes are needed, make sure the form still looks the same as before and that is has no effect on the visual appearance of the form.

Aha! Link: https://ushahiditeam.aha.io/features/PROD-840

Create a pull request template an example can be found at https://github.com/americanexpress/one-app/blob/main/.github/pullrequesttemplate.md

This tutorial can be followed

https://docs.github.com/en/free-pro-team@latest/github/building-a-strong-community/creating-a-pull-request-template-for-your-repository

Add the following check list in the PR template:

• [ ] Created a folder with the name of language you code inside directory for the day you are making the contribution to
• [ ] Added your Codes
• [ ] Tested your codes
• [ ] Added credits (author and date) at the top of the code
• [ ] Updated README.md of the day you are contributing to
• [ ] Added yourself as a contributor using all-conributors-cli

The idea and requirements for this project will be finalized soon,

Till then we can go on with some generic contribution guideline template,

This should be an easy issue, feel free to take this and raise the PR

Example! 

Addition to this in readme.md! 

See the list of sources documented at https://github.com/gautamkrishnar/blog-post-workflow#popular-sources

Add more RSS Feed sources to the list.

Im a CSS newbie, if you see any better styling, feel free to help..

Following the https://github.com/bancodobrasil/stop-analyzing-api/issues/16#issuecomment-667519483 spec, this issue is about enchancing the db and the /choice endpoint of the mocking server so it can return different values with sequentials invocations to emulate how the real API will behave so we can work on the progress visual interaction and the final interaction when the user reaches "the end of the line".

Add a useEffect to the useChoiceBoardModel.ts that fetches the initial choices from an endpoint and set the initial options from that.

Tip: this endpoint could be the mock server endpoint

This change is  <!-- Reviewable:end -->

What to do

Which is that algorithm that you find intriguing? Edit the README.md file, by adding the algorithm's name as a heading and then add a brief description of it. Keep the description as unique as possible and avoid repetitions.

New to markdown?

See GitHub Markdown Guide

This issue is open for all

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

• Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree!
• Create a Pull Request between October 1-31 of 2020 to count towards your 4 PRs
• See Contributing Guidelines
• See https://hacktoberfest.digitalocean.com for more details

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

• Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree!
• Create a Pull Request between October 1-31 of 2020 to count towards your 4 PRs
• See Contributing Guidelines
• See https://hacktoberfest.digitalocean.com for more details

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

• Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree!
• Create a Pull Request between October 1-31 of 2020 to count towards your 4 PRs
• See Contributing Guidelines
• See https://hacktoberfest.digitalocean.com for more details

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

• Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree!
• Create a Pull Request between October 1-31 of 2020 to count towards your 4 PRs
• See Contributing Guidelines
• See https://hacktoberfest.digitalocean.com for more details

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

Welcome to Hacktoberfest

..and welcome to our community! So many fun things to get into this Hacktoberfest like adding translations for your native written language 🌏 , sharpening & sharing your python skills 🐍 or even helping foster our community 📸 by creating instastories or managing our communication channels ❤️!

Stay in the know New issues are added every day with varying difficulty levels for varying skillsets. Get notified of updates by clicking the 👁‍🗨 watch button and save the repo for later reference by clicking the ⭐️ star button at the top right corner of this repo!

Ways to get involved

Legesher is a growing project with many different ways to get involved. Below is a list of all of the repositories that are participating in Hacktoberfest. You can search by label to find issues that are in the area of your expertise or an area you're wanting to learn / grow in!

| Project | Purpose | |---------|---------| | tree-sitter-legesher-python | Tree-sitter python grammar used by text editors allowing Legesher's languages to be implemented | | language-legesher-python | Atom's programming language binding to allow syntax highlighting, code folding etc. to a specific grammar | | legesher-translations | Host and API of all the language translations for written languages for code keywords / concepts | | legesher-dot-io | Legesher's public website | | legesher-pride | Community-focused initiatives to add more value (and members) to our pride | | legesher-docs | Legesher's documentation hub. Will be transitioning to a documentation host soon. | | legesher | Git integration to collaborate with code and others in other languages |

Important Hacktoberfest Information

• Be sure to sign up at https://hacktoberfest.digitalocean.com so you can qualify to pick a limited edition t-shirt 👚 or plant a tree!
• Create a Pull Request between October 1-31 of 2020 to count towards your 4 PRs
• See Contributing Guidelines
• See https://hacktoberfest.digitalocean.com for more details

🎁 If you contribute to a Legesher repository, then you will receive a handwritten letter from our founder expressing her deepest gratitude. You might also find some special edition stickers 👀.

As always, feel free to comment or ask any questions here as well.

Feel free to open a pull request organizing the list in alphabetical order every time you find something out of order.

Describe the bug The 'CONTRIBUTING.md' link is not loading 'CONTRIBUTING.md' file

To Reproduce Steps to reproduce the behavior: 1. Go to 'Contributing section of README.md' 2. Click on 'CONTRIBUTING.md link' 3. It doesn't load the file

Expected behavior It should have loaded 'CONTRIBUTING.md' file

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

Desktop (please complete the following information): - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22]

Smartphone (please complete the following information): - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22]

Additional context Add any other context about the problem here.

Is your feature request related to a problem? Please describe. Sauce Labs supports setting cacheId property. It's pretty easy to set it if tests are running with a concurrency of 1, but managing cacheIds becomes tricky when we are running, say, 10 tests with a max concurrency of 3 (using maxInstances capability).

Describe the solution you'd like Add a boolean argument named autoSetCacheId in the config file. If this argument is set to true, reuse same 3 devices for those 10 tests with the help of cacheId.

Describe alternatives you've considered - An alternative would be to not use maxInstances capability, and just run each test in a separate process (essentially having my own maxInstances implementation in bash) - Implement this feature ourselves in our project. Something like: have an array of "released cacheIds". Whenever a new test starts, we can check if there is a cacheId available in that array. If there is, use it. If there isn't, generate a new one. Whenever the test finishes, add the cacheId used in that test to that array.

Implement any algorithm or data structure or solve any programming problem in any language you want, when done, share your success by making a PR. Include the file in your pull request. Keep the name of the file as: Language-Problem Short Name eg: Python-Knapsack.py

This change is  <!-- Reviewable:end -->

I was able to confirm that os.Create() will happily follow symlinks.

Although standard tools like tar will not likely allow you to add two files with the same name to an archive file, it's certainly easy enough to do in code. This means that we need to add an additional check before writing to a destination to make sure that it's not a symlink outside of the destination.

The vulnerability only exists if OverwriteExisting is also turned on.

What file is affected?

filecompressor.go: ```go // DecompressFile reads the source file and decompresses it to destination. func (fc FileCompressor) DecompressFile(source, destination string) error { if fc.Decompressor == nil { return fmt.Errorf("no decompressor specified") }

if !fc.OverwriteExisting && fileExists(destination) {
    return fmt.Errorf("file exists: %s", destination)
}

// TODO needs check here

in, err := os.Open(source)
if err != nil {
    return err
}
defer in.Close()

out, err := os.Create(destination)
if err != nil {
    return err
}
defer out.Close()

return fc.Decompress(in, out)

} ```

Possible solution

If the destination exists we should always check if it's a symlink first:

```go if fileExists(destination) { // TODO check if destination is a symlink with an outside target // should be a simple os.Lstat()

    if !fc.OverwriteExisting {
        return fmt.Errorf("file exists: %s", destination)
    }
}

```

Also, we could block ALL symilnks that have a target outside of the destination directory.

I think the former approach is the best for now, as some archives may link outside of the destination directory for legitimate reasons.

Please link to any related issues, pull requests, and/or discussion

This is related to

• https://github.com/mholt/archiver/pull/203
• https://github.com/mholt/archiver/pull/169
• https://github.com/mholt/archiver/pull/70
• https://github.com/snyk/zip-slip-vulnerability/issues/41

• [ ] Create CONTRIBUTING.md file in the root folder
• [ ] Add How to Contribute instructions to the file

Please use markdown!

• [ ] Add Install and Run instructions to run this React-Native project generated with expo-cli

Clicking on a proposed name takes the user to another screen where the user can see availability of that domain

To keep things simple, as of now we can probably open some website like https://namechk.com/ and pre-fill the domain name

If you are a first-time contributor you can contribute to this project by re-designing the CONTRIBUTING.md file. Use your imagination and make it more beautiful. However, please do not remove important information from the CONTRIBUTING.md file. Feel free to add more information as you see fit.

Find the component under components/QuoteCard.tsx * [ ] Update the color codes to the tailwind present from this demo -> https://theme-ui.com/demo * [ ] Copy icon should be on the bottom right of the card. No need of text Copy. * [ ] Adjust alignments and font-sizes. Test with large captions of 100 characters. * [ ] Add a screenshot of the new UI along with your PR

• [ ] Take a look at https://github.com/devcer/captions-for-ig/blob/master/captions.csv to see for captions without tags or mood
• [ ] Use your common sense and judgement to think of the tags and mood to fill up those columns in the sheet.

Please take a look at the README.md for the list of moods

If you are a first-time contributor you can contribute to this project by re-designing the README.md file. Use your imagination and make it more beautiful. However, please do not remove important information from the README.md file. Feel free to add more information as you see fit.

Hacktoberfest 2020

Hacktoberfest 2020 🎉

So, the festive season for OPEN SOURCE is back guys and we are here to help you contribute (and grab the swags :tada: ).

🗣 Hacktoberfest encourages participation in the open source community, which grows bigger every year. Complete the 2020 challenge and earn a limited edition T-shirt.

📢 Register here for Hacktoberfest and make four pull requests (PRs) between October 1st-31st to grab free SWAGS 🔥.

GOAL

To help you contribute to OPEN SOURCE REALM.

WHAT YOU NEED TO DO

• Go and open README.
• Follow the steps there :rocket: :tada:.


Add a query to fetch total confirmed, deceased and active COVID-19 cases for a given a state code.

Please check the API here.

There is not any query for getting latest data, add a query to get data for current date.

js { latest { active confirmed deaths recovered } }

Current UI is not responsive.


In the mobile view the tab shifts to the right, so margins on both sides becomes unequal.

I think once the details of a faculty are displayed, The suggestions tab can be hidden. And can be displayed again once the user starts searching. What is your suggestion @vinitshahdeo ?


The list of names displayed is not fitting in the container.


Hello, I am a beginner and I'd like to contribute in this project. Go easy on me lol

Regards,

Reinaldo

Map organizations in your country where you can donate money to plant trees and save the world 🌳

Hey, I am quite a newbie to programming and this is the first time I am trying to contribute to an open-source project. I have experience with working on operational tasks for 6 months in a cloud telephony company.

Following this issue comment https://github.com/bancodobrasil/stop-analyzing-api/issues/16#issuecomment-667519483, document the endpoint to get the next choice in the README.md

CVE-2020-15168 - Medium Severity Vulnerability

Vulnerable Library - node-fetch-1.7.3.tgz

A light-weight module that brings window.fetch to node.js and io.js

Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz

Path to dependency file: mycovidconnect/package.json

Path to vulnerable library: mycovidconnect/node_modules/node-fetch/package.json

Dependency Hierarchy: - react-google-maps-9.4.5.tgz (Root Library) - recompose-0.26.0.tgz - fbjs-0.8.17.tgz - isomorphic-fetch-2.2.1.tgz - :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)

Found in HEAD commit: 3dacf50349ac32a7152cbf1b2f833e52e653fc42

Found in base branch: master

Vulnerability Details

node-fetch before versions 2.6.1 and 3.0.0-beta.9 did not honor the size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

Publish Date: 2020-09-10

URL: CVE-2020-15168

CVSS 3 Score Details (5.3)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r

Release Date: 2020-07-21

Fix Resolution: 2.6.1,3.0.0-beta.9

Step up your Open Source Security Game with WhiteSource here

Vulnerabilities

DepShield reports that this application's usage of lodash:4.17.19 results in the following vulnerability(s):

• (CVSS 7.4) [CVE-2020-8203] Prototype pollution attack when using _.zipObjectDeep in lodash <= 4.17.15.

Occurrences

lodash:4.17.19 is a transitive dependency introduced by the following direct dependency(s):

• @testing-library/jest-dom:4.2.4         └─ lodash:4.17.19

• node-sass:4.14.1         └─ gaze:1.1.3               └─ globule:1.3.2                     └─ lodash:4.17.19         └─ lodash:4.17.19         └─ sass-graph:2.2.5               └─ lodash:4.17.19

• react-google-maps:9.4.5         └─ lodash:4.17.19

• react-scripts:3.4.3         └─ @babel/core:7.9.0               └─ @babel/helper-module-transforms:7.11.0                     └─ lodash:4.17.19               └─ @babel/traverse:7.11.0                     └─ lodash:4.17.19               └─ @babel/types:7.11.0                     └─ lodash:4.17.19               └─ lodash:4.17.19         └─ @svgr/webpack:4.3.3               └─ @babel/preset-env:7.11.0                     └─ @babel/plugin-transform-classes:7.10.4                           └─ @babel/helper-define-map:7.10.5                                 └─ lodash:4.17.19                     └─ @babel/plugin-transform-sticky-regex:7.10.4                           └─ @babel/helper-regex:7.10.5                                 └─ lodash:4.17.19         └─ @typescript-eslint/parser:2.34.0               └─ @typescript-eslint/typescript-estree:2.34.0                     └─ lodash:4.17.19         └─ eslint:6.8.0               └─ inquirer:7.3.3                     └─ lodash:4.17.19               └─ lodash:4.17.19               └─ table:5.4.6                     └─ lodash:4.17.19         └─ eslint-plugin-flowtype:4.6.0               └─ lodash:4.17.19         └─ html-webpack-plugin:4.0.0-beta.11               └─ lodash:4.17.19         └─ jest-environment-jsdom-fourteen:1.0.1               └─ jsdom:14.1.0                     └─ request-promise-native:1.0.9                           └─ request-promise-core:1.1.4                                 └─ lodash:4.17.19         └─ optimize-css-assets-webpack-plugin:5.0.3               └─ last-call-webpack-plugin:3.0.0                     └─ lodash:4.17.19         └─ react-dev-utils:10.2.1               └─ inquirer:7.0.4                     └─ lodash:4.17.19         └─ webpack-dev-server:3.11.0               └─ http-proxy-middleware:0.19.1                     └─ lodash:4.17.19               └─ portfinder:1.0.28                     └─ async:2.6.3                           └─ lodash:4.17.19         └─ webpack-manifest-plugin:2.2.0               └─ lodash:4.17.19

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Vulnerabilities

DepShield reports that this application's usage of lodash.uniq:4.5.0 results in the following vulnerability(s):

• (CVSS 7.4) CWE-471: Modification of Assumed-Immutable Data (MAID)
• (CVSS 6.5) [CVE-2018-3721] lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutabl...

Occurrences

lodash.uniq:4.5.0 is a transitive dependency introduced by the following direct dependency(s):

• react-scripts:3.4.3         └─ optimize-css-assets-webpack-plugin:5.0.3               └─ cssnano:4.1.10                     └─ cssnano-preset-default:4.0.7                           └─ postcss-merge-rules:4.0.3                                 └─ caniuse-api:3.0.0                                       └─ lodash.uniq:4.5.0

_{This is an automated GitHub Issue created by Sonatype DepShield. Details on managing GitHub Apps, including DepShield, are available for personal and organization accounts. Please submit questions or feedback about DepShield to the Sonatype DepShield Community.}

Add focusRectSizeFactor parameter for rectangle focus shape (like focusCircleRadiusFactor for circular). Default value should be 1.

The result of the crawler made by @douglasferlini in #5 is a JSON array with the overall information of the dresses os La Fiancee. Now, we need now to get the details of the dresses and generate a more detailed JSON array.

To do so, you will read the attached JSON and will make a request for the product API providing the urlPartin the following format:

Javascript const productID = <urlPart_from_json_array> await fetch("https://www.lafiancee.com.br/_api/wix-ecommerce-storefront-web/api", { "credentials": "include", "headers": { "Accept": "*/*", "Authorization": "brUTfgwc9eaqQ4m_KjbIkjnR-MRt9rGfCLGikGEPiRU.eyJpbnN0YW5jZUlkIjoiMWI0OTQ1ODItZDg5Zi00MmY2LTg0YzAtNTAxOGE3NzI1Y2MyIiwiYXBwRGVmSWQiOiIxMzgwYjcwMy1jZTgxLWZmMDUtZjExNS0zOTU3MWQ5NGRmY2QiLCJtZXRhU2l0ZUlkIjoiN2RlM2ExNjgtNDEyNC00NDljLTg4ZDYtZmViNjkzYWY3NzRjIiwic2lnbkRhdGUiOiIyMDIwLTA5LTIzVDEyOjI3OjE4LjUyOVoiLCJ2ZW5kb3JQcm9kdWN0SWQiOiJQcmVtaXVtMSIsImRlbW9Nb2RlIjpmYWxzZSwiYWlkIjoiOWE0ZjJjNDAtMTIzNC00ZGM3LTg3OWEtMjIzZDMxMzI0N2E1IiwiYmlUb2tlbiI6IjY2YWFlNGVhLTk5YmItMDY2YS0wYzE2LWFlYWUzNGRkMmI4ZSIsInNpdGVPd25lcklkIjoiZmI0Y2Y2ODQtODZkZS00N2E0LWE2NjUtZjE4ZDcxYzA3YzUxIn0", "Content-Type": "application/json; charset=utf-8", }, "body": `{"query":"query getProductBySlug($externalId: String!, $slug: String!, $withPricePerUnit: Boolean!, $withCountryCodes: Boolean!) { appSettings(externalId: $externalId) { widgetSettings } catalog { product(slug: $slug, onlyVisible: true) { id description isVisible sku ribbon price comparePrice discountedPrice formattedPrice formattedComparePrice formattedDiscountedPrice pricePerUnit @include(if: $withPricePerUnit) formattedPricePerUnit @include(if: $withPricePerUnit) pricePerUnitData @include(if: $withPricePerUnit) { baseQuantity baseMeasurementUnit } seoTitle seoDescription createVersion digitalProductFileItems { fileId fileType fileName } productItems { price comparePrice formattedPrice formattedComparePrice pricePerUnit @include(if: $withPricePerUnit) formattedPricePerUnit @include(if: $withPricePerUnit) optionsSelections isVisible inventory { status quantity } sku weight surcharge subscriptionPlans { list { id price formattedPrice pricePerUnit @include(if: $withPricePerUnit) formattedPricePerUnit @include(if: $withPricePerUnit) } } } name isTrackingInventory inventory { status quantity } isVisible isManageProductItems isInStock media { id url fullUrl altText thumbnailFullUrl: fullUrl(width: 50, height: 50) mediaType videoType videoFiles { url width height format quality } width height index title } customTextFields { title isMandatory inputLimit } nextOptionsSelectionId options { title optionType selections { id value description linkedMediaItems { altText url fullUrl thumbnailFullUrl: fullUrl(width: 50, height: 50) mediaType width height index title videoFiles { url width height format quality } } } } productType urlPart additionalInfo { id title description index } subscriptionPlans { list(onlyVisible: true) { id name tagline frequency duration price formattedPrice pricePerUnit @include(if: $withPricePerUnit) formattedPricePerUnit @include(if: $withPricePerUnit) } oneTimePurchase { index } } discount { mode value } currency weight seoJson } } localeData(language: "en") @include(if: $withCountryCodes) { countries { key shortKey } } }","variables":{"slug":productID,"externalId":"","withPricePerUnit":true,"withCountryCodes":false},"source":"WixStoresWebClient","operationName":"getProductBySlug"}`, "method": "POST", });

This request will return a JSON that has the product options with title and selections which will be the features.

With this enhanced JSON Array we can build the database to serve this data.

Adding issue templates and pull request template will enhance the workflow of the repository.

Use the new form of ISSUETEMPLATE i.e. making a folder ISSUETEMPLATE in .github and adding different types of .md files for different issues like bug.md, documentation.md and feature.md. A contributor can choose the type of templates whenever they make an issue.

Reference: https://docs.github.com/en/github/building-a-strong-community/about-issue-and-pull-request-templates