1. 18 12月, 2021 2 次提交
    • A
      Implement last opened functionality (#4633) · c4c480a0
      Asher 提交于
      * Implement last opened functionality
      
      Fixes https://github.com/cdr/code-server/issues/4619
      
      * Fix test temp dirs not being cleaned up
      
      * Mock logger everywhere
      
      This suppresses all the error and debug output we generate which makes
      it hard to actually find which test has failed.  It also gives us a
      standard way to test logging for the few places we do that.
      
      * Use separate data directories for unit test instances
      
      Exactly as we do for the e2e tests.
      
      * Add integration tests for vscode route
      
      * Make settings use --user-data-dir
      
      Without this test instances step on each other feet and they also
      clobber your own non-test settings.
      
      * Make redirects consistent
      
      They will preserve the trailing slash if there is one.
      
      * Remove compilation check
      
      If you do a regular non-watch build there are no compilation stats so
      this bricks VS Code in CI when running the unit tests.
      
      I am not sure how best to fix this for the case where you have a build
      that has not been packaged yet so I just removed it for now and added a
      message to check if VS Code is compiling when in dev mode.
      
      * Update code-server update endpoint name
      c4c480a0
    • J
      chore: use readonly deploy key for preview (#4645) · b990dabe
      Jonathan Yu 提交于
      b990dabe
  2. 17 12月, 2021 4 次提交
  3. 16 12月, 2021 5 次提交
  4. 15 12月, 2021 3 次提交
  5. 11 12月, 2021 2 次提交
    • J
      release: 4.0.0 (#4597) · c77999bc
      Joe Previte 提交于
      * chore(release): bump version to 4.0.0
      
      * Bump test plugin code-server engine
      Co-authored-by: NAsher <ash@coder.com>
      c77999bc
    • A
      Add separate function for VS Code arguments (#4599) · 9e583fa5
      Asher 提交于
      The problem before was that the pop() caused the open in existing
      instance functionality to break because the arguments no longer
      contained the file.
      
      We could simply remove the pop() but since `workspace` and `folder` are
      not CLI arguments I think it makes sense to handle them in a separate
      function which can be called at the point where they are needed.  This
      also lets us de-duplicate some logic since we create these arguments in
      two spots and lets us skip this logic when we do not need it.
      
      The pop() is still avoided because manipulating a passed-in object
      in-place seems like a risky move.  If we really need to do this we
      should copy the positional argument array instead.
      9e583fa5
  6. 10 12月, 2021 1 次提交
  7. 09 12月, 2021 1 次提交
    • A
      Fix relative paths (#4594) · 4b4ec378
      Asher 提交于
      * Add tests for relativeRoot
      
      * Remove path.posix.join
      
      Since this is for file system paths it feels incorrect to use it on
      URL paths as they are different in many ways.
      
      * Rewrite cookie path logic
      
      Before we relied on the client to resolve the base given to it by the
      backend against the path.
      
      Instead have the client pass that information along so we can resolve it
      on the backend.  This means the client has to do less work.
      
      * Do not remove out directory before watch
      
      This is re-used for incremental compilation.
      
      Also remove del since that was the only use (and we can use fs.rmdir in
      the future if we need something like this).
      
      * Remove unused function resolveBase
      4b4ec378
  8. 08 12月, 2021 3 次提交
    • A
      Fix spawning code-server within code-server (#4590) · 9d9f3a41
      Asher 提交于
      * Remove extra VS Code CLI spawn
      
      We already spawn VS Code's CLI when necessary in the lines below.
      Having the CLI spawn unconditionally when in a VS Code environment makes
      it impossible to run code-server within code-server (for example to
      develop it).
      
      * Update VS Code
      
      This sanitizes our environment variables so code-server does not always
      think it is a child spawn.
      
      Fixes https://github.com/cdr/code-server/issues/4519.
      9d9f3a41
    • A
      Remove excessive reloading before VS Code is ready (#4589) · c3eb9b80
      Asher 提交于
      The watch script was reloading the web server after every extension
      compilation which is not necessary plus VS Code will not even be ready
      at that point anyway.
      
      Instead restart when the main compilation is finished.  The string to
      match with includes a "with" because otherwise it would match "Finished
      compilation extensions" which is not the main compilation task where we
      actually need to restart the web server.
      
      I also replaced this.log with console.log because the former does not
      include a newline and it appears we want newlines with all
      these (otherwise the next log starts on the same line which looks odd).
      
      I removed the cache clean as well because the cache is meant to stay
      there to speed up builds.
      c3eb9b80
    • J
  9. 07 12月, 2021 2 次提交
  10. 02 12月, 2021 1 次提交
    • T
      Proxy path fixes (#4548) · 62b3a6fd
      Teffen 提交于
      * Fix issue where HTTP error status codes are not read.
      
      * Fix issues surrounding sessions when accessed from a proxy.
      
      - Updated vscode args to match latest upstream.
      - Fixed issues surrounding trailing slashes affecting base paths.
      - Updated cookie names to better match upstream's usage, debuggability.
      
      * Bump vendor.
      
      * Update tests.
      
      * Fix issue where tests lack cookie key.
      Co-authored-by: NAsher <ash@coder.com>
      62b3a6fd
  11. 30 11月, 2021 2 次提交
  12. 23 11月, 2021 2 次提交
  13. 20 11月, 2021 4 次提交
  14. 18 11月, 2021 1 次提交
  15. 17 11月, 2021 2 次提交
    • A
      Fix watcher not restarting code-server on VS Code compilation (#4520) · cd26f84b
      Asher 提交于
      The "Starting watch-client" string no longer appears in the latest build
      output.  We could look for "Finished compilation with" to avoid
      restarting when other tasks restart (since they also include the name
      i.e. "Finished compilation extensions with 0 errors") but I figure we
      might as well restart code-server when any compilation task completes in
      case other tasks include changes that need to be reloaded.
      cd26f84b
    • J
      fix NOTE.txt (#4515) · ccb9d948
      Jinu 提交于
      ccb9d948
  16. 16 11月, 2021 2 次提交
  17. 15 11月, 2021 1 次提交
  18. 13 11月, 2021 2 次提交