V-Spark Online Help

Maintenance Fixes Since the Initial 3.4.3 Release

This section identifies fixes that were introduced in patch releases and hot fixes since the initial 3.4.3 release, and are therefore now included in the latest version of the 3.4.3 release. Maintenance versions and associated fixes are listed most recent to earliest:

  1. Google Chrome 83 Support Update - Chrome 83 now blocks all downloads initiated from or instantiated in a sandboxed iframe by default. This update enables V‑Spark to override that default behavior and allow file downloads. (3.4.3-13)

  2. Improved handling of email communication - Email notifications were updated to list email recipients in the BCC field of the message. Also, the TO field is now set to the application's global address. (3.4.3-12)

  3. Improved support to AWS S3 downloads - Improved download retry logic to account for possible issues during network transport. (3.4.3-11)

  4. Run V‑Spark on a Single Core - Enabled V‑Spark to run on a machine with a single core on its single CPU. (3.4.3-10)

  5. Eliminate Temporary File Leaks - Improved cleanup of temporary files. (3.4.3-10)

  6. Fix Application Reprocessing Failure - Improved mysql retry logic to reduce application processing errors. (3.4.3-10)

  7. Audio Duration Update - Improved how a file's audio duration is determined. (3.4.3-10)

  8. S3 Update - V‑Spark now fully supports signed S3 bucket requests for all AWS regions by adding support for the AWS Signature Version 4 Signing Process. Previously only Version 2 was supported. (3.4.3-10)

  9. Partial Content Requests - Some browsers, such as Google Chrome, specify a desired content range for cases such as fetching a piece of an audio file to play/seek in its embedded audio/video player. V‑Spark now honors partial content requests on the part of a browser by responding with 206 HTTP code and the piece of audio that was requested. (3.4.3-10)

  10. Elasticsearch connection management - Connections to Elasticsearch clients are now managed more effectively to prevent connection errors. (3.4.3-9)

  11. Folder ASR options - Expanded support for folder ASR options to allow adding values with multiple elements via the /config/folders API and GUI. Previously, both methods only supported simple ASR options with string, boolean, or numeric values. Boolean ASR option values must now be formatted properly for them to be correctly recognized. The Boolean values true and false must be entered in all lower case with no quotation marks. Values containing capital letters or contained within quotes (such as True or "false") are interpreted as string values, and not as Booleans. (3.4.3-8)

  12. Request API Content-type - The /request API status and details calls were returning output with the incorrect content-type value. The content-type has been restored to "application/json". (3.4.3-8)

  13. Cloud Tokens Checked Properly on Company Update - Updating a company that uses cloud tokens was pausing all of the company's folders due to a token check that was not matching the tokens to the folder servers properly. Tokens are now checked properly, enabling companies to update without their folders being paused. (3.4.3-7)

  14. Emotion Word Highlighting - Turning off "emotion" view on file details page will mitigate a known issue where phrase matches that overlap words marked with emotion are not highlighted. Now, opening a file details page from the application dashboard will turn off emotion by default, to improve the display of application phrase matches. (3.4.3-7)