pub struct ManagerSynchronousProxy { /* private fields */ }
Implementations§
Source§impl ManagerSynchronousProxy
impl ManagerSynchronousProxy
pub fn new(channel: Channel) -> Self
pub fn into_channel(self) -> Channel
Sourcepub fn wait_for_event(
&self,
deadline: MonotonicInstant,
) -> Result<ManagerEvent, Error>
pub fn wait_for_event( &self, deadline: MonotonicInstant, ) -> Result<ManagerEvent, Error>
Waits until an event arrives and returns it. It is safe for other threads to make concurrent requests while waiting for an event.
Sourcepub fn check_now(
&self,
options: &CheckOptions,
monitor: Option<ClientEnd<MonitorMarker>>,
___deadline: MonotonicInstant,
) -> Result<ManagerCheckNowResult, Error>
pub fn check_now( &self, options: &CheckOptions, monitor: Option<ClientEnd<MonitorMarker>>, ___deadline: MonotonicInstant, ) -> Result<ManagerCheckNowResult, Error>
Immediately check for an update, and optionally track the state and progress of that update check.
-
request
options
Options for how this request should be performed. E.g. What kind of entity initiated this request? E.g. Is monitoring an existing update check that is already in process an acceptable alternative? -
request
monitor
An interface on which to receive the status events for this update check. The monitor is only valid for this single update check, after that it will not receive any more notifications and will be closed.
- error If an update check cannot be started, an error will be returned.
The [
Monitor
], if provided, will not receive any notifications.
Sourcepub fn perform_pending_reboot(
&self,
___deadline: MonotonicInstant,
) -> Result<bool, Error>
pub fn perform_pending_reboot( &self, ___deadline: MonotonicInstant, ) -> Result<bool, Error>
Performs any pending reboot of the system into an updated OS, if an update has been staged for the next system startup.
Should be used when the platform is configured to let the product drive reboot scheduling. If this method is called when the platform is not configured to let the product drive reboot scheduling, no reboot will occur, and the system will reboot on its own after an update.
In product-driven reboot configurations, the platform still contains a backstop for post-update reboots. This means that if an update is installed but the system has not rebooted before the backstop duration occurs, the update system will automatically reboot the system as a security measure. To avoid hitting this backstop, products which desire control over reboot timing should call this method roughly daily.
- response
rebooting
true if the system is rebooting, false if no update was pending reboot.
Sourcepub fn monitor_all_update_checks(
&self,
attempts_monitor: ClientEnd<AttemptsMonitorMarker>,
) -> Result<(), Error>
pub fn monitor_all_update_checks( &self, attempts_monitor: ClientEnd<AttemptsMonitorMarker>, ) -> Result<(), Error>
Monitor all update attempts as they start, as well as an in-progress attempt, if there is one.
Arguments:
- |attempts_monitor| A protocol on which to receive |Monitor| instances as update attempts start.
Trait Implementations§
Source§impl Debug for ManagerSynchronousProxy
impl Debug for ManagerSynchronousProxy
Source§impl SynchronousProxy for ManagerSynchronousProxy
impl SynchronousProxy for ManagerSynchronousProxy
Source§type Proxy = ManagerProxy
type Proxy = ManagerProxy
Source§type Protocol = ManagerMarker
type Protocol = ManagerMarker
Proxy
controls.