The documentation equates two kinds of attribute declarations:

explicit:

 class Derp:
    attribute: int = 1

    @property
    def property(self) -> int: ...

and implicit:

  class Derp:
    def __init__(self):
       self.attribute: int = 1

Those two things are not about explicit v

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

Description

I created a Google Codelab tutorial as a research assistant for a professor using mythril and he said it was okay to share. The tutorial leads someone on how to use mythril in Docker and on the CLI on a Google Compute instance. Feel free to use or modify as you please.

Here is the [link](https://docs.google.com/document/d/1_RbrfiCxl3sqbOAxffoiLmA7cq67Khe-lLyvxMuEZbw/edit?usp=sha

Our documentation site is always lagging behind as updating the docs is a non-trivial task that has to be automated. Setting up the Travis job for building wouldn't be trivial (we probably won't fit into the time constraints), but we can use GitHub actions and host a documentation builder on one of our servers. We shall update both bap documentation and Primus Lisp docs.

Craft an extended version (or extend the existing version) of the IDE linear constant propagation.

A constant propagation is often used as a helper analysis for some more advanced data-flow analyses that may spawn their own analyses in order to obtain additional information.

The current version of the IDE-LCA is only concerned with integer types. However, having information on constant float

At least, add winners:

• vampire,
• veiT,
• Redlog,
• SMTInterpol,
• CaDiCaL,
• MinkeyRink,
• COLIBRI,
• AProVE.

Hi,

I have noticed that one need to use AnalysisScope and ClassHierarchy several times to create a call graph. Like follows:

AnalysisScope scope = AnalysisScopeReader.makeJavaBinaryAnalysisScope(classPath, exFile);
ClassHierarchy cha = ClassHierarchyFactory.make(scope);
Iterable<Entrypoint> entrypoints = new AllApplicationEntrypoints(scope, cha);
AnalysisOptions options = new Analy

I noticed you have a plugin for Ghidra, but it is not the only one FOSS tool available.
Radare2 is a highly-portable cross-platform reverse engineering framework and a toolkit without dependencies. It has support for analyzing binaries, disassembling code, debugging programs, attaching to remote GDB/LLDB, WinDbg servers, rich plugin system (see r2pm), an

If an undefined function has a standard name (like printf), should we check also the prototype to increase the confidence that we really may assume that the function behaves like the standard function?

We want to auto-generate a website that documents all the supported patterns of ReqAnalyzer and their countertrace formulas.

It would be even better if we would generate pictures of automata and/or timing diagrams.

siderophile will currently output something like

<http::uri::scheme::Scheme as HttpTryFrom<&'a[u8]>>::try_from

or

<futures_io_preview::if_std::Pin<&'amutT> as AsyncRead>::initializer

The lifetime 'a should not be present, and there should be a space between mut and T.