Update GAMS to version 39.1.0.

Bug fixes

• Fix issue issue where the event manager could hang indefinitely when receiving a canceled job.

New features

• UI: Add charts when viewing a user's usage data.
• UI: Engine SaaS users can now select a default instance.
• UI: Minor restructuring of job submission form.

Bug fixes

• Fixed an issue in the GET /usage endpoint when recursively querying usage data for an inviter as root admin. In this case, the root admin usage data was also included.

API Changes

• The maximum length for text entries is now 10 MB. It can be configured via the new /configuration endpoint.

New features

• It is now possible to tag a (Hypercube) job with a human-readable string to make it easier to identify.
• Engine licences are now tied to a specific Engine installation. Old licences will continue to be accepted and work just as before. To learn more about how to activate new Engine licenses, read here.
• Engine now supports webhooks as a way to be notified when a job is finished. Webhooks are disabled by default, but can be enabled via the new configuration API (either for administrators only or for everyone).
• When registering models (POST/PATCH /namespaces/{namespace}/models/{model}), you can now specify that model files should be protected from being overwritten (protect_model_files parameter). Together with INEX files, you can thus protect the intellectual property of your models.
• Jobs can now be shared with user groups. Any user with access to this group can then access the job (view the job details, cancel the job, download/delete the results, etc.).

Bug fixes

• The query for usage data (GET /usage/) by the first admin with recursive=true did not contain any usage data of this admin.

Update GAMS to version 38.3.0.

Update GAMS to version 38.2.1.

Update GAMS to version 38.2.0.

Bug Fixes

• Fix issue with sorting by username, model and namespace when listing jobs, listing hypercubes and listing cleanup entries.
• Fix layout issue with Engine UI when many namespaces are present.

Update GAMS to version 38.1.0.

API Changes

• The minimum length for passwords has been increased to 8 characters.
• The maximum length for namespace names has been increased to 100 characters.

Bug fixes

• Fix issue where deleting users did not work in certain situations.
• Fix issue where retrieving user details of a specific user did not work in certain situations.

New features

• The installation script now supports specifying the default admin password via the -a switch.
• UI: String columns in tables rendered client-side (users, models) can now be filtered.

Update GAMS to version 37.1.0.

Breaking Changes

• This release does not contain any breaking changes. In the next 3rd release stream entries and partial logs will return 410 instead of 308 when the stream is ended.

New features

• The installation script now supports specifying the path where GAMS Engine is mounted via the -m switch.
• The access scope of JWT can now be restricted.
• The maximum expiration time of JWT was increased to 186 days.
• JWT can now be invalidated via the new /auth/logout endpoint.
• The worker container now marks the GAMS process as the first candidate for the Out-of-Memory killer.
• The following containers accept the new GMS_RUNNER_LOG_SHOW_MSEC environment variable to add milliseconds to timestamps in log entries:
  • Broker*
  • Worker
  • Cleaner
  • Hypercube Unpacker
  • Hypercube Appender
  • Dependency Checker
  • Job Watcher
  • Job Spawner
  • Job Cleaner
  • Job Canceler
  Setting GMS_RUNNER_LOG_SHOW_MSEC environment variable to 'true' will change the logging format. Not setting it or setting it to anything else will have no effect. For example, a log from the worker container: [17/10/2021 14:58:47] INFO #: Start consuming on signal queue Would become: [17/10/2021 14:58:47.084] INFO #: Start consuming on signal queue

API Changes

• DELETE /jobs/{token}/stream-entry/{entry_name} now returns queue_finished which indicates whether the stream entry queue has been finished.
• GET /hypercube/ labels field also includes resource_warning which can be "none", "memory" or "disk".
• GET /jobs/{token} labels field also includes resource_warning which can be "none", "memory" or "disk".
• GET /usage/ labels field also includes resource_warning which can be "none", "memory" or "disk".
• POST /auth/, creating JWT token via basic auth, is not considered deprecated anymore since it might be used to create a new token using another token.
• GET /users/ now returns the details of the logged in user if user is not admin or inviter. Previously a 403 Forbidden error was thrown if the username parameter was not explicitly set to the name of the logged in user.
• Now it is possible to use stream/text entries to track files located in subdirectories.
  • New endpoint: GET /jobs/{token}/text-entry?entry_name={entry_name}. It does exactly what GET /jobs/{token}/text-entry/{entry_name} does but accepts the entry name in query string to allow querying inside the directories. Operation ID is: queryJobTextEntry
  • New endpoint: HEAD /jobs/{token}/text-entry?entry_name={entry_name}. It does exactly what HEAD /jobs/{token}/text-entry/{entry_name} does but accepts the entry name in query string to allow querying inside the directories. Operation ID is: queryJobTextEntryInfo
  • New endpoint: DELETE /jobs/{token}/stream-entry?entry_name={entry_name}. It does exactly what DELETE /jobs/{token}/stream-entry/{entry_name} does but accepts the entry name in query string to allow querying inside the directories. Operation ID is consumeStreamEntry

Bug fixes

• Fix issue where sparse output of stream entries caused connection timeouts.
• Introduced performance improvements for stream entries.
• CRITICAL: Fix security issue that allowed an authorized attacker to leak system information.

Breaking changes

• The log file is no longer automatically appended to the array of text entries. GAMS log files can get quite large and storing them can consume significant resources. Therefore, this is now opt-in: To save log files, you must explicitly add them to the text_entries array.

New features

• Models can now be assigned to user groups to limit the visibility of the model.
• New string interface for INEX files.
• The results of GET /cleanup/results can now be filtered by namespace.
• Text entries and stream entries can now be specified when creating/updating a model.

Bug fixes

• CRITICAL: Fix a security issue that can lead to privilege escalation if an attacker has access to an inviter account.
• Fix issue with updating models via Python client.

API Changes

• POST /jobs/ accepts query parameter inex_string
that can be used instead of inex_file
• POST /hypercube/ accepts query parameter inex_string that can be used instead of inex_file
• POST /namespaces/{namespace}/models/{model} accepts query parameter inex_string that can be used instead of inex_file
• PATCH /namespaces/{namespace}/models/{model} accepts form parameter inex_string that can be used instead of inex_file
• Admins can no longer make a user an admin if their inviter is not also an admin.

Update GAMS to version 36.2.0.

Bug fixes

• Fix issue with updating models via Engine UI.

New features

• When inviting users, Engine now supports assigning a GAMS license when invited by an admin.
• Now, admins can change usernames. Changing username invalidates previously generated JWT tokens.
• Now, changing password invalidates previously generated JWT tokens.
• Significantly reduced image size of Engine components.

Bug fixes

• Fix issue with inheriting licenses from admins.
• Fix issue where license inheritance did not work in certain situations.

API Changes

• When listing invitations, quotas, user groups, and GAMS license attached to the invitation are also listed.
• All the endpoints that return datetimes ensure that the datetimes have timezone info. For example, if an old return value were 2021-08-04T17:10:15.000000, which did not indicate the timezone, the new return value would be 2021-08-04T17:10:15.000000+00:00.