Lines Matching refs:will
27 thread publishes a message on a channel, the bus will make the message available to all the
83 or observations individually. The event dispatcher will ignore disabled observers and observations.
94 shows the observer is disabled, so the event dispatcher will ignore it. (c) shows the observer
95 enabled. However, there is one static observation disabled. The event dispatcher will only stop
96 sending notifications from channel ``C3``. In (d), the event dispatcher will stop sending
307 in the calculation. The VDED will elevate the publisher's priority based on the HOP to ensure small
328 subscriber is attached to a thread, it assumes its priority, and the priority boost algorithm will
355 On the above code, the :c:func:`zbus_obs_attach_to_thread` will set the ``s1`` observer with
358 will be considered on the channel HOP calculation. Masking a specific observation of a channel will
364 * No bounded priority inversion will happen among the publisher and the observers;
367 * Message subscribers will wait for the VDED to finish the message delivery process. So the VDED
368 execution will be faster and more consistent;
374 acceptable in the zbus scenario since it will ensure a small bus latency.
381 arise. ZBus will not solve every problem, so it is necessary to analyze the situation to be sure
411 Subscribers will receive only the reference of the changing channel. A data loss may be perceived
413 overwrites the value from the first. Thus, the subscriber will receive two notifications, but
422 The message delivery will follow the precedence:
432 The VDED will ignore all disabled observers or observations.
529 Publish attempts invalidated by hard channels will return immediately with an error code. This
534 only messages with ``move`` equal to 0, -1, and 1 are valid. Publish function will discard all other
570 trying to publish the message ``acc1`` to channel ``acc_chan``, and it will wait up to one second
588 following code tries to read the channel ``acc_chan``, which will wait up to 500 milliseconds to
601 :c:func:`zbus_sub_wait` carefully because the channel will always be unavailable during the VDED
629 channels, and naming new channels or linking will fail. It is possible to declare more than one
710 The code will log the following output:
763 macro's ``user_data`` field, which will then be accessible by others. Note that ``user_data`` is