- Sort Score
- Result 10 results
- Languages All
Results 181 - 190 of 950 for events (0.08 sec)
-
fastapi/applications.py
) -> Callable[[DecoratedCallable], DecoratedCallable]: """ Add an event handler for the application. `on_event` is deprecated, use `lifespan` event handlers instead. Read more about it in the [FastAPI docs for Lifespan Events](https://fastapi.tiangolo.com/advanced/events/#alternative-events-deprecated). """ return self.router.on_event(event_type)
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sat Aug 17 04:52:31 UTC 2024 - 172.2K bytes - Viewed (0) -
docs/en/docs/deployment/docker.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Wed Sep 18 16:09:57 UTC 2024 - 28.5K bytes - Viewed (0) -
compat/maven-compat/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java
import org.apache.maven.repository.legacy.metadata.MetadataResolutionRequest; import org.apache.maven.repository.legacy.resolver.conflict.ConflictResolver; import org.apache.maven.wagon.events.TransferListener; import org.codehaus.plexus.PlexusContainer; import org.codehaus.plexus.component.repository.exception.ComponentLookupException; import org.codehaus.plexus.logging.Logger;
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 24.8K bytes - Viewed (0) -
cni/pkg/nodeagent/server.go
// Add IP/port combo to set. Note that we set Replace to false here - we _did_ previously // set it to true, but in theory that could mask weird scenarios where K8S triggers events out of order -> // an add(sameIPreused) then delete(originalIP). // Which will result in the new pod starting to fail healthchecks. //
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Sep 25 20:54:34 UTC 2024 - 13.4K bytes - Viewed (0) -
docs/vi/docs/features.md
* Hỗ trợ **WebSocket**. * In-process background tasks. * Startup and shutdown events. * Client cho kiểm thử xây dựng trên HTTPX. * **CORS**, GZip, Static Files, Streaming responses. * Hỗ trợ **Session and Cookie**. * 100% test coverage. * 100% type annotated codebase. ## Tính năng của Pydantic
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 11.5K bytes - Viewed (0) -
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 Nov 03 19:28:11 UTC 2024 - Last Modified: Tue Jan 24 23:46:33 UTC 2023 - 18.2K bytes - Viewed (0) -
CHANGELOG/CHANGELOG-1.16.md
* kube-scheduler now fallbacks to emitting events using core/v1 Events when events.k8s.io/v1beta1 is disabled. ([#83692](https://github.com/kubernetes/kubernetes/pull/83692), [@yastij](https://github.com/yastij))
Registered: Fri Nov 01 09:05:11 UTC 2024 - Last Modified: Thu Feb 11 10:00:57 UTC 2021 - 345.2K bytes - Viewed (0) -
architecture/networking/pilot.md
As a result, they do not go through `PushContext`, and changes do not trigger a `PushContext` recomputation. Instead, the current state is incrementally computed based on events from `ServiceDiscovery`. #### Conclusion Overall, the high level config ingestion flow: ```mermaid graph TD sd(Service Discovery) cs(ConfigStore) ep(Endpoints) pc(PushContext)
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Wed Feb 07 17:53:24 UTC 2024 - 19.1K 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 Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Oct 04 11:32:32 UTC 2024 - 53.2K bytes - Viewed (0) -
common-protos/k8s.io/api/core/v1/generated.proto
} // Event is a report of an event somewhere in the cluster. Events // have a limited retention time and triggers and messages may evolve // with time. Event consumers should not rely on the timing of an event // with a given Reason reflecting a consistent underlying trigger, or the // continued existence of events with that Reason. Events should be
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Mar 11 18:43:24 UTC 2024 - 255.8K bytes - Viewed (0)