fix: add slither disable after slither actions update
- We have always been ok with risk here and ensured this won't happen for our use case, but slither actions version was recently updated so this fails in CI.
This commit is contained in:
@@ -62,7 +62,7 @@ contract Dispatcher {
|
|||||||
revert Dispatcher__UnapprovedExecutor();
|
revert Dispatcher__UnapprovedExecutor();
|
||||||
}
|
}
|
||||||
|
|
||||||
// slither-disable-next-line controlled-delegatecall,low-level-calls
|
// slither-disable-next-line controlled-delegatecall,low-level-calls,calls-loop
|
||||||
(bool success, bytes memory result) = executor.delegatecall(
|
(bool success, bytes memory result) = executor.delegatecall(
|
||||||
abi.encodeWithSelector(IExecutor.swap.selector, amount, data)
|
abi.encodeWithSelector(IExecutor.swap.selector, amount, data)
|
||||||
);
|
);
|
||||||
|
|||||||
Reference in New Issue
Block a user