node: Allow seed not to be connected on fetch
See code comment for explanation.
This commit is contained in:
parent
95e3b9673d
commit
5a46ded318
|
|
@ -555,8 +555,12 @@ where
|
||||||
error!(target: "service", "Session {from} does not exist; cannot initiate fetch");
|
error!(target: "service", "Session {from} does not exist; cannot initiate fetch");
|
||||||
return;
|
return;
|
||||||
};
|
};
|
||||||
debug_assert!(session.is_connected());
|
if !session.is_connected() {
|
||||||
|
// This can happen if a session disconnects in the time between asking for seeds to
|
||||||
|
// fetch from, and initiating the fetch from one of those seeds.
|
||||||
|
error!(target: "service", "Session {from} is not connected; cannot initiate fetch");
|
||||||
|
return;
|
||||||
|
}
|
||||||
let seed = session.id;
|
let seed = session.id;
|
||||||
|
|
||||||
match session.fetch(rid) {
|
match session.fetch(rid) {
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue