117 results about "Multiple version" patented technology

A method of code vulnerability detection includes obtaining a set of patches from at least one code repository for a vulnerability record of a vulnerability of a software component, applying the set of patches to obtain a modified set of code files modified by the set of patches, and inferring a vulnerable code section set according to the modified set of code files. The vulnerable code section set is a subset of the modified set of code files. The method further includes obtaining a vulnerable version list of a plurality of versions of the software component comprising the vulnerability, validating a version in the vulnerable version list as having the vulnerable code section set, and processing a target software comprising the version using the vulnerable code section set.

Disclosed herein are system, method, and computer program product embodiments for detecting anomalies during software testing. The methods include generating a plurality of test reports for the software program by executing one or more test cases on a plurality of versions of the software program, generating a control chart based on the plurality of test reports, generating an alert when at least one testing characteristic includes an anomaly over the plurality of versions of the software program as determined based on the control chart. The control chart includes a plot associated with at least one testing characteristic of the software program, and a historical context associated with execution of the one or more test cases on the plurality of versions of the software program.

The invention provides a multi-version dynamically expandable data source method and device, a terminal and a storage medium, and relates to the technical field of database data source loading. The method comprises the steps that a JAVA SDK package is created, the JAVA SDK package comprises core dependence, a core entity class, a core interface class, a database connection pool management core class, thread isolation, a routing data source class and basic attributes and target data source mapping of the routing data source class, and the target data source mapping is used for storing a loaded database connection pool; initializing a system database connection pool in the application system based on a JAVA SDK packet; after a system database connection pool in an application system is initialized, a new database connection pool is dynamically expanded in the application system based on a JAVA SDK package. The system has the design characteristics of strong dynamic expansion capability and loose coupling, the flexibility and expansibility of the system can be greatly improved, and the development and maintenance cost is reduced.

A method is disclosed. The method comprises detecting one or more vulnerabilities in a software package, generating a version upgrade recommendation for each of the detected vulnerabilities, generating a version graph including one or more of the version upgrade recommendations and displaying the version graph at a user interface.

An automated identification of vulnerable software components is presented. The objective to find a method for the automatic identification of CVE affected software components through source-code parsing and text analysis. The method shall reduce manual work to a minimum and ensure a high level of data quality. The objective is solved by the computer-implemented method for identifying vulnerable software, comprising: receiving a software package; unpacking source code files for multiple versions of the software package; retrieving an entry for the software package from a vulnerability database; retrieving a patch for the software package; determining changes made by the patch to source code files of the software package; and determining whether the changes were made to a given version of software and reporting the given version of software as vulnerable in response to a determination the changes were absent from the given version of software.

The invention discloses a file metadata multi-version storage management method and device, computer equipment and a storage medium. The method comprises the steps of obtaining file metadata; in response to the received generation instruction, generating a snapshot version for the file metadata to obtain a snapshot version set; extracting a first snapshot version and a second snapshot version from the snapshot version set, updating the snapshot version set, and storing the snapshot version set in a memory area; packaging the file metadata, the first snapshot version and the second snapshot version to obtain a coded data structure, and storing the coded data structure in a memory area; storing the updated snapshot version set and the coded data structure in a storage device; querying the memory area according to the query instruction, querying the storage device if the query fails, and returning a query result; by means of the method, decoupling storage of multiple versions of file metadata can be achieved, and the system memory utilization rate and the snapshot version management efficiency can be improved.

Various systems and methods are presented regarding using generative artificial intelligence / machine language (AI / ML) to resolve a merge conflict between two or more versions of a program code. The program code can be industrial automation software utilized to control one or more PLCs in an industrial environment. Interaction with the program code can be via a programming tool that presents the program code in a human readable format, while the AI / ML can be applied to the underlying source code. Hence, while the source code is applied to the PLC, the programming tool enables interaction various human readable summaries of the program code and respective options available to resolve the merge conflict. Accordingly, a process engineer, or suchlike, does not have to be familiar with the source code format to readily understand a summary of the merge conflict or one or more options available to correct the conflict.

A database business system upgrade management method, apparatus, device and medium, the method comprising: creating a fixed version table in a database, the version table comprising a table field for storing a version number of a current database structure; wherein the initial value of the table field is set to be 1, and 1 is increased progressively after upgrading is successfully completed every time; each program version is upgraded, and if the database structure is changed, an upgrading file is newly added; database upgrading: querying the version table before upgrading, and obtaining the current version number recorded in the database; traversing the names of all the upgrade files, and if the upgrade file of the next version of the current version number exists, executing the upgrade file; if the execution of the upgrade file fails, the upgrade fails; and if the database upgrade fails, querying the version table, obtaining the current database version number according to the table field in the version table, and carrying out a rollback operation. According to the method, one-time upgrading across multiple versions can be realized, and the actual version state of the database can be quickly confirmed.

A method of code vulnerability detection includes obtaining a set of patches from at least one code repository for a vulnerability record of a vulnerability of a software component, applying the set of patches to obtain a modified set of code files modified by the set of patches, and inferring a vulnerable code section set according to the modified set of code files. The vulnerable code section set is a subset of the modified set of code files. The method further includes obtaining a vulnerable version list of a plurality of versions of the software component comprising the vulnerability, validating a version in the vulnerable version list as having the vulnerable code section set, and processing a target software comprising the version using the vulnerable code section set.

The invention discloses an acquisition protocol multi-version application method and system, and relates to the technical field of big data acquisition, and the method comprises the steps: adding a version number identifier to an acquisition protocol and each field in the acquisition protocol; the collection SDK compares the version number of the collected data with the collection protocol metadata, marks a corresponding version number on a corresponding field and reports the version number; the cloud side correspondingly stores the field version numbers into a wide table database according to the field version numbers; and the application layer selects available version number field data as required. When an acquisition protocol is created or updated, all fields are numbered by independent versions, the versions are controlled to be fine-grained, and field data corresponding to the version numbers can be freely selected when using data is applied; unified processing is carried out according to the field version number during cloud cleaning and warehousing, iterative development does not need to be carried out on an old version cleaning and warehousing process, and manpower is saved; in the storage stage, other fields which are not modified and updated in the same protocol do not need to be additionally and repeatedly stored due to consideration of old version data value, so that the storage space is greatly saved.

The invention discloses a multi-version space-time consistency verification method and system for a test case and a medium, mainly relates to the technical field of test cases, and is used for solving the problem of low efficiency of large-scale data verification due to multi-focus time or space single-dimension verification in the prior art. Comprising the following steps: randomly extracting a preset number of analysis nodes from a plurality of deployment nodes, and obtaining formula programs of test cases on the analysis nodes; extracting a preset non-core formula program and all preset core formula programs in a preset proportion, and comparing output data of the preset non-core formula program with output data of all the preset core formula programs to obtain a comparison result; comparing the sampling similarity of the sampling data in the same automatic comparison combination through the deployment nodes in the same automatic comparison combination; sampling similarities corresponding to all the automatic comparison combinations are obtained; and determining that multiple versions of the test cases involved in the automatic comparison combination with the sampling similarity greater than a preset similarity threshold are consistent in time and space, otherwise, inconsistent in time and space.

The invention discloses a system call hijacking method and device compatible with multiple versions of Linux kernels, a first hijacking channel and a second hijacking channel are deployed in parallel in a target version of Linux kernel in advance, the first hijacking channel is adapted to a Linux kernel version executing system call through a system call table, and the second hijacking channel is adapted to a second hijacking channel which is adapted to a Linux kernel version executing system call through a system call table. The second hijacking channel is adapted to a Linux kernel version which executes system calling through a system calling distribution function, and the method comprises the following steps: in response to a system calling request, hijacking the system calling request to a pre-defined target address through a target hijacking channel which actually takes effect in a Linux kernel of a target version, determining a corresponding target function based on the target address; sorting system call parameters carried in the system call request into a data format required by a preset hook entry function through a target function, and sending the data subjected to format sorting to the hook entry function; and determining a security processing strategy for the system call request through a hook entry function on the basis of the formatted data.

In some implementations, a user device may transmit, to the package repository, a request for a code package. The user device may receive, from the package repository, an indication of a plurality of versions of the code package. The user device may receive, from the package repository, an indication of a suggested version from the plurality of versions. The suggested version is based on automatic testing of the code package by the package repository. The user device may transmit, to the package repository, a request for the suggested version. The user device may receive, from the package repository, at least one file included in the suggested version.

The invention discloses a cache data management method and electronic equipment, and relates to the technical field of computers.The cache data management method includes the steps that a hash table is arranged in a cache system, multiple version nodes corresponding to the same data identifier are organized into a version linked list, new version nodes are added into the linked list when new data are written, and old versions are not covered; and the system can perceive and manage multi-version data. And meanwhile, comprehensive judgment is performed by combining the popularity information of the version nodes and the positions of the version nodes in the version linked list, and the oldest version nodes with low popularity are selectively eliminated when the cache space is insufficient. In this way, the cache system can keep the hot data to the maximum extent, it is ensured that the old version data is reasonably eliminated, the accuracy of elimination of the cache data is improved, the situation that the hot data are mistakenly deleted is avoided, and therefore the consistency of data access and efficient operation of the whole system are guaranteed.

Disclosed are a method and a system for changing a database schema. The method comprises receiving a request to make a set of changes to a first version of the database schema of a database, and creating, based on the set of changes to the first version, a conversion rule for converting data records maintained by the database between the first version and a second version of the database schema. The second version results from the application of the set of changes to the first version of the database schema. The method further comprises storing the conversion rule for retrieval when performing data operations on the data records in accordance with any database schema version in a set of supported versions comprising the first version and the second version of the database schema. Also disclosed are methods and systems for performing data operations on databases supporting multiple versions of a database schema.

Provided are systems and methods that facilitate the upgrade of multiple versions of a software application within a containerized environment. In one example, the method may include importing a software update of a software application into a prior version of the software application in a containerized environment, executing a test of the prior version of the software application with the software update included therein via the containerized environment and display results of the execution of the test via a user interface, modifying the prior version of the software application with the software update included therein while the prior version of the software application with the software update included therein is within the containerized environment, and delivering an instance of the modified prior version of the software application from the containerized environment to a productive environment.

The embodiment of the invention provides a version release method and device, equipment, a storage medium and a program product, and relates to the field of financial science and technology. According to the invention, a version release mechanism which associates and updates two release branches and realizes release in the same window is constructed, and the current version packages of different release branches can be released in the same production window, so that the limitation that multiple versions cannot be released in the same production window in the prior art is broken through; the method not only ensures coordination and code consistency of release of different versions, but also improves version release efficiency, is particularly suitable for software research and development scenes needing to maintain multiple associated versions at the same time, can realize efficient synchronous release of multiple versions on the premise of not increasing extra risks, and improves the development efficiency of software development. And a more flexible and reliable solution is provided for software development management.

The invention discloses a cross-version vulnerability recognition system based on a depth map neural network, and the system comprises a multi-version code metadata collection module which is used for collecting software source codes of multiple versions and analyzing the software source codes to generate a multi-version code metadata set; the multi-version code graph generation module is used for constructing a multi-version code graph set; the feature representation matrix generation module is used for generating a feature representation matrix of the multi-version code graph; the depth map neural network modeling module is used for obtaining an embedded matrix of each node by adopting a GLEM model; the potential vulnerability node identification module is used for identifying a cross-version potential vulnerability node set; and the result output module is used for outputting a cross-version vulnerability identification result and generating a detection report. According to the method, the depth map neural network and the cross-version modeling method are adopted, multi-version vulnerability automatic recognition is achieved, and the method has the advantages of being high in intelligence, high in adaptability and accurate in detection.

In some aspects, the techniques described herein relate to systems (130) and methods (200; 300) for determining versions of a software application that are affected by a vulnerability including: receiving an indication of a detected vulnerability in a first version of a software application by a computing device (201); in response to the indication of the detected vulnerability, generating a tree representation of the first version of the software application by the computing device (203); retrieving a plurality of versions of the software application by the computing device (301), wherein each of the plurality of version is different than the first version; for each version of the software application of the plurality of versions of the software application, generating a tree representation of the version of the software application by the computing device (303); and based on the generated trees, identifying at least one version of the plurality of versions of the software application that may include the detected vulnerability by the computing device (307).

Embodiments of the present invention provide a system for dynamically generating automation test scripts for software applications comprising multiple versions. The system is configured for identifying a new version of a software code associated with a software application in a code repository in a software development environment, scanning the new version of the software code, identifying new changes to the software code based on scanning the new version of the software code, analyzing the new changes to determine impact associated with the new changes, determining a first set of new changes from the new changes that have an impact on an automation base repository associated with testing the software code, identifying locators associated with the first set of new changes, dynamically creating a new version of a test repository corresponding to the new version in the code repository, and updating the new version of the test repository with the locators.

The invention discloses an automatic construction method of an APK file and a related product. According to the method, firstly, a user construction demand and an APK code corresponding to the user construction demand are obtained, the code comprises application module codes of multiple versions, and the application module codes comprise a bottom layer package code and an HMI code. And then version filtering is carried out on the APK code based on a user construction demand to obtain a target code. And then interface consistency verification is carried out on an interaction interface of the bottom layer package code and the HMI code in the target code. And if the verification is passed, querying a construction workflow matched with the construction demand of the user in the knowledge graph to obtain a target workflow. On this basis, according to the target workflow, bottom layer package codes and HMI codes in the target codes are called and compiled in order, and an APK file matched with the construction requirement of the user is generated. According to the method, the automation level and accuracy of APK construction are greatly improved, and the problems of manual operation errors and version compatibility are reduced.

The invention discloses a processing method for coexistence of multiple versions of project software, which comprises the following steps of: defining a namespace and a routing rule, and mapping requests of different versions to corresponding service instances; differentiating versions based on the URL, HTTP header, or client identification; according to the dynamic request feature, the flow direction of the request is determined based on a load balancing algorithm, the project software multi-version coexistence processing method provides options of multiple versions for users at the same time, the learning cost and the pressure of adapting to new functions are reduced, the anti-risk capacity of software during updating is improved, and stability and safety are high.

The application discloses a kind of cross-version vulnerability identification systems based on depth map neural network, comprising: multi-version code metadata acquisition module, for collecting multiple versions of software source code and parsing generation multi-version code metadata set;Multi-version code graph generation module, for constructing multi-version code graph set;Characteristic representation matrix generation module, for generating the characteristic representation matrix of multi-version code graph;Depth map neural network modeling module, for using GLEM model, obtains the embedding matrix of each node;Potential vulnerability node identification module, for identifying the potential vulnerability node set across version;Result output module, for outputting cross-version vulnerability identification result and generating detection report.The application adopts depth map neural network and cross-version modeling method, realizes multi-version vulnerability automatic identification, with the advantages of strong intelligence, high adaptability, detection precision.

The present invention discloses a key management system based on version management, comprising: a cryptographic device and a key backup central server; the cryptographic device comprises: a key card, which is used to generate keys of different version numbers according to a time baseline in a hardware security environment, and encrypt the keys of different version numbers through a device key; a local key synchronization service module, which is used to detect key changes and synchronize them to a central server; a key backup central server, which stores the key version directory and encrypted key files of all devices; the cryptographic device and the key backup central server communicate via a network to achieve two-way synchronization of key version data, support the selection of multiple version keys for merge recovery, and resolve index conflicts through hash comparison. The present invention manages the key life cycle of the cryptographic device based on the version number, making the management work clearer; multiple version key backups can be used for fusion recovery to meet more key recovery scenarios.

The application discloses a cloud platform-based upgrade test method and device and a medium, and is suitable for the technical field of software testing. An upgrade test path is determined according to an initial version and a target version, and a test configuration file is obtained according to the upgrade test path and corresponding test scale and test scene combination; an initialization test environment is accessed, a corresponding script configuration file is selected according to the target version to obtain a use case function set, and upgrading is performed according to the upgrade test path and the use case function set. The test configuration file is obtained through the determined upgrade test path, then the cloud platform is configured to create the initialization test environment to specify the version system file, the use case function set suitable for the target version is selected according to the version function difference, and the upgrade package is uploaded and upgraded according to the use case function set and the upgrade test path. The version can be upgraded level by level, the cross-version upgrade of multiple versions can be realized, the upgrade speed is improved, and the version of the upgrade test is relatively flexible.

Computing systems, for example, multi-tenant systems deploy software artifacts in datacenters created in a cloud platform. The system receives multiple version maps. Each version map provides version information for a particular context associated with the datacenter. The context may specify a target environment, a target datacenter entity, or a target action to be performed on the cloud platform. The system generates an aggregate pipeline comprising a hierarchy of pipelines. The system generates an aggregate version map associating datacenter entities of the datacenter with versions of software artifacts targeted for deployment on the datacenter entities and versions of pipelines. The system executes the aggregate pipeline in conjunction with the aggregate version map to perform requested operations on the datacenter configured on the cloud platform, for example, provisioning resources or deploying services.

The invention relates to a method and a device for integrating multi-version demand documents and computer equipment, and relates to the technical field of computers, and the method in one embodiment comprises the following steps: obtaining multi-version demand documents of a target system, and sorting the multi-version demand documents based on the latest update time of the demand documents to obtain a demand document sequence; structural analysis is conducted on the demand documents of all the versions, the content of the demand documents is disassembled into structural knowledge units, and each knowledge unit comprises an independent function point and corresponding attribute information; determining knowledge units describing the same function point in the demand document of each version, and associating the knowledge units describing the same function point in the demand document of each version based on the demand document sequence to form a knowledge unit change chain; and generating an integrated demand document based on the knowledge unit change chain of each function point. By adopting the scheme of the embodiment, the management efficiency of multi-version demand documents is improved.

Computing systems, for example, multi-tenant systems deploy software artifacts in datacenters created in a cloud platform. The system receives multiple version maps. Each version map provides version information for a particular context associated with the datacenter. The context may specify a target environment, a target datacenter entity, or a target action to be performed on the cloud platform. The system generates an aggregate pipeline comprising a hierarchy of pipelines. The system generates an aggregate version map associating datacenter entities of the datacenter with versions of software artifacts targeted for deployment on the datacenter entities and versions of pipelines. The system executes the aggregate pipeline in conjunction with the aggregate version map to perform requested operations on the datacenter configured on the cloud platform, for example, provisioning resources or deploying services.

The present disclosure relates to a request-level consistency control method and system for dynamic configuration hot update. The method comprises: organizing configuration content into multiple versioned configuration snapshots, establishing a corresponding reference count for each versioned configuration snapshot, and setting a candidate version; enhancing a configuration reading path in a service node by plugging so as to be able to perform a configuration reading operation according to a bound version; in response to receiving a service request, creating an activation token for the service request, obtaining a current candidate version as the bound version, writing the bound version into the activation token, and increasing the reference count of the bound version; during processing of the service request, when configuration needs to be read, reading a configuration value from a corresponding versioned configuration snapshot according to the bound version in the activation token; and in response to the processing of the service request being completed, decreasing the reference count of the bound version by one.

The application discloses a cross-platform VSTO plug-in development framework and an implementation method for one-time development and multi-version multiplexing, belongs to the technical field of plug-in development, and comprises a bottom-up runtime version detection layer, a reflection calling layer, an abstract interface layer, a platform adaptation layer and a unified interface adaptation layer; wherein the runtime version detection layer is used for automatically identifying a host environment and a specific version of host software when the VSTO plug-in is started, collecting interface rendering parameters and outputting a standardized environment identification tuple. The application provides a compatible framework and a matching unified interface design scheme for "one-time development and multi-version multiplexing", realizes configuration-free installation and interface self-adaptive compatibility of the same plug-in package on Excel 2007-2019 and WPS 2016-2019, greatly reduces compatibility code and interface development costs, and improves plug-in adaptation efficiency, installation success rate and user interaction experience.