* Upgrade Stackdriver Logging Agent addon image to 0.6-1.6.0-1 to use Fluentd v1.2. This provides nanoseconds timestamp granularity for logs. ([#70954](https://github.com/kubernetes/kubernetes/pull/70954), [@qingling128](https://github.com/qingling128))

pkg syscall (windows-386), method (*DLL) Release() error
pkg syscall (windows-386), method (*DLLError) Error() string
pkg syscall (windows-386), method (*Filetime) Nanoseconds() int64
pkg syscall (windows-386), method (*LazyDLL) Handle() uintptr
pkg syscall (windows-386), method (*LazyDLL) Load() error
pkg syscall (windows-386), method (*LazyDLL) NewProc(string) *LazyProc

            // Given
            byte[] buffer = new byte[60];
            SMBUtil.writeInt2(60, buffer, 0);

            // SMB times are in 100-nanosecond intervals since 1601
            // Java times are in milliseconds since 1970
            long currentJavaTime = System.currentTimeMillis();
            long smbTime = currentJavaTime * 10000L + 116444736000000000L;

		fitsOctal := fitsInOctal(size, ts.Unix())
		if (isMtime && !fitsOctal) || !isMtime {
			whyNoUSTAR = fmt.Sprintf("USTAR cannot encode %s=%v", name, ts)
			format.mustNotBe(FormatUSTAR)
		}
		needsNano := ts.Nanosecond() != 0
		if !isMtime || !fitsOctal || needsNano {
			preferPAX = true // USTAR may truncate sub-second measurements
			if paxKey == paxNone {
				whyNoPAX = fmt.Sprintf("PAX cannot encode %s=%v", name, ts)

Si vous venez d'un autre framework asynchrone qui ne fonctionne pas comme de la façon décrite ci-dessus et que vous êtes habitués à définir des *fonctions de chemin* basiques avec un simple `def` pour un faible gain de performance (environ 100 nanosecondes), veuillez noter que dans **FastAPI**, l'effet serait plutôt contraire. Dans ces cas-là, il vaut mieux utiliser `async def` à moins que votre *fonction de chemin* utilise du code qui effectue des opérations <abbr title="Input/Output ou Entrées...

  - `priority_level_seat_count_watermarks` is removed.
  - `priority_level_request_count_samples` is replaced with `priority_level_request_utilization`, which samples every nanosecond rather than every millisecond; the old metric conveyed utilization despite its name.

    - `apiserver_flowcontrol_upper_limit_seats`: Configured upper bound on number of execution seats available to each priority level
    - `apiserver_flowcontrol_demand_seats`: Observations, at the end of every nanosecond, of (the number of seats each priority level could use) / (nominal number of seats for that level)
    - `apiserver_flowcontrol_demand_seats_high_watermark`: High watermark, over last adjustment period, of demand_seats

pkg time, const March = 3
pkg time, const May = 5
pkg time, const Microsecond = 1000
pkg time, const Millisecond = 1000000
pkg time, const Minute = 60000000000
pkg time, const Monday = 1
pkg time, const Nanosecond = 1
pkg time, const November = 11
pkg time, const October = 10
pkg time, const RFC1123 = "Mon, 02 Jan 2006 15:04:05 MST"
pkg time, const RFC1123Z = "Mon, 02 Jan 2006 15:04:05 -0700"