The current godoc says of Logger.Out:

It's common to set this to a file, or leave it default which is os.Stderr.

However, this is in the struct doc rather than the documentation for logrus.New. The default when declaring a logrus.Logger as a struct is, of course, nil, and leaving it that way results in a panic [whenever a log wou

Some files in the repository are missing newlines at the very end, as pointed out by @nrbrook in #1026

Classes/CocoaLumberjack.h was specifically mentioned, but there could be other files that are missing this as well.

Rob: The documentation at https://www.elastic.co/guide/en/logstash/current/configuration-file-structure.html#array talks about the array type being largely deprecated, and that isn't really borne out in practice - compare the number of occurrences of config options where :list => :true is used vs :validate => :array is used

Andre: I took a look at the github repos and hope that are the places t

Recently the table manager period has been changed to use model.Duration from Prometheus because of a vendoring in Cortex. see https://github.com/grafana/loki/blob/master/vendor/github.com/cortexproject/cortex/pkg/chunk/table_manager.go#L95 and #1838

The problem is that before time.Duration was supporting the value 0. Before it propagates to other fields we should try to suggest in the [pro

I am trying to run an express app through Visual Studio Code. I have a launch.json file with DEBUG defined like so:

        "env": {
             "DEBUG": "*"
        }

Here is a trimmed down version of my app.js file where you can see the bolded debug line that doesn't output to the debug console (Test 2). Test 1 before it outputs as expected. If I run this from the command li

Currently there is an inconsistency of the naming convention for the inputs. Of the ~30 inputs, there are 5 that contain the word "input" in the name of the input

Expected Behavior

Tasks:

• Update Android Documenation!
• May be add a build issue FAQ, for example #2543

I've wanted to craft a "1 minute", "5 minute", "15 minute" moving average (like a unix load average), but don't know the right r to pass to ewma-timeless to get it.

Either documenting a rule of thumb or providing a mechanism to recreate that would be helpful.

Someone should map publicly available EVTX samples to Sigma rules. This would enable us to automatically test the correctness of generated queries.

Known security-related EVTX repositories:

• https://github.com/sbousseaden/EVTX-ATTACK-SAMPLES
• https://github.com/Cyb3rWard0g/mordor

Feel free to extend the list.

Mapping should be:

Sigma rule -> Repository/EVTX ( -> expected matched