M3T009 |
SAS Studio 3.82 |
Issue(s) Addressed: | Introduced: |
69660 | A sign out from SAS® Studio 3.8 Enterprise might occur unexpectedly |
M3T001 |
70109 | New variables that you add in a SAS® Studio 3.x process flow do not show up in the query |
M3T001 |
66173 | The code editor in SAS® Studio generates incorrect characters after you enter a right parenthesis followed by an equal sign (=) |
M3T002 |
70340 | The creation of very large log files in SAS® Studio could cause excessive and retained heap usage on SASServer2_1 |
M3T002 |
70343 | Opening ODBC or Postgres tables from SAS® Studio (Enterprise) 3.82 might generate a dialog box with a 415 status message |
M3T002 |
70362 | SAS® Studio (Basic) 3.81 and 3.82 releases contain JAR files with known vulnerabilities |
M3T002 |
70465 | Latency occurs in SAS® Studio 3.82 when a server directory contains thousands of files |
M3T003 |
70436 | Attempting to commit changes in SAS® Studio 3.82 with the Git User Interface fails with the error, "An unknown error occurred..." |
M3T004 |
70500 | Saving is not functional when you attempt to create a new folder in SAS® Studio 3.82 |
M3T004 |
70499 | Filtering data using a DATETIME variable does not return all matching results |
M3T006 |
70695 | The AllowDownload configuration setting limits the ability to download code and data only within the context of SAS® Studio functions |
M3T006 |
70819 | SAS® Studio 3.x stops responding and displays the message "Getting history" when attempting to open the history for a Git repository |
M3T006 |
70832 | SAS® Studio (Basic) might not display full results for the "Errors, Warnings, or Notes" section in in the log output |
M3T006 |
70878 | Data sets that are renamed with CHANGE statement are not displayed on the "Output Data" tab in SAS® Studio 3.x |
M3T008 |
70958 | Font ligature might need to be removed in order to correctly display codes in SAS® Studio programs |
M3T009 |
70981 | SAS® Studio Single-User contains a version of Apache Tomcat that is affected by CVE-2024-34750 |
M3T009 |
|
D indicates that the Documentation has special pre-installation, post-installation or other unique instructions not commonly used for hot fix deployment. |