This is follow up of #1969 intended as a discussion on how this rule should behave.
It would be great if @jfoug and/or @magnumripper would join so we can battle it out and make it consistent between hashcat and john.

As I mentioned in the original report I assumed that given the input word foobar and the rule ef the mangled output should be FOobar. This is based on my first thought when

As documented in #5392 using the packages for tflite and tensorflow 2.1.0 the test as in the subject line segfaults. It has now been skipped in the testsuite but this needs to be fixed.

See #4243. We can use hccap/hccapx files, but normally I'd recommend using wpapcap2john if you do have a pcap at all. That, or (possibly even better) something from hcxtools which we could also mention (Zerobeat's hcxdumptool is the absolute best sniffer for WPA as well).

As of 00e1f52cf95c16b0cea34c83372145532b4745ba the LWJGL codebase has a new directory layout. This has broken the included Eclipse project.

https://01.org/dnnl

The project was initially launched as Intel Math Kernel Library for Deep Neural Networks (Intel MKL-DNN) and renamed to DNNL with v1.1 release.

It looks like the website could use an update for the latest rename to oneDNN.

Tools such as gofmt are very useful for quickly cleaning reformatting code according to some coding style. I think we need the same for Futhark. It's a bit more complicated to do this for an expression-oriented language than a statement-oriented one, but there is prior art we can look at (like Brittany for Haskell).

While constructing futhark fmt i

Images about preformance are missing in boost page documentation http://www.boost.org/doc/libs/1_61_0/libs/compute/doc/html/boost_compute/performance.html

Looks like there's no example using vector types defined in cltypes while the doc itself for these types are not so understandable. There are many examples having kernels taking vector type arguments, but the python code is using the numpy type, instead of the defined vector type. E.g. https://github.com/inducer/pyopencl/blob/master/examples/demo_elementwise_complex.py

The docs generated for #431 at https://mratsim.github.io/Arraymancer/pca.html have broken formatting:

• Upstream bug on the type:
  
• Random bolding:
  and
  ![image](https:/

Closely related to #52 but it might be nice if there was a sort of translation table for people coming from Matlab:

The current behaviour of glossy and glossycoating is to behave like matte on the backface.
I can't think of a good reason for this, and it is very confusing for users, so I would like to request to rework these materials to show their coating on both front and back faces.

(intended for v2.4)

Want to back this issue? **[Post a bounty on it!](https://www.bountyso