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

Currently in the Mod center, when you click a post it opens inline underneath the post you clicked. This is really nice BUT it can be useful opening a bunch of posts into multiple tabs and handle it that way.

Because the post items are handled by JS magic, you can't actually open them into a new tab.

**Describe the solutio

You may use this guide to make quality contributions at Hacktoberfest 2020: Hacktoberfest 2020 guide

To begin contributing, you shall get a quick overview of how Cosmos is used today. Cosmos is one of the most extensive code database and is used as:

• A datastore for various projects (such as [Quark](https://github.com/OpenGenus/

it would be good to have
min-width, max-width <-- this 2 is good for PWA, if user resized it too small, it would become ugly.
maximized <-- this would be maximized on first load.

another thing would be, try delay webview resize when the host window resize, like how all the browser did, this would make sure PWA reflective size won't response immediately... current resize is seriously lagging

dvc metrics show -a currently gives

workspace:
        eval.json:
                AUC: 0.66729
                error: 0.16982
                TP: 516
master:
        eval.json:
                AUC: 0.65115
                error: 0.17304
                TP: 528
increase_bow:
        eval.json:
                AUC: 0.66524
                error: 0.17074
                TP: 52

Description
Remove any google fonts dependency from api-platform.

Example
Remove the google font stylesheet in line 8 of api-platform\core\src\Bridge\Symfony\Bundle\Resources\views\SwaggerUi\index.html.twig depending on a configuration variable?

Context
I'm working on an intranet application for a big company where any call to the fonts.googleapi.com CDN takes 30 seconds

Enhancement

Label names in chatwoot only support alphabets, numbers, hyphen and underscore.
At the moment the available validation doesn't show the user any errors, which would leave the user confused.

So let's add a validation error describing this behaviour

Current behaviour

<img width="1273" alt="Screenshot 2020-10-02 at 4 29 03 PM" src="https://user-images.githubuserconten

🐛 Bug report

Description

You can use UI-Bypass on checkout to get a negative wallet (To pay without having enough money)
(It could also get a nice Challange :)

🔬 Minimal Reproduction

We need to design a single Docker container that can run all of the Appwrite services and internal processes using Supervisord. This should be a feature with Appwrite minimum, must-have features (ClamAV disabled, no need for Traefik). This is something we need to allow developers to run Appwrite easily on low-end systems and 1-click deployment services (Raspberry PI, Free hosting tiers, Heroku, Ki

🐛 Bug description

From the documentation it seems that the event TERMINATE_SINGLE_EPOCH is only fired, if engine.terminate_epoch is called.
I discovered, that the event is also fired, if I call engine.terminate inside of an epoch as can be seen in the code linked below.

Event description:
https://github.com/pytorch/ignite/blob/51d3e3e54ee042b5ef1b73a489aabe4b75968411/ignite/engin

What happened:
Tried running Regression test using command ./test/run_regression_tests.sh $PWD/build.
The test

With #4150 merged we have a new model format: glTF ! This should be a much easier and long-lived format than the old md5 one. There are still some bits of cleanup and bugs to fix. Not necessarily all needed as part of this issue and some bits might be worthwhile to split out

Some of the following checkboxes may be suitable Good First Issues for anybody with some

Aforementioned article lacks the technical interview round questions. Anyone taking this issue must follow the contributing guidelines.

Problem
Users can set custom metadata on their customers, but we currently don't display this information anywhere in the UI.

This is what we currently display:

Solution
Using this metadata field on the customer o

The Jenkins project now uses "agent"and "controller" as official terms. See https://issues.jenkins-ci.org/browse/JENKINS-42816 and https://groups.google.com/forum/#!topic/jenkinsci-dev/CLR55wMZwZ8 for the reference. There are some occurrences which could be cleaned up:

• Docker image names
• Configuration entries for plugins which now support "agent"/"controller" aliases.
• Documentation tex