* }
 *
 * <p>Even if your non-test code does not use finalization, you can use this class to test for
 * leaks, by ensuring that objects are no longer strongly referenced:
 *
 * {@snippet :
 * // Helper function keeps victim stack-unreachable.
 * private WeakReference<Foo> fooWeakRef() {
 *   Foo x = ....;
 *   WeakReference<Foo> weakRef = new WeakReference<>(x);
 *   // ... use x ...
 *   x = null; // Hint to the JIT that x is stack-unreachable

 * }
 *
 * <p>Even if your non-test code does not use finalization, you can use this class to test for
 * leaks, by ensuring that objects are no longer strongly referenced:
 *
 * {@snippet :
 * // Helper function keeps victim stack-unreachable.
 * private WeakReference<Foo> fooWeakRef() {
 *   Foo x = ....;
 *   WeakReference<Foo> weakRef = new WeakReference<>(x);
 *   // ... use x ...
 *   x = null; // Hint to the JIT that x is stack-unreachable

- Fixed a scheduler preemption issue where the victim pod was not deleted due to incorrect status patching. This issue occurred when the preemptor and victim pods had different QoS classes in their status, causing the preemption to fail entirely. ([#126644](https://github.com/kubernetes/kubernetes/pull/126644), [@Huang-Wei](https://github.com/Huang-Wei))...

- Fixed broken shell completion for API resources. ([#133771](https://github.com/kubernetes/kubernetes/pull/133771), [@marckhouzam](https://github.com/marckhouzam))

- Align the meaning of victim metrics between async preemption and sync preemption. The definition has been standardized to refer to the number of Pods chosen as victims. ([#135955](https://github.com/kubernetes/kubernetes/pull/135955), [@utam0k](https://github.com/utam0k)) [SIG Scheduling]

  public void testPrimitiveAndWrapper() {
    ImmutableClassToInstanceMap<Number> ictim =
        new ImmutableClassToInstanceMap.Builder<Number>()
            .put(Integer.class, 0)
            .put(int.class, 1)
            .build();
    assertEquals(2, ictim.size());

    assertEquals(0, (int) ictim.getInstance(Integer.class));
    assertEquals(1, (int) ictim.getInstance(int.class));
  }

    Note over Client: Keeps consuming...
```

Hatta, sürekli veri gönderdiğiniz sonsuz bir akış da olabilir.

## JSON Lines { #json-lines }

Bu tür durumlarda, her satıra bir JSON nesnesi gönderdiğiniz bir biçim olan “**JSON Lines**” kullanmak yaygındır.

Response’un `application/json` yerine `application/jsonl` içerik türü (Content-Type) olur ve body aşağıdaki gibi görünür:

```json

labels.url=URL
labels.userFavorite=Favori Günlüğü
labels.userInfo=Kullanıcı Bilgisi
labels.webApiJson=JSON Yanıtı
labels.webConfigName=Web Tarama Yapılandırma Adı
labels.allLanguages=Tüm Diller
labels.dictId=Sözlük ID
labels.docId=Belge ID
labels.endTime=Bitiş Zamanı
labels.hq=hq
labels.inputs=Girdiler
labels.jobLogging=Günlükleme
labels.jobName=Ad
labels.jobStatus=Durum
labels.labelTypeIds=Etiketler

labels.threadName=Thread Name
labels.url=URL
labels.userFavorite=Favorite Log
labels.userInfo=User Info
labels.webApiJson=JSON Response
labels.webConfigName=Web Crawl Config Name
labels.allLanguages=All Languages
labels.dictId=Dictionary ID
labels.docId=Document ID
labels.endTime=End Time
labels.hq=hq
labels.inputs=Inputs
labels.jobLogging=Logging
labels.jobName=Name
labels.jobStatus=Status
labels.labelTypeIds=Labels

	VMSBFM		V2, V4, V3			// ERROR "invalid vector mask register"
	VMSIFM		V2, V4, V3			// ERROR "invalid vector mask register"
	VMSOFM		V2, V4, V3			// ERROR "invalid vector mask register"
	VIOTAM		V2, V4, V3			// ERROR "invalid vector mask register"
	VSLIDEUPVX	X10, V2, V4, V3			// ERROR "invalid vector mask register"
	VSLIDEUPVI	$16, V2, V4, V3			// ERROR "invalid vector mask register"