The Code of Federal Regulations (CFR) is the official legal print publication containing the codification of the general and permanent rules published in the Federal Register by the departments and agencies of the Federal Government. The Electronic Code of Federal Regulations (eCFR) is a continuously updated online version of the CFR. It is not an official legal edition of the CFR.
The Federal awarding agency and the non-Federal entity should, whenever practicable, collect, transmit, and store Federal award-related information in open and machine-readable formats rather than in closed formats or on paper in accordance with applicable legislative requirements. A machine-readable format is a format in a standard computer language (not English text) that can be read automatically by a web browser or computer system. The Federal awarding agency or pass-through entity must always provide or accept paper versions of Federal award-related information to and from the non-Federal entity upon request. If paper copies are submitted, the Federal awarding agency or pass-through entity must not require more than an original and two copies. When original records are electronic and cannot be altered, there is no need to create and retain paper copies. When original records are paper, electronic versions may be substituted through the use of duplication or other forms of electronic media provided that they are subject to periodic quality control reviews, provide reasonable safeguards against alteration, and remain readable.
The cost of services provided by one agency to another within the governmental unit may include allowable direct costs of the service plus a pro-rated share of indirect costs. A standard indirect cost allowance equal to ten percent of the direct salary and wage cost of providing the service (excluding overtime, shift premiums, and fringe benefits) may be used in lieu of determining the actual indirect costs of the service. These services do not include centralized services included in central service cost allocation plans as described in Appendix V to Part 200.
Costs of entertainment, including amusement, diversion, and social activities and any associated costs are unallowable, except where specific costs that might otherwise be considered entertainment have a programmatic purpose and are authorized either in the approved budget for the Federal award or with prior written approval of the Federal awarding agency.
A change in level of 1/2 inch (13 mm) is permitted to be 1/4 inch (6.4 mm) vertical plus 1/4 inch (6.4 mm) beveled. However, in no case may the combined change in level exceed 1/2 inch (13 mm). Changes in level exceeding 1/2 inch (13 mm) must comply with 405 (Ramps) or 406 (Curb Ramps).
404.2.6 Doors in Series and Gates in Series. The distance between two hinged or pivoted doors in series and gates in series shall be 48 inches (1220 mm) minimum plus the width of doors or gates swinging into the space.
703.2.8 Line Spacing. Spacing between the baselines of separate lines of raised characters within a message shall be 135 percent minimum and 170 percent maximum of the raised character height.
703.4.1 Height Above Finish Floor or Ground. Tactile characters on signs shall be located 48 inches (1220 mm) minimum above the finish floor or ground surface, measured from the baseline of the lowest tactile character and 60 inches (1525 mm) maximum above the finish floor or ground surface, measured from the baseline of the highest tactile character.
707.6.3.2 Tactile Symbols. Function key surfaces shall have tactile symbols as follows: Enter or Proceed key: raised circle; Clear or Correct key: raised left arrow; Cancel key: raised letter ex; Add Value key: raised plus sign; Decrease Value key: raised minus sign.
1002.4.3 Gaps. Floors of amusement rides with wheelchair spaces and floors of load and unload areas shall be coordinated so that, when amusement rides are at rest in the load and unload position, the vertical difference between the floors shall be within plus or minus 5/8 inches (16 mm) and the horizontal gap shall be 3 inches (75 mm) maximum under normal passenger load conditions.
The following example shows how exception 3 would be applied: A gangway is provided to a floating pier which is required to be on an accessible route. The vertical distance is 10 feet (3050 mm) between the elevation where the gangway departs the landside connection and the elevation of the pier surface at the lowest water level. Exception 3 permits the gangway to be 80 feet (24 m) long. Another design solution would be to have two 40 foot (12 m) plus continuous gangways joined together at a float, where the float (as the water level falls) will stop dropping at an elevation five feet below the landside connection. The length of transition plates would not be included in determining if the gangway(s) meet the requirements of the exception.
Oracle recommends that the JDK is updated with each Critical Patch Update.In order to determine if a release is the latest, the Security Baseline page canbe used to determine which is the latest version for each release family.
Critical patch updates, which contain security vulnerability fixes, are announced one year in advance onCritical Patch Updates, Security Alerts and Bulletins.It is not recommended that this JDK (version 8u361) be used after the next critical patch update scheduledfor April 18, 2023.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u361) on2023-05-18.After either condition is met (new release becoming available or expiration date reached),the JRE will provide additional warnings and reminders to users to update to the newer version.For more information, see 23.1.2 JRE Expiration Date in the Java Platform, Standard Edition Deployment Guide.
JFR is a low-overhead data collection framework for troubleshooting Java applications and the HotSpot JVM in production. Recorded data can be opened in JDK Mission Control (JMC). To start recordings from within JMC, a new version of JMC is required. Currently, it is not released as part of the JDK but is available as a downloadable patch from Supported Java SE Downloads on MOS or from JDK Mission Control 8 Downloads. JFR comes with a supported API to produce and consume data programmatically.
Critical patch updates, which contain security vulnerability fixes, are announced one year in advance onCritical Patch Updates, Security Alerts and Bulletins.It is not recommended that this JDK (version 8u351) be used after the next critical patch update scheduledfor January 17, 2023.
For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u351) on2023-02-17.After either condition is met (new release becoming available or expiration date reached),the JRE will provide additional warnings and reminders to users to update to the newer version.For more information, see 23.1.2 JRE Expiration Date in the Java Platform, Standard Edition Deployment Guide.
The new SHA-256 based MAC algorithms were introduced in the 11.0.12, 8u301, and 7u311 JDK versions. Keystores created using this newer, stronger, MAC algorithm cannot be opened in JDK versions earlier than 11.0.12, 8u301, and 7u311. A 'java.security.NoSuchAlgorithmException' exception will be thrown in such circumstances.
This version includes changes from 2022b that merged multiple regions that have the same timestamp data post-1970 into a single time zone data. All time zone IDs remain the same but the merged time zones will point to a shared zone data.
As a result, pre-1970 data may not be compatible with earlier JDK versions. The affected zones are Antarctica/Vostok, Asia/Brunei, Asia/Kuala_Lumpur, Atlantic/Reykjavik, Europe/Amsterdam, Europe/Copenhagen, Europe/Luxembourg, Europe/Monaco, Europe/Oslo, Europe/Stockholm, Indian/Christmas, Indian/Cocos, Indian/Kerguelen, Indian/Mahe, Indian/Reunion, Pacific/Chuuk, Pacific/Funafuti, Pacific/Majuro, Pacific/Pohnpei, Pacific/Wake, Pacific/Wallis, Arctic/Longyearbyen, Atlantic/Jan_Mayen, Iceland, Pacific/Ponape, Pacific/Truk, and Pacific/Yap.
The Java SE 8 Enterprise Performance Pack follows the versioning format defined by JEP 322, and reports the actual VM version of 17.x, when, for example, java -version is invoked. However, for compatibility purposes, the sun.misc.Version methods jvmMajorVersion() and jvmMinorVersion() instead report the same VM version as Java SE 8 i.e. 25.x. This ensures that application code checking for a Java 8 runtime by looking for a major version greater than, or equal to, 25, will work correctly even though the actual VM version is 17.
Some linux kernel versions (including, but not limited to 3.13.0-121-generic and 4.4.0-81-generic) are known to contain an incorrect fix for a linux kernel stack overflow issue (See CVE-2017-1000364). The incorrect fix can trigger crashes in the Java Virtual Machine. Upgrading the kernel to a version that includes the corrected fix addresses the problem.
This change enforces the unqualified name format checks for NameAndType strings as outlined in the JVM specification sections 4.4.6 and 4.2.2, meaning that some illegal names and descriptors that users may be utilizing in their classfiles will now be caught with a Class Format Error. This includes format checking for all strings under non-referenced NameAndType's. Users will see a change if they (A) are using Java classfile version 6 or below and have an illegal NameAndType descriptor with no Methodref or Fieldref reference to it; or (B) are using any Java classfile version and have an illegal NameAndType name with no Methodref or Fieldref reference to it. 2b1af7f3a8