In the following scenario, replacing the body of Child#one with super causes a SystemStackError when Child#one is being called. However mutant does not detect that this error kills the mutation that replaces the method's body with super. See https://github.com/matthias-g/mutant_super_bug for a running example.

class Parent
  attr_reader :foo

  def initialize(foo)
    @foo = fo

As bundles emerge as the central organizing pattern for Aquameta modules, it's becoming clear that a very common pattern is to reference a row by its bundle name, plus "name", whatever that might be. We do this with widgets already on import, referencing {namespace}:{widget.name} and have a custom function for resolving them. Other places do crude hacks around this missing functionality as wel

To reproduce, run a request to the rdf/cypher endpoint with wrong fields (cypher_wrong instead of cypher).
Example :

curl http://localhost:7474/rdf/cypher -d '{ "cypher_wrong": "MATCH path = ()-[:BY]->()<-[:BY]-() RETURN path LIMIT 1"}' --header "Authorization:Basic ..."

Throws a 500 with an NPE

• Avro-compatibility

• Black Hat USA 2018 Keynote: Parisa Tabriz: Optimistic Dissatisfaction with the Status Quo: Steps We Must Take to Improve Security in Complex Landscapes

• [Apache Beam Capabilities Matrix (good documentation)](https://beam.apache.org/documentation/runners/capability

Principle of Single Inheritance:

_This principle does not prohibit the use of subclass or equivalent class axioms whereby a class is defined to be a subclass or equivalent class of an anonymous class. The OWL language provides the means to express facts about entities using relations to other entities. For example, a fact such as “Automobile has_part some Engine” uses the has_part relation to r

The napoleon extension to Sphinx (which we use for documentation) accepts PEP-484 type hints as well as types in the docstrings. E.g., these are the same:

def foo(a):
    """
    foo the a

    Args:
        a (int): a bar
    """
    return a * 2

def foo(a: int):
    """
    foo the a

• Show positional parameter info whenever a call or return happens
• Show call stack somewhere

Real talk: we should get rid of the JS stateful morass and reimplement this all in Elm. (That's the part that's a "good student project".)

• EXCEL.md specifies that rows should not be reordered, but that only matters for editing the CoNLL-U-Lex directly.

• csv2conllulex.py strips out the header row (#67). We want to keep it for tupdate/supdate.