there is data_structures/src/list/singly_linked_list, but there is also a code for same problem in data_structures/linked_list/
One of them ought to be removed.

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

Refactoring based on the comment

Differentiate config (instance of Config class) and settings (content of the config section)

• documentation on how to configure the facebook app in development mode ( ref #39)
• how to configure the bot url
• how to run the bot endpoint in local using ngrock or serveo.net

version 0.6.9 (0.6.9.91)
macOS 10.14.6

Motivation

After mentioning deprecating docker images in #1015 I think this merits a holistic review of our Dockerfiles.

Feature

Can we please audit, and document which container images we are supporting, how each of them sho

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

Your checklist for this issue

🚨 Please review the guidelines for contributing to this repository.

• Link to any upstream changes that might be required (for example Jenkins Core pull request)

Feature Request

It is currently po

Expected Behaviour

Instructions for deployment with "helm template" should reflect new syntax as of helm version 3

Current Behaviour

Instructions for deployment with

Describe the bug
After adding few sources and opening few articles images stopped to apear in articles

To Reproduce
Steps to reproduce the behavior:

1. Add 2 sources
2. Open few articles
3. After some time articles stop to show images

Expected behavior
Images displayed

Screenshots
![2019-02-14__21-42-53](https://user-images.githubusercontent.com/14232100/52814148-1

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

After the update (today) the code cracker started reporting commented code for code that was previously not reported.

Example:

This code produces two warnings. It seems the pattern Word : Word (white space ignored) produces the error. It also applies for web pages in comments (but there seems to be an advanced rule for this).

    // word : word
    int value;

    //

• 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.

Currently, contributing guidelines do not exist.
IMHO, contributing guidelines would be a great addition to the repository.

I remember Vue tools used to work nicely at some point, now I get a bunch of errors at the end of npm run dev, anyone have a workaround is driving me insane. Been searching forever for a solution.

┏ Electron -------------------

  Debugger listening on ws://127.0.0.1:5858/0f8f45a8-a340-4e2b-9276-37e1b2063253
  For help see https://nodejs.org/en/docs/inspector

┗ --------------------

Context

Excalibur sample "excalibird" is using a super old version of excalibur (v0.2.5), it should be updated to reflect current excalibur.

https://github.com/excaliburjs/excalibird

Proposal

• Update to use typescript
• Update to use webpack build
• Update to the lastest excalibur
• Add to CI
• Add to Renovate

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 ":"

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