mirrors/zed
1
0
Fork 0
mirror of https://github.com/zed-industries/zed.git synced 2025-02-03 17:44:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 6
zed/crates/collab
History
Conrad Irwin 0b1b758f02 Fix leaking test contexts 
I was unable to run the collab tests locally because I would run out of
file descriptors.

From some digging it turned out that tokio allocates a new file
descriptor to do work on the CurrentThread using KQUEUE.

We create a new tokio Runtime with each database connection, and these
database connections were being retained by the Client, which is
retained by the Context.

Cleaning up our leaked contexts fixes the problem (though does make me
wonder if a different approach might be preferrable).
2024-01-22 23:05:54 -07:00
..
k8s Deploy tweaks 2024-01-05 13:24:29 -07:00
migrations Add requires_zed_cla column to channels table 2024-01-22 16:41:24 -08:00
migrations.sqlite Add requires_zed_cla column to channels table 2024-01-22 16:41:24 -08:00
src Fix leaking test contexts 2024-01-22 23:05:54 -07:00
.admins.default.json Make zed-local support opening 5 or 6 zed instances 2024-01-18 12:18:12 -08:00
.env.toml
admin_api.conf Run postgrest as part of foreman 2023-09-13 12:32:15 -07:00
basic.conf
Cargo.toml collab 0.40.0 2024-01-22 17:30:55 -08:00
README.md

README.md

Zed Server

This crate is what we run at https://collab.zed.dev.

It contains our back-end logic for collaboration, to which we connect from the Zed client via a websocket after authenticating via https://zed.dev, which is a separate repo running on Vercel.