Commit Graph
554 Commits
Author SHA1 Message Date
Nathan Sobo e38e92cad3 Remove unnecessary step 2021-05-17 18:09:35 -06:00
Nathan Sobo 1831a22638 Explicitly install aarch64 target 2021-05-17 18:07:39 -06:00
Nathan Sobo 466bf44fea Install cargo-bundle if needed in script/bundle 2021-05-17 17:57:50 -06:00
Nathan Sobo 8cddbfc44a Focus on bundling 2021-05-17 17:51:48 -06:00
Nathan Sobo a182a5ccc7 Will you work please? 2021-05-17 17:51:06 -06:00
Nathan Sobo ff46521641 Can we skip caching because we're self hosted? 2021-05-17 16:48:03 -06:00
Nathan Sobo 62be9f1dd0 Run CI on tag pushes 2021-05-17 16:47:42 -06:00
Nathan Sobo 01ac894614 Add a release upload action 2021-05-17 16:38:56 -06:00
Nathan Sobo e5a5d0cc79 WIP 2021-05-14 10:58:02 -06:00
Antonio ScandurraandNathan Sobo 831265f33f WIP: Replace ropey with our own Rope
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-14 18:30:47 +02:00
Antonio ScandurraandNathan Sobo 1487b91359 Implement a Cursor for Rope
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-14 17:14:57 +02:00
Antonio ScandurraandNathan Sobo d69e9cc567 Clarify variable and method names
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-14 16:42:46 +02:00
Antonio Scandurra 2d7deda173 💄 2021-05-14 16:07:46 +02:00
Antonio Scandurra 6d9fb1fab8 📝 2021-05-14 16:00:45 +02:00
Antonio Scandurra 29d5586014 Add Rope::chunks 2021-05-14 15:19:03 +02:00
Antonio Scandurra 537d3f15a2 Better balancing of chunks on push 2021-05-14 15:07:30 +02:00
Antonio Scandurra 2337a961a6 Implement ::chars, ::to_point and ::to_offset for Rope 2021-05-14 14:44:19 +02:00
Antonio Scandurra 6ce5743af7 Increase leaf occupation for rope 2021-05-14 13:20:20 +02:00
Antonio Scandurra 9b34b4fd81 Don't underflow Rope chunks on append 2021-05-14 12:26:21 +02:00
Antonio Scandurra 81bc61c8a2 Start on a SumTree-based Rope implementation 2021-05-14 11:33:39 +02:00
Max BrunsfeldandNathan Sobo f3535b99fe Get tests passing using a slow rightmost_point impl
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-13 11:54:29 -07:00
fc304b3f1a Fix concurrent editing in buffer after using ropes
Co-Authored-By: Max Brunsfeld <max@zed.dev>
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-13 19:59:01 +02:00
Antonio ScandurraandMax Brunsfeld 4bdacb7cfd Get local buffer usage working with ropes
Randomized tests for remote edits are still not passing.

Co-Authored-By: Max Brunsfeld <max@zed.dev>
2021-05-13 19:48:55 +02:00
Antonio ScandurraandMax Brunsfeld 74798d6f7f WIP: Get the type checker passing...
...but not the borrow checker!

Co-Authored-By: Max Brunsfeld <max@zed.dev>
2021-05-13 19:24:03 +02:00
Antonio ScandurraandNathan Sobo ce93be6402 WIP
Co-Authored-By: Nathan Sobo <nathan@zed.dev>
2021-05-13 18:35:48 +02:00
Antonio Scandurra b28aaa3d47 Merge pull request #60 from zed-industries/fix-failures
Fix more test flakiness
2021-05-13 11:55:26 +02:00
Antonio Scandurra 73701cdef8 Increase timeout for fs-dependent conditions 2021-05-13 11:38:39 +02:00
Antonio Scandurra 4d2dbd982b Change buffer atomically when reloading from disk 2021-05-13 11:26:11 +02:00
Antonio Scandurra d9679063f7 Rely more on conditions for state derived after worktree changes 2021-05-13 11:25:29 +02:00
Antonio Scandurra 6994f91b65 Merge pull request #59 from zed-industries/more-resilient-fs-events
Use `flush_fs_events` more after performing synchronous fs mutations
2021-05-13 10:42:58 +02:00
Antonio Scandurra 1e11afd43e Use flush_fs_events more after performing synchronous fs mutations
I am not sure I have caught all the examples of this, but in general
I think we always want to perform a `flush_fs_events` as opposed to
`next_scan_complete` when doing synchronous I/O. Indeed, the file
system may inform us about the events caused by the just-performed
I/O over multiple batches, and `next_scan_complete` may return
before seeing all of them.

Note that this also removes a few assertions which were ensuring
that, on start, a worktree's file handle wouldn't know its deleted
status, even if the file didn't exist for sure on disk. However,
now that `file` is an async API, it's possible that by the time the
`FileHandle` is resolved, `Worktree` has already completed scanning.
We test a similar behavior further along in the test where those
assertions were removed, so it felt okay to proceed without them.
2021-05-13 10:25:16 +02:00
Max Brunsfeld a27ba01aed Merge pull request #54 from zed-industries/file-changed-on-disk
Handle buffers' files changing on disk from outside of Zed
2021-05-12 20:19:39 -07:00
Max BrunsfeldandAntonio Scandurra 368d8723ab Read file's mtime in background when getting a FileHandle
Co-Authored-By: Antonio Scandurra <me@as-cii.com>
2021-05-12 20:13:56 -07:00
Max Brunsfeld 9e54aa6471 Merge branch 'master' into file-changed-on-disk 2021-05-12 20:08:09 -07:00
Max Brunsfeld ba6bcd9a33 Merge pull request #57 from zed-industries/dropped-entities
Fix panic when an entity's ref count is decremented to 0 and then is incremented again
2021-05-12 20:03:24 -07:00
Max Brunsfeld 97cc639825 Remove dropped entities even if there are no effects to flush 2021-05-12 19:45:45 -07:00
Nathan Sobo 018d30cc00 Don't remove entities whose ref count has become positive again 2021-05-12 19:29:17 -06:00
Nathan Sobo d9392243f9 Remove dropped entities after every effect 2021-05-12 19:28:48 -06:00
Max Brunsfeld a053c3b5a0 Allow a longer timeout in buffer conflict test 2021-05-12 16:20:22 -07:00
Max Brunsfeld 3226435fc5 Merge branch 'master' into file-changed-on-disk 2021-05-12 16:20:03 -07:00
Max Brunsfeld 4a6919960e Merge pull request #56 from zed-industries/async-ctx
Simplify spawning and asynchronous code
2021-05-12 15:35:07 -07:00
Max Brunsfeld 4d075c38e0 Remove commented-out tests for spawn and spawn_stream 2021-05-12 15:27:58 -07:00
Nathan Sobo a792e53401 Pass a handle to the current view model when spawning
Most of the time, we'll want a way to get a reference back to the current view or model, so this facilitates that common case.
2021-05-12 15:28:59 -06:00
Nathan SoboandMax Brunsfeld f39e101ae2 Introduce AsyncAppContext and simplify spawning
Now when you call spawn in various context, you pass an FnOnce that is called with an AsyncAppContext and returns a static future. This allows you to write async code similar to how our tests work, borrowing the guts of the AsyncAppContext when needed to interact, but using normal async await semantics instead of callbacks.

Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com>
2021-05-12 15:16:49 -06:00
Max Brunsfeld 1eafa99c62 Merge pull request #55 from zed-industries/test-macros
Introduce a `gpui::test` macro for less ceremony when writing tests
2021-05-12 10:19:46 -07:00
Antonio ScandurraandMax Brunsfeld 78f4e93215 Use gpui::test for tests in gpui
Co-Authored-By: Max Brunsfeld <max@zed.dev>
2021-05-12 18:21:32 +02:00
Antonio ScandurraandMax Brunsfeld d6002dcc81 Use gpui::test in async tests in zed
Co-Authored-By: Max Brunsfeld <max@zed.dev>
2021-05-12 18:20:49 +02:00
Antonio Scandurra 630049eb8d Use gpui::test macro for synchronous tests in zed 2021-05-12 17:18:23 +02:00
Antonio Scandurra ba47eafe25 Introduce a gpui::test macro 2021-05-12 17:05:03 +02:00
Antonio Scandurra ed49b0ea34 Test prompting when saving while there's a conflict 2021-05-12 15:21:50 +02:00