- Sort Score
- Num 10 results
- Language All
Results 1 - 10 of 147 for emitted (0.07 seconds)
-
docs/en/docs/tutorial/security/oauth2-jwt.md
``` It is not encrypted, so, anyone could recover the information from the contents. But it's signed. So, when you receive a token that you emitted, you can verify that you actually emitted it. That way, you can create a token with an expiration of, let's say, 1 week. And then when the user comes back the next day with the token, you know that user is still logged in to your system.
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 05 18:13:19 GMT 2026 - 10.7K bytes - Click Count (0) -
android/guava/src/com/google/common/util/concurrent/AtomicDouble.java
@Override public double doubleValue() { return get(); } /** * Saves the state to a stream (that is, serializes it). * * @serialData The current value is emitted (a {@code double}). */ private void writeObject(ObjectOutputStream s) throws IOException { s.defaultWriteObject(); s.writeDouble(get()); }
Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Thu Jan 29 22:14:05 GMT 2026 - 7.2K bytes - Click Count (0) -
tests/test_sse.py
@keepalive_app.get("/slow-async", response_class=EventSourceResponse) async def slow_async_stream(): yield {"n": 1} # Sleep longer than the (monkeypatched) ping interval so a keepalive # comment is emitted before the next item. await asyncio.sleep(0.3) yield {"n": 2} @keepalive_app.get("/slow-sync", response_class=EventSourceResponse) def slow_sync_stream(): yield {"n": 1} time.sleep(0.3)
Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Sun Mar 01 09:21:52 GMT 2026 - 9.8K bytes - Click Count (0) -
android/guava/src/com/google/common/util/concurrent/AtomicDoubleArray.java
} b.append(',').append(' '); } } /** * Saves the state to a stream (that is, serializes it). * * @serialData The length of the array is emitted (int), followed by all of its elements (each a * {@code double}) in the proper order. */ private void writeObject(ObjectOutputStream s) throws IOException { s.defaultWriteObject();Created: Fri Apr 03 12:43:13 GMT 2026 - Last Modified: Thu Jan 29 22:14:05 GMT 2026 - 8.1K bytes - Click Count (0) -
okhttp/src/commonJvmAndroid/kotlin/okhttp3/internal/idn/Punycode.kt
Created: Fri Apr 03 11:42:14 GMT 2026 - Last Modified: Tue Jan 27 09:00:39 GMT 2026 - 8.6K bytes - Click Count (0) -
impl/maven-cli/src/main/java/org/apache/maven/cling/invoker/LookupInvoker.java
* <p> * If there are Maven3 passwords presents in settings, this results in doubled warnings emitted. So Plexus DI * creation call keeps "emitSettingsWarnings" false. If there are fatal issues, it will anyway "die" at that * spot before warnings would be emitted. * <p> * The method returns a "cleaner" runnable, as during extension loading the context needs to be "cleaned", restoredCreated: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Tue Oct 28 13:01:07 GMT 2025 - 43.2K bytes - Click Count (0) -
src/cmd/api/main_test.go
if methodNames == nil { methodNames = make(map[string]bool) } methodNames[m.Obj().Name()] = true } } // emit methods with pointer receiver; exclude // methods that we have emitted already // (the method set of *T includes the methods of T) pset := types.NewMethodSet(types.NewPointer(typ)) for i, n := 0, pset.Len(); i < n; i++ { m := pset.At(i)Created: Tue Apr 07 11:13:11 GMT 2026 - Last Modified: Mon Mar 02 13:20:41 GMT 2026 - 31.4K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.34.md
- Updated the HPA controller so that it no longer emitted a `FailedRescale` event if a scale operation initially failed due to a conflict but succeeded after a retry; it now emitted a `SuccessfulRescale` event in this case. A `FailedRescale` event was still emitted if all retries were exhausted. ([#132007](https://github.com/kubernetes/kubernetes/pull/132007), [@AumPatel1](https://github.com/AumPatel1)) [SIG...
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:19:43 GMT 2026 - 368.7K bytes - Click Count (2) -
CHANGELOG/CHANGELOG-1.36.md
- DRA device taint eviction: the controller might have reported "1 pod needs to be evicted in 1 namespace. 1 pod evicted since starting the controller." when only a single pod is involved, depending on timing (pod evicted, informer cache not updated yet). It would eventually arrive at the correct "1 pod evicted since starting the controller.", but now it tries harder to avoid the confusing intermediate state by delaying the status update after eviction....
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 23:38:00 GMT 2026 - 142.1K bytes - Click Count (0) -
CHANGELOG/CHANGELOG-1.33.md
- Fixed a bug where kube-apiserver could emit a subsequent watch event even if the previous event failed to decrypt and was not emitted. ([#131020](https://github.com/kubernetes/kubernetes/pull/131020), [@wojtek-t](https://github.com/wojtek-t)) [SIG API Machinery and Etcd]
Created: Fri Apr 03 09:05:14 GMT 2026 - Last Modified: Thu Mar 19 03:17:58 GMT 2026 - 369K bytes - Click Count (0)