PyTest Salt Engine#
Salt Factories Engine For Salt.
Simple salt engine which will setup a socket to accept connections allowing us to know when a daemon is up and running
- saltfactories.utils.saltext.engines.pytest_engine.ext_type_encoder(obj)[source]#
Convert any types that msgpack cannot handle on it’s own.
- class saltfactories.utils.saltext.engines.pytest_engine.PyTestEventForwardClient(queue, client_running_event)[source]#
Bases:
ProtocolTCP Client to forward events.
- data_received(data)#
Called when some data is received.
The argument is a bytes object.
- eof_received()#
Called when the other end calls write_eof() or equivalent.
If this returns a false value (including None), the transport will close itself. If it returns a true value, closing the transport is up to the protocol.
- pause_writing()#
Called when the transport’s buffer goes over the high-water mark.
Pause and resume calls are paired – pause_writing() is called once when the buffer goes strictly over the high-water mark (even if subsequent writes increases the buffer size even more), and eventually resume_writing() is called once when the buffer size reaches the low-water mark.
Note that if the buffer size equals the high-water mark, pause_writing() is not called – it must go strictly over. Conversely, resume_writing() is called when the buffer size is equal or lower than the low-water mark. These end conditions are important to ensure that things go as expected when either mark is zero.
NOTE: This is the only Protocol callback that is not called through EventLoop.call_soon() – if it were, it would have no effect when it’s most needed (when the app keeps writing without yielding until pause_writing() is called).
- resume_writing()#
Called when the transport’s buffer drains below the low-water mark.
See pause_writing() for details.