4.0.0-dev.6

Changes 4.0.0 (in development)

• Since Cate App is now designed to work inside of Jupyter Lab and standalone,
  The user login action is no longer required because users already log into
  JupyterLab. Therefore, all code dealing with user login and Cate service
  provisioning in the cloud has been removed. Other changes include:

  • Added a new user action to open Cate App in a browser tab available, if
    Cate App is initially opened in a JupyterLab widget.
  • Added a new user action to shut down the Cate server
    in order to release memory.
  • Removed the top level Files menu, because file management can
    be effectively done through JupyterLab.
  • Removed the user action to install Cate App as a Desktop PWA.
  • Removed proxy configuration from user preferences dialog.
  • Rephrased filesystem info from "sandboxed / full access" to
    "restricted / unrestricted".

• The following changes apply to the "local" data store because the server
  now serves local files from the current working directory. This has been
  done to let Cate integrated with Jupyter Lab pick up all datasets found
  in the Lab's workspace.

  • Users can now refresh the list of files from the "local" data store.
  • Users can no longer add/remove data sources to the "local" data store.
    This is a temporary change. We may reassign add/remove actions to perform
    a filtering on the local datasets.

• Now using workspace identifiers instead of base directories in resource
  URLs of the WebAPI. This way we no longer need to URL-encode workspace
  directories in WebAPI URLs, which did not work with
  jupyter-server-proxy.

• Slightly improved readability of dataset titles generated from identifiers
  if titles are missing.

Full Changelog: v3.1.4...v4.0.0-dev.6

3.1.4

Changes 3.1.4

• Updated default urls to authentication service

3.1.4-dev0

Changes 3.1.4 (in development)

• Updated to consider new keycloak url

3.1.3

Changes 3.1.3

• Changed the time until the message is shown that Cate
  will automatically shut down due to inactivity.
  Message is shown after 25% of server's auto-shutdown time. (#150)

• Show last remote container status after connection to server
  closed unexpectedly and give hint to users how to limit harm. (#150)

• Added button "Click here in case you need support"
  to start screen that refers to the ESA Helpdesk page. (#181)

Full Changelog: v3.1.2...v3.1.3

3.1.3-dev0

Changes in version 3.1.3 (in development)

• Added button "Click here in case you need support"
  to start screen that refers to the ESA Helpdesk page. (#181)
• Minor updates of external dependencies

3.1.2

Changes in version 3.1.2

• Fixed issue where no data sources were shown right after start. (#56)

3.1.1

Changes in version 3.1.1

• Added hint in DATA SOURCES panel addressing the case
  where loading seems to take forever.

• Now displaying a warning dialog when there is not much
  time left until the Cate backend service will automatically
  shut down due to service inactivity. (#164)

• If connection is closed, there are now two different message boxes.
  depending on whether the server was automatically shutdown or
  the connection closed unexpectedly.

• Outputting more information to investigate into
  unintentionally closed WebSocket connections:

  • Allow toasts to stay longer for such errors (2 minutes).
  • Provide more details on the console.

• No longer attempt to load in scratch workspaces at startup
  (avoid error message).

3.1.1-dev.0

Changes 3.1.1-dev.0

• Outputting more information to investigate into unintentionally closed WebSocket connections:
  • Allow toasts to stay longer for such errors (2 minutes).
  • Provide more details on the console.

3.1.0

Changes 3.1.0

• Adapted to Cate Web API 3.1.x which changed in an
  incompatible way. Dataset descriptors now have a data_type
  field instead of a type_specifier field in 3.0.x.
• Revert workaround from previous release that prevented user logins
  once a certain server-side degree of capacity utilisation was
  reached. (#156)

3.1.0.dev2

Changes 3.1.0 (in development)

• Ask again whether max number of users was reached