Abstract: According to examples, an apparatus may include a processor and a memory on which are stored machine-readable instructions that when executed by the processor, may cause the processor to receive a request from a client for a status of the client, and based on the status of the client, generate a token associated with application programming interface (API) calls to be received from the client. In some examples, the token may include a value representing a priority for determining an adaptive rate limiting of the API calls to be received from the client. The processor may send a response to the request, in which the response may include the status of the client and the token.

Abstract: A method for the sonification of continuous integration data to audibly represent the health/behavior of builds. The method includes receiving, by a processor, from a build server, continuous integration data for a build job in the continuous integration environment. The method also includes converting, by the processor, the continuous integration data into sonification data. The method further includes applying at least one of toccata, legato, or arpeggio to the sonification data. The method includes generating an audio file from the sonification data; and publishing and/or storing the generated audio file for end users. In some embodiments, the method also includes combining, by the processor, different sets of sonification data, wherein each set of sonification data is associated with a different build job, and wherein each set of sonification data is represented by a different instrument of a plurality of instruments.

Abstract: Quality indicators regarding a software project under development that has a plurality of functional areas are collected. Each quality indicator is normalized to a coverage of the functional area of the software project to which the quality indicator corresponds. The normalized quality indicators are correlated to previously identified anomalies of the software project, yielding an anomaly indicative value for each normalized quality indicator corresponding to a probability that the normalized quality indicator is revelatory of unidentified anomalies of the software project. A normal behavior for each normalized quality indicator is estimated. For each functional area of the software project, an anomaly score indicative of a likelihood of an unidentified anomaly within the functional area is calculated.

Abstract: Subsequent to registration of a client device with a server device such that credentials by which the client device is authenticated are securely stored at the client device, the client device provides a user device and a server device a recovery identifier and a recovery secret key associated with the client device. Upon the credentials no longer being stored at the client device such that the client device has to be reregistered with the server device to store new credentials by which the client device is authenticated, the user device generates and provides a recovery code to the client device, which provides the recovery code to the server device. Upon validating the recovery code based on the recovery identifier and the recovery secret key, the server device reregisters the client device with the server device such that the new credentials are securely stored at the client device.

Abstract: A transaction block in a blockchain is generated. The transaction block in the blockchain comprises a token that points to blockchain data in a tokenization table. An event is detected (e.g., an administrative event). The event is to forget the blockchain data in the tokenization table. In response to detecting the event, the blockchain data in the tokenization table is forgotten. For example, forgetting the blockchain data may comprise permanently deleting the blockchain data in the tokenization table and/or permanently deleting an encryption key for the blockchain data in the tokenization table.

Abstract: An event is identified. The event is associated with device content (e.g., one or more files) and a network location (e.g., a branch location of a corporation). One or more rules are retrieved. The one or more rules are associated with the device content, the network location, and a number of communication devices at the network location. A number of shards (e.g., erasure encoding shards) are determined based on the rules. The number of shards are generated. The number of shards are sent to a plurality of communication devices at the network location according to the rules. The plurality of communication devices at the network location are equal to or less than the number of communication devices at the network location.

Abstract: The present disclosure is to determine a probable root cause of a performance issue. For example, a method can include processing, using a processor, a set of calls for a Hypertext Transfer Protocol (HTTP) transaction wherein individual calls of the set of calls have a set of parameters; and identifying, using the processor, that the HTTP transaction has a performance issue that falls below a predetermined level of a performance metric. Further steps can include separating, using the processor, the set of calls into a first group with the performance issue and a second group without the performance issue; discovering, using the processor, a common subset of parameters among the first group; and determining that the common subset of parameters is a probable root cause of the performance issue if the common subset of parameters is not found in the second group.

Abstract: The design for modern graphical interfaces generated by an application under test (AUT) can take many forms. A codeless testing system reads the output generated by the AUT to identify components, however, scroll bars may be present but in a form that is not reliably identified. As a result, an AUT may comprise scrollable graphical elements that are not identified as such resulting in the performance of tests that are incomplete. By applying a middle button click event, an associated pointer changes form and reveals an associated graphical element to comprise a scrollable element. When the pointer change occurs, testing directed to the scrollable element is then included to perform a more complete testing of the features of the AUT.

Abstract: Examples relate to detecting an abnormality. The examples disclosed herein enable receiving, from a first user, a first request to perform a first transaction on at least one data record. A plurality of transactions originated from the first request may be organized in a first hierarchical tree-based data structure having multiple depth levels. The data structure may comprise a root node representing the first transaction and a leaf node representing a second transaction. The examples further enable detecting the abnormality based on at least one parameter where the at least one parameter comprises a size of the data structure and a depth level associated with the leaf node.

Abstract: An event is detected. The event is a designated event for capturing a snapshot of a blockchain where the blockchain is not replicated in a distributed ledger. For example, the event may be where a specific number of new blocks have been added to the blockchain. In response to detecting the event, a capstone block or a lock block is created. The capstone block or the lock block is added to the blockchain. A copy of the capstone block or the copy of the lock block sent to a trusted authority. The copy of the capstone block or the copy of the lock block is used to validate some or all the blockchain to detect if the blockchain has been changed. For example, validating the blockchain may be to detect if the blockchain has been tampered with or has become corrupted.

Abstract: A self-contained validation process is initiated. For example, an application may contain code to initiate the self-contained validation process. The self-contained validation process comprises at least one of: a self-contained application validation process, a self-contained container validation process, a self-contained virtual machine validation process, and a self-contained hypervisor validation process. In response to initiating the self-contained validation process, the self-contained validation process requests a list of vulnerabilities associated with the self-contained validation process. The list of vulnerabilities associated with the self-contained validation process is received. For example, the received list of vulnerabilities may identify a security vulnerability in the application. An action taken based on the received list of vulnerabilities associated with the computer process. For example, the application may self-quarantine itself based on the received list of vulnerabilities.

Abstract: A first message is received from a first communication device. The first message comprises an authentication token. For example, the authentication token may be a username/password. A determination is made if the first message also comprises a valid temporary password. The temporary password is used to prevent a Denial-of-Service (DOS) attack. In response to the first message comprising the valid temporary password, a determination is made if the authentication token is valid. In response to the authentication token being valid, the first message is responded to in a normal manner. If the first message does not contain the temporary password, the first message is handled based on a DOS message handling process.

Abstract: A computer implemented method includes: accessing from a configuration management database, by a virtualization manager, configuration data for a first computing node of a computing system; generating, by the virtualization manager, a set of attribute/value pairs for the first computing node using the configuration data; and managing, by the virtualization manager, a first container on the first computing node using the set of attribute/value pairs for the first computing node.

Abstract: A shard of a selected document is identified. A hierarchy of documents including the selected document are to be tagged with metadata in a data store of a search engine so that the related documents are queryable by the metadata using the search engine. The shard specifies a location of the related documents within the data store of the search engine. For each related document, a tagging operation is generated within a script, the tagging operation specifying the metadata, the shard, an identifier of the related document, and an identifier of the selected document. The script including the generated tagging operation for each related document is transmitted to the search engine to execute to tag the related documents in the data store with the metadata and with the selected document as a source of the metadata.

Abstract: A request to install a first version of a software application is received. The first version of the software application is stored in a first blockchain in a first distributed blockchain ledger. In response to receiving the request to install the first version of the software application, the first version of the software application is validated by running a hash of the first blockchain. In response to validating the first version of the software application, the first version of the software application is installed from the blockchain to a device. The software application may also be validated after being installed to the device.

Abstract: A non-tokenized string is received. For example, a non-tokenized string could be a credit card number. The non-tokenized string is partitioned into a plurality of non-tokenized substrings. For example, if the credit card number is 16 digits long, it may be partitioned into substrings that are three, six, and seven digits in length. The non-tokenized substrings are used as an index into a plurality of lookup tables. As a result of the indexing, a plurality of tokenized substrings are retrieved. The plurality of tokenized substrings are combined into a tokenized string. The tokenized string is used as a token that represents the credit card number without disclosing the actual credit card number. The reverse of the above process can also occur.

Abstract: A computing device includes a processor and a machine-readable storage storing instructions. The instructions are executable by the processor to: receive a bit vector representing input data to be tokenized; divide the bit vector into two vector portions; and perform a plurality of rounds of a Feistel network on the two vector portions, each round including converting one vector portion using a table-based hash function that combines multiple tokens retrieved from at least one token table.

Abstract: A synchronization structure that indicates changes to files that are to be synchronized is created. The synchronization structure is stored as a series of synchronization blocks. A first synchronization message is received from a communication device. The first synchronization message includes a next block number. A second synchronization message is sent to the communication device. The second synchronization message comprises one or more synchronization blocks that are identified based on the next block number. A third synchronization message is received from the communication device. The third synchronization message requests a number of files to be synchronized. The number of files to be synchronized are sent to the communication device.

Abstract: A system includes a processor and a memory coupled with and readable by the processor and storing therein a set of instructions. When executed by the processor, the processor is caused to receive application events associated with an application and create data records based on the application events. The processor is further caused to compute an interestingness value for each of the data records based on a goal of the application, assign the computed interestingness value to each of the data records and store each of the data records with the assigned interestingness value.

Abstract: Results of an authentication process are received. The authentication process allows for a graded level of authentication using a plurality of authentication types (e.g., a username/password and a fingerprint scan). Encrypted data is then accessed. The encrypted data has been encrypted using a plurality of encryption levels. The data is unencrypted based on the graded level of authentication. In a second embodiment, a system and method are provided that establish a communication session (e.g., a voice or email communication session). The communication session is between a plurality of users. During the communication session, an indication is received to change an encryption level for the communication session. In response to receiving the indication to change the encryption level for the communication session, an encryption level of the first communication session is dynamically changed from a first level of encryption to a second level of encryption.