dataflow

The problem

The current implementation of processElement

1. Check if cache existence for input
2. If the cache returns value return it
3. otherwise, aquire a semaphore
4. call asyncLookup and pass it input. It return a future: F
5. Maintain a list of the currently executing futures
6. release a semaphore at the end each future execution
7. make sure all the future are com

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.

As reported by @jonalv , it can be confusing what is happening when if the globber pattern does not catch any files.

The suggestion is to:

• Log when the globber starts, with the pattern used
• Issue a warning if the globber doesn't match any files at all

unsafeOffset :: Int -> Array.Array a -> Array.Array a

and

unsafeCut :: Int -> Array.Array a -> Array.Array a

or,

unsafeSlice :: Int -> Int -> Array.Array a -> Array.Array a

@harendra-kumar Thoughts?

"AA03": { "description": "Weakness in SSO Authorization", "source": (Process, Element), "target": (Process, Server), "condition": "target.implementsAuthenticationScheme is False", },

What if the Process implements BasicAuth or uses mutual TLS (neither of which is SSO)?
If the Process uses SAML or OAuth, then maybe.
Maybe authenticationScheme as a string var is neces

FINN has a Vivado version requirements, e.g. 2019.1 in the 0.2b release. The available Vivado version should be checked before any Vivado-related commands are launched, and an assertion should be raised if there is a version mismatch.