HSPLandroidx/core/app/CoreComponentFactory;->instantiateApplication(Ljava/lang/ClassLoader;Ljava/lang/String;)Landroid/app/Application;
HSPLandroidx/core/app/CoreComponentFactory;->instantiateProvider(Ljava/lang/ClassLoader;Ljava/lang/String;)Landroid/content/ContentProvider;
HSPLandroidx/core/view/MenuHostHelper;-><init>(Ljava/lang/Runnable;)V

          </annotations>
        </field>
        <field>
          <name>outputDirectory</name>
          <version>4.0.0+</version>
          <description>
            The directory where compiled application classes are placed.
            The default value is {@code target/classes}.
          </description>
          <type>String</type>
        </field>
        <field>
          <name>testOutputDirectory</name>

- **Simplified User Experience**
  - Easier to get a cluster up and running (eg: `kubeadm`, intra-cluster bootstrapping)
  - Easier to understand a cluster (eg: API audit logs, server-based API defaults)
- **Stateful Application Support**
  - Enhanced persistence capabilities (eg: `StorageClasses`, new volume plugins)
  - New resources and scheduler features (eg: `ScheduledJob` resource, pod/node affinity/anti-affinity)
- **Cluster Federation**

¤DDirÄ Ÿl;âF?Gq¦Ç ºª?ò¦EcAlgo £EcM £EcN §EcBSizeÒ §EcIndex ¦EcDist” ¨CSumAlgo ¨PartNums‘ ©PartETags‘ ©PartSizes‘Ò ªPartASizes‘Ò ¤SizeÒ ¥MTimeÓ ð ÞÍ &˜§MetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ fffb6377948ebea75ad2¬content-type¸application/octet-streamÎ7£ï; disk1/testbucket/file/xl.meta 䱘′ ÆĀ腘嚨牥楳湯酳ꒂ祔数ꔁ㉖扏 ᄀ䦢쑄 ꐀ䑄物Ⴤ沟㽆煇잦Вꪺ䖦䅣杬ů䖣䵣ꌂ捅Ɏ䖧䉣楓敺Ò ꜀捅湉敤ɸ䖦䑣獩鑴̂Ą䎨畓䅭杬ů储牡乴浵酳꤁慐瑲呅条酳ꦠ慐瑲楓敺酳ÒЂꨀ慐瑲十穩獥튑Ȁ 厤穩퉥Ȁ 䶥楔敭ᛓ翰췞☝Ꞙ敍慴祓腳碼洭湩潩椭瑮牥慮⵬湩楬敮搭瑡쑡琄畲ꝥ敍慴獕色掬湯整瑮琭灹롥灡汰捩瑡潩⽮捯整⵴瑳敲浡斤慴 晦㙢㜳㤷㠴扥慥㔷摡戲〸㠵㡥㤴晥층౵ㅒ脁溤汵왬Ā 鍭஥ῗ퇞햑䦕餫䈒렿ᗒ轸럴ឹꙀᒟ㒝琦곥...

- Extended resources backed by DRA feature allowed cluster operator to specify `extendedResourceName` in `DeviceClass`, and application operator to continue using extended resources in pod's requests to request for DRA devices matching the DeviceClass.
  

- Fixed file permission issues that happened during update of `Secret`/`ConfigMap`/`projected volume` when `fsGroup` is used. The problem caused a race condition where application gets intermittent permission denied error when reading files that were just updated, before the correct permissions were applied. ([#114464](https://github.com/kubernetes/kubernetes/pull/114464), [@tsaarni](https://github.com/tsaarni))

			successMsg = fmt.Sprintf("%s\n- default bandwidth %v for peer %s", successMsg, peer.DefaultBandwidth.Limit, peer.Name)
		}
		state.Peers[peer.DeploymentID] = pi
	}

	// If ILM expiry replications enabled/disabled, set accordingly
	if opts.DisableILMExpiryReplication {
		for dID, pi := range state.Peers {
			if !pi.ReplicateILMExpiry {
				return madmin.ReplicateEditStatus{

- Fixed a potential data race in DRA with no known real-world implications. ([#123222](https://github.com/kubernetes/kubernetes/pull/123222), [@pohly](https://github.com/pohly))
- Fixed a race condition in the iptables mode of kube-proxy in `1.27` and later

- kubeadm: fix "certificate-authority" files not being pre-loaded when using file discovery ([#80966](https://github.com/kubernetes/kubernetes/pull/80966), [@neolit123](https://github.com/neolit123))
- Add instruction to setup "Application Default Credentials" to run GCE Windows e2e tests locally. ([#81337](https://github.com/kubernetes/kubernetes/pull/81337), [@YangLu1031](https://github.com/YangLu1031))

- client-go discovery clients constructed using `NewDiscoveryClientForConfig` or `NewDiscoveryClientForConfigOrDie` default to rate limits that cause normal discovery request...