Add dropdown with all available model languages in client side

server side expose end point to get all available languages.

server side refactor /api/upload support language in request

Server side save recent 3-5 images with there prediction.

Expose end point to fetch recent predictions

client side add component showing recent predictions

Current Behavior <!-- A brief description of what the current circumstance is. --> Layer5 is participating in SheCodeAfrica Contributhon Program & Programs Page is missing card & details for it .

Desired Situation <!-- A brief description of the necessary action to take. -->

Add a Card & details for SheCodeAfrica Program . Please refer to this doc for more details about the program https://docs.google.com/document/d/1_LUAqcCnAl-8lCZMKBSRUsZB1358SjHT3cPyej2wTcg/edit#

Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch. - See contributing instructions - See Layer5 site designs in this Figma project. Join the Layer5 Community for access.

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.

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 - For more details about this gem, visit the official repository of whenever gem. + For more details about this gem, visit the official repository of the whenever gem.

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

Environment (please complete the following information): - WebdriverIO version: 7.3.1 - Mode: WDIO Testrunner - If WDIO Testrunner, running sync/async: sync - Node.js version: 12.22.1 - NPM version: 6.14.12 - Additional wdio packages used (if applicable): "@wdio/cucumber-framework": "^7.3.1", "@wdio/local-runner": "^7.3.1", "@wdio/sauce-service": "^7.3.1", "@wdio/spec-reporter": "^7.3.1", "@wdio/sync": "^7.3.1"

Config of WebdriverIO https://github.com/michalboo/wdio-eu-link/blob/eu-reporter-link-issue/wdio.conf.js

Describe the bug Running tests in Saucelabs with the eu region works as expected, but the 'Check out job at …' links posted in stdout by the reported point to the https://app.saucelabs.com domain (instead of the expected https://app.eu-central-1.saucelabs.com/tests/…). This causes problems (a 404 in saucelabs), especially for newcomers trying to debug failures.

Going from: To:

Looking into the code, it appears that the region config field "gets lost" before reaching what seems to be the relevant spec-reporter code

The region appears to get dropped at the point of starting the remote session. The validateConfig function is invoked with a keysToKeep argument, containing the keys of the the webdriver config DEFAULTS onject: https://github.com/webdriverio/webdriverio/blob/dc7413a095ad13cfb6c49a8937696aa394ccb2cc/packages/webdriverio/src/index.ts#L33 This is defined in: https://github.com/webdriverio/webdriverio/blob/dc7413a095ad13cfb6c49a8937696aa394ccb2cc/packages/webdriver/src/constants.ts#L6, and does not include region.

To Reproduce Steps to reproduce the behaviour: 1. run tests on saucelabs with region 'eu' 2. Check out the "Check out job at …" link in the stdout report

(cloning https://github.com/michalboo/wdio-eu-link/blob/eu-reporter-link-issue/ and running: npm i SAUCE_USERNAME=<YER_USERNAME> SAUCE_ACCESS_KEY=<YER_ACCESS_KEY> npx wdio run wdio.conf.js should also do it.

Expected behavior The "Check out job at …" link points at the correct (eu) saucelabs domain.

Log https://gist.github.com/michalboo/212fbdaf468da66c06da65a1c0785e57

Additional context This appears to work as expected in wdio 6 (checked 6.6.3) I'd appreciate some thoughts on what the best way of fixing this could be. I imagine it would be relatively simple to (re)add region to the webdrivier DEFAULTS constant, similar to the fix in https://github.com/webdriverio/webdriverio/pull/6416, but I don't know a great deal about the overall picture (so I could be missing something simple/obvious/beautiful).

Current State:

The screenshot showing a performance graph to describe the SMP feature is out of date in the Meshery README.

Desired State:

A new, animated gif shows off this feature in a better way. The readme should be updated to use this new gif.

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

Current State: Meshery supports deployment of WebAssembly filters to Envoy-based data planes. The https://meshery.io site describes this feature:

Desired State: This repo's readme.md should describe the feature in the same way.

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

The Sauce service updates the job details page command tab with an error message in case the test fails (see code lines here). When using our expect-webdriverio assertion library we have color ascii characters in that message, making it look as follows:


Let's strip these characters from being uploaded and just send text.

follow Hebrew instructions at #37

follow Hebrew instructions at #37

follow Hebrew instructions at #37

Current Behavior <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> Currently the values on getnighthawk page https://layer5.io/projects/getnighthawk are not smoothly getting to it's final value like we have here https://layer5.io/service-mesh-management/meshery

As Currently <h3 /> tag is used . Just replace that with <Counter /> Component present in /sections/reusecore .


Desired Behavior <!-- A brief description of the enhancement. --> when the page renders ,values should reach there final values smoothly not instantly.

[Optional] Screenshots / Mockups

https://user-images.githubusercontent.com/44670961/113593149-b3ec6c80-9653-11eb-8da2-5ea1c8ce6c2c.mp4

[Optional] Alternatives <!-- A brief description of any alternative solutions or features you've considered. -->

Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch. - See contributing instructions - See Layer5 site designs in this Figma project. Join the Layer5 Community for access.

Current Behavior <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> Each Workshop Card neither opens smoothly nor does it close. https://layer5.io/learn/service-mesh-workshops

Desired Behavior <!-- A brief description of the enhancement. --> Workshop card should open smoothly on clicking Read More button & close smoothly on clicking Read Less button.

[Optional] Screenshots / Mockups <!-- Add any other context or screenshots about the feature request here. -->

https://user-images.githubusercontent.com/44670961/113560099-17f53d80-9620-11eb-8628-e6b80f9b96b1.mp4

[Optional] Alternatives <!-- A brief description of any alternative solutions or features you've considered. -->

Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch. - See contributing instructions - See Layer5 site designs in this Figma project. Join the Layer5 Community for access.

Basically this is two steps:

1. Every instance of New-Item that is nested in an IF ... Test-Path should be de-nested - the IF is redundant ```diff -if (!(Test-Path -Path Downloads)) -{
   • New-Item -Path Downloads -ItemType Directory -Force
   • New-Item -Path Downloads -ItemType Directory -Force -} ```
2. Every instance of New-Item and Remove-Item should be updated to end in | out-null ```diff -Remove-Item -Path "$pkgdstcmd" -Recurse -ErrorAction Ignore +Remove-Item -Path "$pkgdstcmd" -Recurse -ErrorAction Ignore | out-null
   • New-Item -Path Downloads -ItemType Directory -Force +New-Item -Path Downloads -ItemType Directory -Force | out-null ```

Tips

You can of course use your familiar GUI tools, but...

If you want to get a quick list of all of the install.ps1 files throughout the repo using modern CLI tools, you could use fd and rg, like so:

```bash curl -sS https://webinstall.dev | bash webi fd rg

git clone YOUR-FORK pushd YOUR-FORK git checkout -b ps1-cleanup fd | rg 'install.ps1' ```

You could then edit the files with your weapon of choice. I'd probably use sd. You could use VS Code or vim or whatever suits your fancy.

Documentation

If you want to learn some git, try this: https://www.youtube.com/playlist?list=PLxki0D-ilnqbXhctTFCDGH3fSN7l7ATkL

If you want to see how new projects are added to Webi, see this: https://github.com/webinstall/webi-installers/blob/master/.github/ISSUETEMPLATE/newinstaller.md

Current Behavior <!-- A brief description of what the problem is. (e.g. I need to be able to...) --> Command div neither smoothly opens nor does it close.

Desired Behavior <!-- A brief description of the enhancement. -->

Command div should open & close smoothly.

[Optional] Screenshots / Mockups <!-- Add any other context or screenshots about the feature request here. -->

https://user-images.githubusercontent.com/44670961/113507184-9b525880-9566-11eb-839e-0b44334f174b.mp4

[Optional] Alternatives <!-- A brief description of any alternative solutions or features you've considered. -->

Contributor Resources

The layer5.io website uses Gatsby, React, and GitHub Pages. Site content is found under the master branch. - See contributing instructions - See Layer5 site designs in this Figma project. Join the Layer5 Community for access.

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/node.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 @@ -850,6 +850,15 @@ def add_tag(tagname, user) # add sub-tags: subtags = {} subtags['pm'] = 'particulate-matter' + subtags['pm'] = 'air-quality' + subtags['h2s'] = 'hydrogen-sulfide' + subtags['near-infrared-camera'] = 'multispectral-imaging' + subtags['infragram'] = 'multispectral-imaging' + subtags['odors'] = 'odor' + subtags['oil'] = 'oil-and-gas' + subtags['purple-air'] = 'purpleair' + subtags['reagent'] = 'reagents' + subtags['spectrometer'] = 'spectrometry' if subtags.include?(key) add_tag(subtags[key], user) 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!

Markdox now introduces 4 severe bugs to the code base. They shouldn't impact the user given we generate our docs in CI but it is still something we should clean up. I suggest to switch to jsdoc-to-markdown.

today we only support English and Chinese label translations

translate image net labels to Hebrew take https://github.com/ntedgi/node-efficientnet/blob/main/misc/en.json translate it to Hebrew using some machine or by hand

• add it to /misc folder

• add the ENUM and corresponding case under EfficientNetLanguageProvider

• add minimal test for example : ```

test("EfficientNetLanguageProvider - check chinese translation file", (done) => { const chineseProvider = new EfficientNetLanguageProvider( EfficientNetLableLanguage.CHINESE ); chineseProvider .load() .then(() => { const result = chineseProvider.get(0); expect(result).toBeDefined(); expect(result).toEqual("丁鲷"); done(); }) .catch((error) => done(error)); }); ``` - update readme file add the language support to https://github.com/ntedgi/node-efficientnet#multilingual-status

ui changes: under here add a new line: "Supported file types : JPG, PNG ,GIF,SVG,HEIC,WEBP"

add available files format to file uploader component

On the /check-client page, exemplify the CURL command. An improvement would be to add a RUN button that already executed this command on the screen and showed the result.

Describe the bug When I create a survey and then go to import posts in settings->import, my new survey is not visible in the list of surveys to select.

To Reproduce Steps to reproduce the behavior: As logged in 1. Go to settings->surveys 2. Create a new survey 3. Save and go to settings->import 4. Click on the "Import to survey"-dropdown 5. The new survey is not in the list 6. Expected behavior The survey should be in the list.

*Hints 💡 💡 *

• The code that belongs to the import-feature is found in this folder: https://github.com/ushahidi/platform-client/tree/develop/app/settings/data-import
• For your awareness: "Surveys" are called "Forms" in this directive.
• There are different methods to fetch the forms from the backend. The form-endpoint service, where you can see the different methods, is found here: https://github.com/ushahidi/platform-client/blob/develop/app/common/services/endpoints/form.js

Describe the bug In the translation-editor for integer, decimal, datetime/date, a field for default value translations is visible. It should not be since its not something we translate.

To Reproduce Steps to reproduce the behavior: As logged in admin: 1. Go to Settings->Surveys->Create a new survey 2. Add a new integer, decimal or datetime/date field 3. Add a default value for the field 4. Add a new language 5. Go to the translation-editor and click on the new field 6. There is a field for translating the default value.

*Hints 💡 * - The code that shows the default-field is found here: https://github.com/ushahidi/platform-client/blob/develop/app/settings/surveys/field-translation-editor.html#L51 - We only want to show the default-field when "field.type" or "field.input" is "text"

Current Behavior

Section titles on the /management page are center-aligned.

Desired Behavior

Section titles on the /management page should be left-aligned.

Mockups


Current Behavior Individuals at SolarWinds have contributed the Service Mesh Performance initiative.

Desired Behavior SolarWinds' participation should be represented in the Contributors section of the website.

Find a copy of the SolarWinds logo on the https://meshery.io site.

Contributor Resources - Service Mesh Performance documentation source - Instructions for contributing to documentation

Current Behavior Individuals at Intel have joined the Service Mesh Performance initiative.

Desired Behavior Intel's participation should be represented in the Contributors section of the website.

CVE-2021-3281 - Medium Severity Vulnerability

Vulnerable Library - Django-1.11.29-py2.py3-none-any.whl

A high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Library home page: https://files.pythonhosted.org/packages/49/49/178daa8725d29c475216259eb19e90b2aa0b8c0431af8c7e9b490ae6481d/Django-1.11.29-py2.py3-none-any.whl

Path to dependency file: covidX/requirements.txt

Path to vulnerable library: covidX/requirements.txt

Dependency Hierarchy: - graphene_django-2.13.0-py2.py3-none-any.whl (Root Library) - :x: **Django-1.11.29-py2.py3-none-any.whl** (Vulnerable Library)

Found in HEAD commit: 6f3dbcb5ab003a4ef1776b72be10967612787631

Vulnerability Details

In Django 2.2 before 2.2.18, 3.0 before 3.0.12, and 3.1 before 3.1.6, the django.utils.archive.extract method (used by "startapp --template" and "startproject --template") allows directory traversal via an archive with absolute paths or relative paths with dot segments.

Publish Date: 2021-02-02

URL: CVE-2021-3281

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: Low - Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.djangoproject.com/weblog/2021/feb/01/security-releases/

Release Date: 2021-02-02

Fix Resolution: 2.2.18,3.0.12,3.1.6

Step up your Open Source Security Game with WhiteSource here

CVE-2020-36242 - High Severity Vulnerability

Vulnerable Library - cryptography-3.2-cp27-cp27mu-manylinux2010_x86_64.whl

cryptography is a package which provides cryptographic recipes and primitives to Python developers.

Library home page: https://files.pythonhosted.org/packages/b2/55/b298540fe693643e2b49dfb5ade6ed711f3e1b39159a9f643376325d76a2/cryptography-3.2-cp27-cp27mu-manylinux2010_x86_64.whl

Path to dependency file: covidX/requirements.txt

Path to vulnerable library: covidX/requirements.txt

Dependency Hierarchy: - pyOpenSSL-19.1.0-py2.py3-none-any.whl (Root Library) - :x: **cryptography-3.2-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)

Found in HEAD commit: 6f3dbcb5ab003a4ef1776b72be10967612787631

Vulnerability Details

In the cryptography package before 3.3.2 for Python, certain sequences of update calls to symmetrically encrypt multi-GB values could result in an integer overflow and buffer overflow, as demonstrated by the Fernet class.

Publish Date: 2021-02-07

URL: CVE-2020-36242

CVSS 3 Score Details (9.1)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst

Release Date: 2021-02-07

Fix Resolution: cryptography - 3.3.2

Step up your Open Source Security Game with WhiteSource here

CVE-2020-25626 - Medium Severity Vulnerability

Vulnerable Library - djangorestframework-3.9.4-py2.py3-none-any.whl

Web APIs for Django, made easy.

Library home page: https://files.pythonhosted.org/packages/1b/fe/fcebec2a98fbd1548da1c12ce8d7f634a02a9cce350833fa227a625ec624/djangorestframework-3.9.4-py2.py3-none-any.whl

Path to dependency file: covidX/requirements.txt

Path to vulnerable library: covidX/requirements.txt

Dependency Hierarchy: - drf_jwt-1.17.2-py2.py3-none-any.whl (Root Library) - :x: **djangorestframework-3.9.4-py2.py3-none-any.whl** (Vulnerable Library)

Found in HEAD commit: 6f3dbcb5ab003a4ef1776b72be10967612787631

Vulnerability Details

A flaw was found in Django REST Framework versions before 3.12.0 and before 3.11.2. When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious