Name	Size	Mode	Actions
amp.cpython-310.pyc	21783	0644	editdlrm
backoff.cpython-310.pyc	2137	0644	editdlrm
base64.cpython-310.pyc	333	0644	editdlrm
bootstrap.cpython-310.pyc	2277	0644	editdlrm
bpickle.cpython-310.pyc	6658	0644	editdlrm
cli.cpython-310.pyc	581	0644	editdlrm
cloud.cpython-310.pyc	1861	0644	editdlrm
compat.cpython-310.pyc	606	0644	editdlrm
config.cpython-310.pyc	10218	0644	editdlrm
disk.cpython-310.pyc	4080	0644	editdlrm
encoding.cpython-310.pyc	759	0644	editdlrm
fd.cpython-310.pyc	951	0644	editdlrm
fetch.cpython-310.pyc	7235	0644	editdlrm
format.cpython-310.pyc	892	0644	editdlrm
fs.cpython-310.pyc	3593	0644	editdlrm
gpg.cpython-310.pyc	2170	0644	editdlrm
hashlib.cpython-310.pyc	408	0644	editdlrm
jiffies.cpython-310.pyc	1352	0644	editdlrm
juju.cpython-310.pyc	807	0644	editdlrm
lock.cpython-310.pyc	1065	0644	editdlrm
log.cpython-310.pyc	671	0644	editdlrm
logging.cpython-310.pyc	2366	0644	editdlrm
message.cpython-310.pyc	2127	0644	editdlrm
monitor.cpython-310.pyc	7200	0644	editdlrm
network.cpython-310.pyc	9015	0644	editdlrm
os_release.cpython-310.pyc	1249	0644	editdlrm
persist.cpython-310.pyc	17787	0644	editdlrm
plugin.cpython-310.pyc	2565	0644	editdlrm
process.cpython-310.pyc	4383	0644	editdlrm
reactor.cpython-310.pyc	10108	0644	editdlrm
schema.cpython-310.pyc	7155	0644	editdlrm
scriptcontent.cpython-310.pyc	674	0644	editdlrm
sequenceranges.cpython-310.pyc	4920	0644	editdlrm
store.cpython-310.pyc	1220	0644	editdlrm
sysstats.cpython-310.pyc	7765	0644	editdlrm
tag.cpython-310.pyc	879	0644	editdlrm
testing.cpython-310.pyc	26194	0644	editdlrm
timestamp.cpython-310.pyc	436	0644	editdlrm
twisted_util.cpython-310.pyc	4736	0644	editdlrm
user.cpython-310.pyc	908	0644	editdlrm
versioning.cpython-310.pyc	1648	0644	editdlrm
vm_info.cpython-310.pyc	2824	0644	editdlrm
warning.cpython-310.pyc	615	0644	editdlrm
__init__.cpython-310.pyc	352	0644	editdlrm

o ¶žâcN ã@sdZe
ƒZd
d„ZdS)z/Helpers for reliable persistent message queues.cCsŠd
}| ¡}|
|| 
¡kr| ¡
d}t}n"|
|kr$| ¡
|
|}n|
|| ¡kr1d}t}n| ¡|
|}| |¡

| |
¡

|S)a™Our peer has told us what it expects our next message's sequence to be. Call this with the message store and sequence number that the peer wants next; this will do various things based on what *this* side has in its outbound queue store. 0. The peer expects a sequence number from the server that is too high, the difference greater than pending messages in the peer. We flush the older messages in queue b/c the server does not want old or ancient messages, however we also reset the offset so that the pending messages are resent. Then we resynchronize by returning RESYNC. See LP: #1917540 1. The peer expects a sequence greater than what we last sent. This is the common case and generally it should be expecting last_sent_sequence+len(messages_sent)+1. 2. The peer expects a sequence number our side has already sent, and we no longer have that message. In this case, just send *all* messages we have, including the previous generation, starting at the sequence number the peer expects (meaning that messages have probably been lost). 3. The peer expects a sequence number we already sent, and we still have that message cached. In this case, we send starting from that message. If the next expected sequence from the server refers to a message older than we have, then L{RESYNC} will be returned. Né)Úget_sequenceÚcount_pending_messagesÚdelete_old_messagesÚRESYNCÚget_pending_offsetÚset_pending_offsetÚset_sequence)ÚstoreÚ next_expectedÚretÚold_sequenceÚpending_offset©rú7/usr/lib/python3/dist-packages/landscape/lib/message.pyÚgot_next_expecteds(










ÿ
ÿ 

rN)Ú__doc__ÚobjectrrrrrrÚ
s