Don't use a bounded channel for signaling that buffers have been opened
Blocking the sender could halt deserialization for no reason if nobody is consuming the notifications.
This commit is contained in:
parent
1313ca8415
commit
400a2fce58
2 changed files with 17 additions and 14 deletions
|
@ -4371,7 +4371,7 @@ mod tests {
|
|||
.read_with(guest_cx, |project, cx| {
|
||||
assert!(
|
||||
!project.has_buffered_operations(cx),
|
||||
"guest {} has buffered operations ",
|
||||
"guest {} has buffered operations",
|
||||
guest_id,
|
||||
);
|
||||
});
|
||||
|
@ -4779,8 +4779,9 @@ mod tests {
|
|||
} else {
|
||||
buffer.update(&mut cx, |buffer, cx| {
|
||||
log::info!(
|
||||
"Host: updating buffer {:?}",
|
||||
buffer.file().unwrap().full_path(cx)
|
||||
"Host: updating buffer {:?} ({})",
|
||||
buffer.file().unwrap().full_path(cx),
|
||||
buffer.remote_id()
|
||||
);
|
||||
buffer.randomly_edit(&mut *rng.lock(), 5, cx)
|
||||
});
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue