rlundeen2
rlundeen2
> > There are multiple ways to do this, but this is how I'd take a stab at it (and one of the ways we'd approve this). If you have...
As part of this, can you take a stab at documenting what we should do? E.g. this is my best stab at a strategy, which is similar to but different...
Can you please run all notebooks before merging to make sure nothing is broken? Make sure to not commit the new notebooks where nothing has changed, but we want to...
Can you make the description and title more specific (e.g. which jailbreaks/papers)
In the meantime, something that may help is using a SQL database. Then you can have multiple instance running but all saving data to the same place
@Siddheshwari19 thanks for your contribution! We merged it from here (so we could avoid conflicts): https://github.com/Azure/PyRIT/pull/517
Thanks @Tiger-Du! As is, mypy will only print those warnings if there is also an error. And you're correct that the additional methods are new warnings. I approved your PR,...
See this change that pinned the dev version: https://github.com/Azure/PyRIT/pull/810
I like this approach. I'm going to update the ticket with some adjustments. Before anyone tackles this I'd love @romanlutz to take a look and help adjust with feedback
Correct, TreeOfAttacks is just one orchestrator now