I have an extension that always shows the following warning (actual path differs each time):
> WARNING: IPC handle "/var/folders/w_/zfvfxj_x3nbd8wlj9p4ck3xc0000gn/T/vscode-d7124c14bae4868834641c7c08175ab90b7b0993a8.sock" is longer than 103 characters.
This path's length is 103 characters, which is the safe limit for macOS [1]. However the warning is still displayed because of the condition `>=` was used [2].
[1] https://nodejs.org/api/net.html#identifying-paths-for-ipc-connections
[2] bbd65f68bb
Co-authored-by: Dirk Bäumer <dirkb@microsoft.com>
* Sequence send calls.
* More send sequence work
* Make reader process in sequence
* Auto trigger delivery
* Don't pull on close since the document might be deleted.
* Fixes#886: Working extension inexplicably stopped sending document symbols
* Fixes#897: Header field name in jsonrpc Message has to be case-insensitive
* Perpare to publish tsconfig-gen
* Make root npm install work
* Add an empty ThirdPartyNotices.txt
* Add standard comment to ThirdPartyNotice
* Fix post publish step
* Merge into publish branch (#1112)
* Prepare to publish new packages
* Fix pipeline script
* Engineering - remove dependsOn properties (#1110)
* Add variables
* Initial attempt
* Remove unused parameters
* Change if clause
* Fix variables
* Add back parameters
* Comment out code
* Add Jsonrpc
* Fingers crossed
* Add test platform for types
* Remove variables
* Remove dependsOn fields
Co-authored-by: Dirk Baeumer <dirkb@microsoft.com>
Co-authored-by: Ladislau Szomoru <3372902+lszomoru@users.noreply.github.com>
* Avoid referencing client from tests
* Make test depend on client only
* Handle uncaught exceptions.
* export Display
* Use default display
* Use correct default display
* Only execute client
* Correct display setting in run test
* Another try to set display correctly
* Use find process to find the right display for tests
* Reenable all packages
Co-authored-by: Ladislau Szomoru <3372902+lszomoru@users.noreply.github.com>
* Update pipeline script
* Run general npm install
* Add build platforms
* Compile text documents for server
* Add quality parameter
* Complete pipeline for textDocument
* Test publishing text documents
* More pipeline tweaking
* Get tests working in publish pipeline
* Make client pack work
* Minor cleanup
* Start using templates
* Make templates relative
* Self reference template
* Make template path absolute
* Fix wrong template reference
* Add pack steps
* More template use
* Add all target to protocl
* Compile tools when packing protocol
* Use templates for client package
* Experiment with package template
* Revert package template
* Delete package template
Dirk Bäumer
Sebastien Pouliot
dependabot[bot]
Matt Bierner
Artem Borzov
Ladislau Szomoru
Edward Wardell-Yerburgh
Erik Lilja