filibuster-testing / filibuster Goto Github PK

Why do the failures in TestExecution contain the arguments to the call but omit the module/method? (also, maybe none of these are needed, including args, since the execution index is there -- should be enough?)

The TestExecution inside of the counterexample.json file is encoded to JSON string and stored inside of the counterexample as a serialized JSON string, meaning, that it's serialized JSON inside of serialized JSON. Fix this by preventing the double serialization and update all client libraries accordingly.

This is the next bit of work to setup the infrastructure you will be working on.

see: https://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/redis/redis.html

• add required imports and verify that it works
• fork this instrumentation by copying the necessary files (look at requests for an example) and place in this repo, rename instrumentor
• modify cinema-15 to use the forked versions in the same way we do the flask and requests instrumentation

Port over the suite that runs on the corpus as for a CI suite for this repository from the research repository.

For this example, it would be best to work with cinema-11 in the Filibuster Research Corpus.

General thoughts:

• Modify movies to use Redis.
  • Any use of files should be modified to use Redis.
• Modify bookings to use Redis.
  • Any use of files should be modified to use Redis.
  • API provides an update function -- that modifies global state and should instead use Redis.
  • Put a circuit breaker around the function that performs the GET/POST similar to the examples already in cinema-11.
• Modify users to use Redis.
  • Any use of files should be modified to use Redis.

We should try to pick a Redis client that has opentelemetry instrumentation for Python, if possible. This would be the same as we did for the requests instrumentation.

This needs to be done for soundness.

Determine if the static analysis can identify whether or not there is any error handling code that is conditional on the type of error: for example, if a service contains a catch all for all error types, then we don't need to test all possible error types from the dependent services, only to that service.