Tags: jchristov/code-server
Tags
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
Tweak bug report template These checkboxes keep getting checked despite the submitter using an insecure context or not having tested upstream. I think two things are at play here: 1. Folks might be interpreting "cannot reproduce" as "did not reproduce" or "did not have time to reproduce". 2. The checkboxes are required to submit the issue so folks might be marking them just so they can get their issue submitted; maybe they are not even reading the checkboxes and are just seeing the error that they need to be marked and blindly marking them because while in some cases folks will add "I had to check this but it is not true", usually they say nothing. In any case, hopefully these changes make the checkboxes more accurate, and then if they are unchecked we can ask them to go reproduce in VS Code or use a secure context or whatever the case may be.
Ensure we only ever set workspace initialized to true This is just a guard in case there are paths where the workspace is already marked as initialized but the workspace configuration is not and we end up actually un-initializing it.
Use machine settings for e2e tests User settings are browser-based so use machine settings instead.
Update Code to 1.83.1 (coder#6488) * Update Code to 1.83.1 * Patch out lookbehind for Safari support Not sure why it needs a lookbehind unless a number followed by a capital letter is not supposed to be considered a new word, which seems wrong to me. The tests do not contain any numbers so I can only guess. --------- Co-authored-by: Asher <ash@coder.com>
Update Code to 1.83.1 (coder#6488) * Update Code to 1.83.1 * Patch out lookbehind for Safari support Not sure why it needs a lookbehind unless a number followed by a capital letter is not supposed to be considered a new word, which seems wrong to me. The tests do not contain any numbers so I can only guess. --------- Co-authored-by: Asher <ash@coder.com>
Use code-server commit in product.json Also remove github.com from the trusted domains. This causes the browser to block the popup instead (probably because the space between interaction and popup is too great), which is difficult to notice in Chromium. Even in Firefox with the extra bar they add at the top it can be easy to miss.
PreviousNext