This is a(n):

• New algorithm
• Update to an existing algorithm
• Error
• Proposal to the Repository

Details:

We can make a file may be READ.

Extracted from iterative/dvc#3608 (comment)

To match docs, where options have been ordered manually from more to less important (at least that's the idea).

Example difference:

λ dvc commit -h
usage: dvc commit [-h] [-q | -v] [-f] [-d] [-R] [targets [targets ...]]
...

optional arguments:
  -h, --help            show this help message and 

As caught by @OliverJAsh:
Hey! The fixed background is causing the whole page to be repainted on scroll, FYI

Is your enhancement request related to a problem? Please describe.
It's really hard to type a message containing multiple sentences.

Describe the solution you'd like
The text area should expand once agent types a lengthy message

Describe alternatives you've considered
none

Additional context
none

What to document

I am asking wheter we should remove (or not) the CONTRIBUTING and CODE_OF_CONDUCT from the repo in order to fallback to the organization ones (here).

They are the same files and the .github repo works pretty well as a default mechanism.

version 0.6.9 (0.6.9.91)
macOS 10.14.6

How to docker
How to persist
How to manage plugins
😊

At Cognite, we've had to patch faas-netes as a workaround for openfaas/faas-netes#604 and openfaas/faas-netes#358. We use helm to produce a manifest that we then modify before it is deployed in our k8s clusters, so I need to modify which image I use.

The list over options at the end of https://github.com/openfaas/faas-netes/tree/master/chart/

Hi,

I have installed the Cobalt2 theme for Sublime and I don't get the same colorization as in the JavaScript example screenshot. Here is a screenshot of my code.

Can someone explain me if it is normal that I don't get the same colorization ?

Thank

Would be great to improve coverage of Cloud Commander.
To get current coverage all you need is:

git clone https://github.com/coderaiser/cloudcmd
cd cloudcmd
npm install
npm run coverage

• Populate the list of secure web browsers that doesn't allows browser fingerprinting after visiting the www.nothingprivate.ml in them. If you are not able to fingerprint using that browser, add it to the list: https://github.com/gautamkrishnar/nothing-private/blob/master/Secure-Browsers.md
• Verify whether the browsers listed there are actually secure against fingerprinting.

CS0133 will be raised if you are assigning to a constant. This fix will change const <type> to var.

This:

const string myStr = "abc".ToUpper();

Becomes, if it is a local variable:

var myStr = "abc".ToUpper();

Becomes, if it is in a field:

readonly string myStr = "abc".ToUpper();

Category: Compiler (same as CC0133, ha

In README.txt in player_api, there is the part that is not clear:

stujones11 (CC BY-SA 3.0):
  character.b3d
  character.blend -- Both derived from a model by MirceaKitsune (CC BY-SA 3.0)

An0n3m0us (CC BY-SA 3.0):
  character.b3d
  character.blend -- Player animation improvement

Describe the bug
Repetitive loading have you waiting on gists loading.

To Reproduce
Steps to reproduce the behavior:

1. Go to Gists, see the loading circle
2. Click on local
3. Go back to gists, and a new loading circle appears

Expected behavior
I think the loaded gists should remain loaded even when going to local, and maybe have a refresh button if you want to pull new gi

Context

We are dropping support for older browsers, with the wide-spread support of the WebAudio API the need for our own HTML5 tag based implementation of classes is gone.

Proposal

• Remove AudioTagInstance
• Update AudioInstance implementation to use WebAudio only (perhaps even simplify)
• Update any affected tests to remove isseus

Tailwind is fantastic, but the generated CSS file is coming in at over 1mb 😱 - we should look at using Purge CSS to reduce this, see: https://tailwindcss.com/docs/controlling-file-size/#setting-up-purgecss we should also look to employ some of the other tactics outlined on that page to reduce the size.

Because the endpoint for externalCheckReportHandler does several API lookups over a duration to give fast running checker pods time to appear in the API pod list, we should consider the endpoint dangerous for any public consumption.

This means that any request going to the externalCheckReportHandler from sources outside the cluster should automatically be denied. We should design this in a

Small enhancement request: when I pull a list of issues, the Status is formatted as standard text right next to the title, which is less readable:

Perhaps it should get its own column? Or maybe bolded, and followed with a ":"