chaos

The library controller-runtime requires setting a logger (by log.SetLogger()) at the first 30s when the application starts, or it would use the default NullLogSink. We should also call it in testing codes.

When we test with ginkgo, ginkgo provides a helpful GinkgoWriter, which hides the output as default, only prints it when the test failed. We'd better use it to keep our testing output

The idea is to compile a list of publicly available bbp/vdp programs in a structured manner that can be consumed by a program to index subdomains of given domain and publish it at https://chaos.projectdiscovery.io

Format

{
   "name":"HackerOne",
   "url":"https://hackerone.com/security",
   "bounty": true,
   "swag": true,
   "domains":[
      "hackerone.com",
      "h

Be conservative about the changes necessary to the core of DAPPER.

ATM, this requires pretending variable-length state or obs are fixed-length. This enables using np.ndarrays without hassle, but includes overhead.

• Is "pretending" compatible with all DA methods?
• How should RMSEs be calculated?

Even though both GALI and expansion entropy tests pass, they take too long to run. So they are commented out at the moment. We need to be smarter with the tests we write so that we can still test everything without computing for too long.

Now that Makie.jl has support for text input boxes,
we should use those to replace the current boxes that just state the
values of the limits (so that users can choose exact limits)

https://makie.juliaplots.org/stable/examples/layoutables/textbox/