- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

- Previously, the scheduling queue didn't notice any extenders' failures, potentially resulting in missed cluster events and Pods rejected by Extenders being stuck in the unschedulable pod pool for up to 5 minutes in the worst-case scenario. Now, the scheduling queue notices extenders' failures and requeues Pods rejected by Extenders appropriately.
   ([#122022](https://github.com/kubernetes/kubernetes/pull/122022), [@sanposhiho](https://github.com/sanposhiho))

- Fix a bug that when PodTopologySpread rejects Pods, they may be stuck in Pending state for 5 min in a worst case scenario.
  The same problem could happen with custom plugins which have Pod/Add or Pod/Update in EventsToRegister,

2FB9          ; mapped                 ; 9999          # 3.0  KANGXI RADICAL FRAGRANT
2FBA          ; mapped                 ; 99AC          # 3.0  KANGXI RADICAL HORSE
2FBB          ; mapped                 ; 9AA8          # 3.0  KANGXI RADICAL BONE
2FBC          ; mapped                 ; 9AD8          # 3.0  KANGXI RADICAL TALL

uva\u0007vologda\u000bknightpoint\u0004test\u0003ens\u0004intl\u0006mincom\u000borangecloud\u0003611\u0004nett\u0003oya\u0007vpnplus\u000cprequalifyme\u0004addr\u0005ntdll\u0004wadl\u0003bbs\u0003bel\u0003kep\u0003tsk\u000bbetter-than\non-the-web\nworse-than\u0004ebiz\u0003url\u0009cherkassy\u0008cherkasy\u0009chernigov\u0009chernihiv\nchernivtsi\nchernovtsy\u0006crimea\u0002dn\u000ednepropetrovsk\u000ednipropetrovsk\u0007donetsk\u0002dp\u0002if\u000fivano-frankivsk\u0007kharkiv\u0007kharkov\u00...

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

- The scheduling queue didn't notice any extenders' failures, it could miss some cluster events,
  and it could end up Pods rejected by Extenders stuck in unschedulable pod pool in 5min in the worst-case scenario.

186-5, Section 6.4.1, point 2 and Section 6.4.2, point 3. func hashToNat[P Point[P]](c *Curve[P], e *bigmod.Nat, hash []byte) { // ECDSA asks us to take the left-most log2(N) bits of hash, and use them as // an integer modulo N. This is the absolute worst of all worlds: we still // have to reduce, because the result might still overflow N, but to take // the left-most bits for P-521 we have to do a right shift. if size := c.N.Size(); len(hash) >= size { hash = hash[:size] if excess := len(hash)*8 -...

186-5, Section 6.4.1, point 2 and Section 6.4.2, point 3. func hashToNat[P Point[P]](c *Curve[P], e *bigmod.Nat, hash []byte) { // ECDSA asks us to take the left-most log2(N) bits of hash, and use them as // an integer modulo N. This is the absolute worst of all worlds: we still // have to reduce, because the result might still overflow N, but to take // the left-most bits for P-521 we have to do a right shift. if size := c.N.Size(); len(hash) >= size { hash = hash[:size] if excess := len(hash)*8 -...