session timeout causes ERRORs in log

Open
#162 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
backend

Research direction

Start by tracing the 15-minute inactive-session cleanup and the termination path that produces the logged ERROR. Review how code.sas is used for session execution, then verify that an inactive session can finish normally after the requested thank-you message is injected, without producing the current ERROR.

Written by the indexing model from the issue text.

Description

After 15 minutes we check if an active session is currently being utilised, and if not, we kill it.

The murder mechanism leaves an ERROR in the log as follows:

image

Rather than immediate termination we could simply ask the session to die with a simple %put thankyou for your service; injection to the the code.sas file.

The session should then execute normally and finish.

Dominant language
TypeScript
Stars
22
Forks
3
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sasjs/server

All issues in sasjs/server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.