- Sort Score
- Result 10 results
- Languages All
Results 71 - 80 of 502 for eventIn (0.04 sec)
-
docs/changelogs/changelog_4x.md
been received. Previously these events were incorrectly sent too early, when OkHttp was ready to read the response headers or body, which mislead tracing tools. Note that the `responseFailed()` event always used to follow one of these events; now it may be sent without them. * New: Upgrade to Kotlin 1.3.61.
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Apr 17 13:25:31 UTC 2024 - 25.2K bytes - Viewed (0) -
src/main/java/jcifs/smb/SmbSessionImpl.java
} } /** * Handle node unavailable events */ private void handleNodeUnavailable(WitnessNotification notification) { log.warn("Node unavailable: {}", notification.getResourceName()); // Could trigger failover logic here } /** * Handle node available events */ private void handleNodeAvailable(WitnessNotification notification) {
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Sun Aug 31 08:00:57 UTC 2025 - 68.9K bytes - Viewed (0) -
cmd/peer-rest-server.go
enc := json.NewEncoder(buf) tmpEvt := struct{ Records []event.Event }{[]event.Event{{}}} for { select { case <-ctx.Done(): grid.PutByteBuffer(buf.Bytes()) return nil case ev := <-ch: buf.Reset() tmpEvt.Records[0] = ev if err := enc.Encode(tmpEvt); err != nil { peersLogOnceIf(ctx, err, "event: Encode failed") continue }
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Sun Mar 30 00:56:02 UTC 2025 - 53.4K bytes - Viewed (0) -
CODE_OF_CONDUCT.md
## Scope This Code of Conduct applies to all content on tensorflow.org, TensorFlow’s GitHub organization, or any other official TensorFlow web presence allowing for community interactions, as well as at all official TensorFlow events, whether offline or online.
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Fri Feb 05 18:43:16 UTC 2021 - 5.2K bytes - Viewed (0) -
android/guava/src/com/google/common/util/concurrent/ServiceManager.java
private static final ListenerCallQueue.Event<Listener> HEALTHY_EVENT = new ListenerCallQueue.Event<Listener>() { @Override public void call(Listener listener) { listener.healthy(); } @Override public String toString() { return "healthy()"; } }; private static final ListenerCallQueue.Event<Listener> STOPPED_EVENT =
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Tue May 13 17:27:14 UTC 2025 - 33.2K bytes - Viewed (1) -
cmd/bucket-handlers.go
return } // Notify object created events. sendEvent(eventArgsList[i]) if eventArgsList[i].Object.NumVersions > int(scannerExcessObjectVersions.Load()) { // Send events for excessive versions. sendEvent(eventArgs{ EventName: event.ObjectManyVersions, BucketName: eventArgsList[i].Object.Bucket,
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Fri Aug 29 02:39:48 UTC 2025 - 63.9K bytes - Viewed (0) -
okhttp/src/jvmTest/kotlin/okhttp3/FakeRoutePlanner.kt
} canceled -> { events += "plan $id TCP connect canceled" ConnectResult(this, nextPlan = connectTcpNextPlan, throwable = IOException("canceled")) } connectTcpNextPlan != null -> { events += "plan $id needs follow-up" ConnectResult(this, nextPlan = connectTcpNextPlan) } else -> { events += "plan $id TCP connected"
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Wed Mar 19 19:25:20 UTC 2025 - 6.1K bytes - Viewed (0) -
docs/metrics/prometheus/list.md
| `minio_notify_events_errors_total` | Events that were failed to be sent to the targets (deprecated, please use `minio_notify_target_failed_events` instead) | | `minio_notify_events_sent_total` | Total number of events sent to the targets (deprecated, please use `minio_notify_target_total_events` instead) |
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 43.4K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.27.md
- Fixed a bug where `events/v1` `Events` with similar event type and reporting instance were not aggregated by `client-go`. ([#112365](https://github.com/kubernetes/kubernetes/pull/112365), [@dgrisonnet](https://github.com/dgrisonnet))
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Wed Jul 17 07:48:22 UTC 2024 - 466.3K bytes - Viewed (2) -
docs/bucket/replication/README.md
The status of replication can be monitored by configuring event notifications on the source and target buckets using `mc event add`.On the source side, the `s3:PutObject`, `s3:Replication:OperationCompletedReplication` and `s3:Replication:OperationFailedReplication` events show the status of replication in the `X-Amz-Replication-Status` metadata.
Registered: Sun Sep 07 19:28:11 UTC 2025 - Last Modified: Tue Aug 12 18:20:36 UTC 2025 - 18.3K bytes - Viewed (0)