Results for: "Data"

Creates a self-signed certificate with an issuer and subject of subject and the given extensions for the key.

Creates a self-signed certificate with the given number of bits, the issuer cn and a comment to be stored in the certificate.

Creates a self-signed certificate with the given number of bits, the issuer cn and a comment to be stored in the certificate.

Pushes a new {DependencyState}. If the {#specification_provider} says to {SpecificationProvider#allow_missing?} that particular requirement, and there are no possibilities for that requirement, then ‘state` is not pushed, and the node in {#activated} is removed, and we continue resolving the remaining requirements. @param [DependencyState] state @return [void]

Whether to expect full paths in default gems - true for non-MRI ruby implementations

Is there a path from ‘self` to `other` following edges in the dependency graph? @return true iff there is a path following edges within this {#graph}

Sets up the resolution process @return [void]

@return [Conflict] a {Conflict} that reflects the failure to activate

the {#possibility} in conjunction with the current {#state}

Indicates progress roughly once every second @return [void]

Add the current {#possibility} to the dependency graph of the current {#state} @return [void]

Detaches the {#vertex_named} ‘name` {Vertex} from the graph, recursively removing any non-root vertices that were orphaned in the process @param [String] name @return [Array<Vertex>] the vertices which have been detached

Determines whether the given ‘requirement` is satisfied by the given `spec`, in the context of the current `activated` dependency graph.

@param [Object] requirement @param [DependencyGraph] activated the current dependency graph in the

resolution process.

@param [Object] spec @return [Boolean] whether ‘requirement` is satisfied by `spec` in the

context of the current `activated` dependency graph.