Abstract: The technology disclosed herein enables retraction of a vehicle midgate into a cavity. In one example, a vehicle includes a passenger cabin, a cargo bed, and a midgate module positioned between the passenger cabin and cargo bed. The midgate module includes a window, and a midgate body. The window is configured to move from a closed position to an open position within a cavity of the midgate body. The midgate body is configured to move from a closed position to an open position within a cavity formed by the passenger cabin.

Abstract: A method and apparatus are disclosed. Some embodiments may include a sun visor configured to be received in a closed position within a recess of a head liner of a vehicle, a fastening component at a first edge of a top edge of the sun visor, configured to fasten the sun visor to the body of the vehicle, and to define an axis around which the sun visor is configured to rotate, wherein the sun visor is configured to rotate from the closed position to an open position by rotating toward a user sitting in a seat within the vehicle. The sun visor may include a second edge at an opposite edge of the sun visor with respect to the first edge of the sun visor, wherein when in the closed position the second edge is configured to be disposed at a non-zero angle away from a horizontal plane.

Abstract: An aspect of the present disclosure is directed to a vehicle comprising a vehicle body; and a front storage module coupled to the front of the vehicle body, the front storage module comprising: a drawer; and a drawer actuator configured to move the drawer from a closed position within a cavity of the vehicle body to an open position at least partially extended from the front of the vehicle body.

Abstract: An aspect of the present disclosure is directed to a vehicle comprising a vehicle body comprising a rear bumper; and a rear end module coupled to the rear of the vehicle body, the rear end module comprising: a rear window, and a rear gate, wherein the rear window is configured to move from a closed position to an open position within a cavity of the rear gate, and the rear gate is configured to move from a closed position to an opening position within a cavity formed by the rear bumper.

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

Abstract: Various embodiments are directed to systems and methods for providing employee data corresponding to individual employees to a customer computing entity operated by a customer. The employee data is provided so as to provide additional detail regarding an employee involved in a customer service interaction with the customer. The employee data is broadcast from an employee beacon carried by a respective employee. The employee data is received by a customer computing entity within the broadcast range of the employee beacon and, upon detection of a trigger event, the employee data is presented to the user via a graphical user interface of the customer computing entity, which requests that the customer provide feedback data regarding the employee, which may be transmitted to a management computing entity for storage and analysis.

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

Abstract: According to some implementations, while a proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (cos) pods having first app version containers, configuration information is received including an identification of a second app version container image for a second app version. The second app version is an updated version of the first app version. Cos pods having second app version containers are brought up based on the second app version container image identified in the configuration information. Test and/or warmup traffic is caused to be routed to the second app version containers. Responsive to an indication regarding the routing of the test and/or warmup traffic to the second app version, causing a transition to sending production traffic to the second app version containers instead of to the first app version.

Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers.

Abstract: Various embodiments are directed to systems and methods for providing employee data corresponding to individual employees to a customer computing entity operated by a customer. The employee data is provided so as to provide additional detail regarding an employee involved in a customer service interaction with the customer. The employee data is broadcast from an employee beacon carried by a respective employee. The employee data is received by a customer computing entity within the broadcast range of the employee beacon and, upon detection of a trigger event, the employee data is presented to the user via a graphical user interface of the customer computing entity, which requests that the customer provide feedback data regarding the employee, which may be transmitted to a management computing entity for storage and analysis.

Abstract: Various embodiments are directed to systems and methods for providing employee data corresponding to individual employees to a customer computing entity operated by a customer. The employee data is provided so as to provide additional detail regarding an employee involved in a customer service interaction with the customer. The employee data is broadcast from an employee beacon carried by a respective employee. The employee data is received by a customer computing entity within the broadcast range of the employee beacon and, upon detection of a trigger event, the employee data is presented to the user via a graphical user interface of the customer computing entity, which requests that the customer provide feedback data regarding the employee, which may be transmitted to a management computing entity for storage and analysis.

Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers.

Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers.

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.

Abstract: A release orchestration mechanism for cloud services. According to some implementations, while an app aware proxy routes production traffic to a first application (app) version that runs in a plurality of container orchestration system (COS) pods having first app version containers, configuration information is received. When a threshold number of the COS pods having the second app version containers are live, a validation of the second app version is caused. Then a transition to sending production traffic to the second app version containers is performed. After causing the transition, timers are started based on a time period indicated in the configuration information and the first app version containers are instructed to gracefully shut down. Based on expiration of the timers, any of the COS pods having the first app version containers that are not yet shut down are forced to shut down.

Abstract: Cloud services release orchestration with a reusable deployment pipeline. According to some implementations, responsive to receiving from a COS controller parameters from configuration information provided to the COS controller while an app aware proxy routes production traffic to a first application (app) version that communicates with a database management system (DBMS) and that runs in container orchestration system (COS) pods having first app version containers, causing a validation of a second app version using COS pods having second app version containers that are now live after having been brought up by the COS controller responsive to the provision of the configuration information. After the validation, causing the transition to sending production traffic to the second app version containers that are determined to be live instead of to the first app version containers.

Abstract: Various embodiments are directed to systems and methods for providing employee data corresponding to individual employees to a customer computing entity operated by a customer. The employee data is provided so as to provide additional detail regarding an employee involved in a customer service interaction with the customer. The employee data is broadcast from an employee beacon carried by a respective employee. The employee data is received by a customer computing entity within the broadcast range of the employee beacon and, upon detection of a trigger event, the employee data is presented to the user via a graphical user interface of the customer computing entity, which requests that the customer provide feedback data regarding the employee, which may be transmitted to a management computing entity for storage and analysis.

Abstract: The present application is a new improvement in the fine-grained cubic Boron Nitride sintered compact which may be employed to manufacture a cutting tool. The compact contains at least 80 vol % cBN and is sintered under HPHT conditions. The invention has lower levels of unreacted cobalt in the final sintered material than conventions materials. The invention has proved beneficial in the machining of ferrous metal alloys such as sintered metal alloys.

Abstract: The present application is a new improvement in the fine-grained cubic Boron Nitride sintered compact which may be employed to manufacture a cutting tool. The compact contains at least 80 vol % cBN and is sintered under HPHT conditions. The invention has lower levels of unreacted cobalt in the final sintered material than conventions materials. The invention has proved beneficial in the machining of ferrous metal alloys such as sintered metal alloys.

Abstract: Techniques are disclosed relating to caching web application data. In some embodiments, a computing system maintains a multi-tenant database and an in-memory cache for the database. In some embodiments, the computing system is configured to store data in an entry in response to a store request and retrieve data in response to a read request. In various embodiments, data cached by one tenant is not visible to other tenants. The cache may be partitioned and each partition may have an assigned capacity. The computing system may be configured to evict cached data based on capacity thresholds, least-recently-used information, time-to-live information, amount of data in an entry, etc. The cache may indicate misses when requested data is not present. Various disclosed techniques may improve web application performance while maintaining privacy between tenants.