- 06 8月, 2019 1 次提交
-
-
由 Asher 提交于
-
- 03 8月, 2019 2 次提交
- 01 8月, 2019 1 次提交
-
-
由 Asher 提交于
- Don't use "any" for the API type. - Remove everything from the Coder API that can eventually be done through the VS Code API. - Move the event emission to our own client to minimize patching.
-
- 27 7月, 2019 2 次提交
- 24 7月, 2019 3 次提交
- 23 7月, 2019 1 次提交
-
-
由 Asher 提交于
-
- 20 7月, 2019 1 次提交
-
-
由 Asher 提交于
-
- 19 7月, 2019 6 次提交
- 20 5月, 2019 3 次提交
-
-
由 Asher 提交于
Since this will be a path in the binary that we don't want to create on the user's system. I also removed the option to override it; it doesn't seem like a great idea since you'd always want those builtin extensions. This way we also don't have to check if the option was passed and only create it if that was the case.
-
由 Asher 提交于
This isn't a real error event; we artificially emit it just in case something waiting to start is listening to the error event in order to clean up and/or restart.
-
由 Asher 提交于
* Allow setting paths for builtin exts and extra dirs The extra directories aren't used yet, just available from the environment service and to the shared process. * Utilize extra builtin extensions path * Utilize extra extensions directory * Fix cached mtimes for extra extension dirs * Simplify extension cache equality check
-
- 24 4月, 2019 1 次提交
-
-
由 John McCambridge 提交于
* Fix hash * Remove whitespace
-
- 23 4月, 2019 2 次提交
-
-
由 Kyle Carberry 提交于
-
由 Kyle Carberry 提交于
-
- 20 4月, 2019 2 次提交
-
-
由 Kyle Carberry 提交于
-
由 Kyle Carberry 提交于
-
- 18 4月, 2019 3 次提交
-
-
由 Asher 提交于
Mac was using its own thing. - Fixes #535 - Fixes #501
-
由 Kyle Carberry 提交于
-
由 Asher 提交于
-
- 16 4月, 2019 1 次提交
-
-
由 Asher 提交于
This normally happens in electron-main/main.ts but we don't run anything from there. Fixes #499.
-
- 09 4月, 2019 1 次提交
-
-
由 Asher 提交于
Since this is where it attempts to read it, this should solve the JSON errors for good.
-
- 08 4月, 2019 1 次提交
-
-
由 Kyle Carberry 提交于
-
- 06 4月, 2019 1 次提交
-
-
由 Asher 提交于
* Update VS Code to 1.33.0 * Fix slow file tree * Fix WindowsService fill * Provide `off` on event listeners * Fix webview * Fix double title bar and missing preferences on Mac * Bump VS Code version in Travis config * Fix black dialog text (again) * Fix shared process not starting
-
- 02 4月, 2019 1 次提交
-
-
由 Asher 提交于
Registering returns an instance that lets you retry and recover without needing to keep passing the name everywhere. Also refactored the shared process a little to make better use of the retry and downgraded stderr messages to warnings because they aren't critical.
-
- 29 3月, 2019 1 次提交
-
-
由 Asher 提交于
* Make proxies decide how to handle disconnects * Connect to a new terminal instance on disconnect * Use our retry for the watcher * Specify method when proxy doesn't exist * Don't error when closing/killing disconnected proxy * Specify proxy ID when a method doesn't exist * Use our retry for the searcher Also dispose some things for the watcher because it doesn't seem that was done properly. The searcher also now starts immediately so there won't be lag when you perform your first search. * Use our retry for the extension host * Emit error in parent proxy class Reduces duplicate code. Not all items are "supposed" to have an error event according to the original implementation we are filling, but there is no reason why we can't emit our own events (and are already doing so for the "disconnected" event anyway). * Reconnect spdlog * Add error message when shared process disconnects * Pass method resolve to parse * Don't pass method to getProxy It doesn't tell you anything that trace logging wouldn't and has no relation to what the function actually does. * Fix infinite recursion when disposing protocol client in tests
-
- 27 3月, 2019 1 次提交
-
-
由 Asher 提交于
* Replace evaluations with proxies and messages * Return proxies synchronously Otherwise events can be lost. * Ensure events cannot be missed * Refactor remaining fills * Use more up-to-date version of util For callbackify. * Wait for dispose to come back before removing This prevents issues with the "done" event not always being the last event fired. For example a socket might close and then end, but only if the caller called end. * Remove old node-pty tests * Fix emitting events twice on duplex streams * Preserve environment when spawning processes * Throw a better error if the proxy doesn't exist * Remove rimraf dependency from ide * Update net.Server.listening * Use exit event instead of killed Doesn't look like killed is even a thing. * Add response timeout to server * Fix trash * Require node-pty & spdlog after they get unpackaged This fixes an error when running in the binary. * Fix errors in down emitter preventing reconnecting * Fix disposing proxies when nothing listens to "error" event * Refactor event tests to use jest.fn() * Reject proxy call when disconnected Otherwise it'll wait for the timeout which is a waste of time since we already know the connection is dead. * Use nbin for binary packaging * Remove additional module requires * Attempt to remove require for local bootstrap-fork * Externalize fsevents
-
- 19 3月, 2019 1 次提交
-
-
由 Kyle Carberry 提交于
-
- 15 3月, 2019 1 次提交
-
-
由 Kyle Carberry 提交于
-
- 14 3月, 2019 1 次提交
-
-
由 Asher 提交于
There is a window between when the stat is made and the result makes it back to the client where a file is created or deleted and it won't be a part of that stat. To fix it, I added a new property signaling that we got some changes since starting the stat and should run the stat again because we have no way of knowing whether the currently running stat will include the new changes or not.
-
- 12 3月, 2019 1 次提交
-
-
由 Asher 提交于
-
- 09 3月, 2019 1 次提交
-
-
由 Asher 提交于
Forgot to move this to the new file when upgrading to 1.32.0.
-