Saspy

Added

- `None` Nothing added

Changed

- `Enhancement` A new requirement in Viya 4 called for a change in the SSO authentication mechanism, to support PKCE. So this
release provides support for that. There's nothing you have to do, but you will see a different message about the URL you need
to use to get an auth code to provide, when using that authentication mechanism. In short, every time you want to authenticate,
you get a new URL (it has its own unique code in it). This is displayed in the log same as the previous URL was, but unlike
previously, where the url was the same every time for the deployment, and you could already get a code and provide it to SASsession(),
this is a unique URL every time. So you can't get an authcode ahead of time. Don't fuss at me, I don't like it either. If you need
help, open an issue and I'll see what I can do.

Fixed

- `None` Nothing fixed

Removed

- `None` Nothing removed

Added

- `Enhancement` Per internal tester request, I've added an option for the STDIO access method to provide an amount of time for
SAS to terminate before killing the process, in the endsas() method. I've always waited up to 5 seconds from the subprocess
to terminate after requesting SAS shutdown, which is normally fine. If it takes longer, I kill the process. In this case,
SAS runs with some internal testing options which causes processing at termination, and takes longer than 5 seconds. So I've
added an option to allow me to wait longer before terminating the process which will allow this extra termination processing
to complete. This isn't a usual option customers would set, but it's there either way. The option is `termwait` and it takes an
integer number of seconds. In this case, the config def required: `'termwait': 60,` to get it to work as expected.

Changed

- `None` Nothing changed

Fixed

- `None` Nothing fixed

Removed

- `None` Nothing removed

Added

- `None` Nothing added

Changed

- `None` Nothing changed

Fixed

- `None` Nothing fixed

Removed

- `Enhancement` Per user request, I've added the ability to request a keepalive thread in the IOM access method.
I added this in V5.9.0, but then found that this could deadlock the IOM access method if the keepalive thread executed while in the middle
of one of my SASPy methods; which I didn't think would be the case, but I didn't happen to have it happen. When it
does, it can deadlock everything. So, I'm removing this feature with this release. It just doesn't work as expected.

Added

- `None` Nothing added

Changed

- `Enhancement` Per user request, I've added the ability to request a keepalive thread in the IOM access method.
The workspace server has a timeout option (defined in metadata), which usually defaults to 60 minutes. If no interaction
happens in that amount of time since the last interaction, the Workspace server will terminate itself. I've added an
option `keepalive` for the IOM access method that can be defined in the Configuration Definition or on SASsession(keepalive=50) to
specify you want this thread created and how many minutes in between interactions. So, if you're Workspace server has
a timeout of 60 min, you can specify `'keepalive' : 50,` in your config def to have saspy send a request every 50 min
so the timeout doesn't happen, and keep your session connected until you terminate it. The default is, of course, the
current behavior which is no keepalive thread.


Fixed

- `None` Nothing fixed

Removed

- `None` Nothing removed

Added

- `None` Nothing added

Changed

- `Enhancement` Per user request, I've added the ability to CANCEL submit()'ed code in both the IOM and HTTP
access methods. Until now you would see a message like the following if you tried to interrupt a submit:
`SAS attention handling is not yet supported over IOM. Please enter (T) to terminate SAS or (C) to continue.`
But now, with the ability to cancel long running code, you will see something like this instead:
`Please enter (T) to Terminate SAS or (C) to Cancel submitted code or (W) continue to Wait.`
If you choose 'C' then I can now use the API to tell the server to terminate whatever was being executed and
come back immediately, so you can then run other code. Also, for IOM, I cancel any code in endsas() so that the
workspace server terminates immediately instead of only after whatever is running finishes.


Fixed

- `None` Nothing fixed

Removed

- `None` Nothing removed

Added

- `None` Nothing added

Changed

- `Enhancement` Per user request, I've added the ability to have the SASLOG returned from the submit methods
be HTML with ERROR:, WARNING: and NOTE: lines colorized like in other SAS UI's. This is how the SAS_Kernel for
Jupyter colors it's LOG and how the log returned in the SAS_Results object in SASPy colors that log too. This
feature requires the Pygments package, so it is only available if that package in installed, else you get the
current behavior. The new `colorLOG` configuration key is how to set this. It's a boolean and defaults to False;
existing behavior. It can be specified in the Configuration Definition or on SASsession, like any other key.

Fixed

- `None` Nothing fixed

Removed

- `None` Nothing removed