forked from gitpod-io/openvscode-server
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump code to 1.78 #2
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* cli: add new control server messages for wsl * support cwd in spawn
* clean up extension recommendations * retain editor config extension
* Use custom node-gyp * Avoid using relative cd * Remove ia32 for Linux * Bump gulp-atom-electron; unblocks downloading PDBs * Add native-is-elevated to the scan
… correct order (microsoft#180410) Similarly to fed69ad, this adds a queue to serialize the processing of pause/continue events. Without this, if a pause and continue events are sent really fast, the pause handler will take longer to process than the continue handler and the state of the debugger UI will be paused when the debuggee is actually running. Fixes microsoft#180409
Fix Interactive Session widget
joh/linear parrotfish
* Fixes microsoft#3928 * Fixes CI
don't use role or aria-label attributes so that contents get read out
* Unexpected theme name showing up in web * incorperate feedback
Fixes `PieceTreeBase.equal` (fixes microsoft/vscode-internalbacklog#4025)
Last iteration I moved some RPC logic to use Tokios "codecs" to give them cancellation safety. These operate on streams of input data. While this worked at first, I failed to take into account that the byte buffer we read from the stream could have _more_ data than just the current message under load scenarios. We were discarding any extra data from the subsequent message. In most cases caused the next message "length" to be read from the middle of the next message, which usually (when parsed as a u32) was some number of gigabytes, then causing the connection to stall forever. Fixes microsoft#181284
* unc - adopt setting and handling of allow list * unc - set allow list on server too * unc - pick our patched node.js for now * bump electron * unc - ignore sync is not needed with machine scope * unc - use process set directly * 🆙 22.5.1
Option 'connection-secret' is deprecated: Use connection-token-file instead.
daniel-wachira
force-pushed
the
gp-code-1.78
branch
from
May 12, 2023 19:11
3e96af1
to
ee984c9
Compare
We can ignore the yarn.lock check failure. I've already verified that this builds ok with our build scripts. |
This reverts commit 8a7a90c. Use the --without-connection-token arg instead
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge into upstream release 1.78