BookmarkSubscribeRSS Feed

Create an "FIFO stack" of log references "in" each node.  When a new log listing for a node is created because the node's operation ran, "push" the new log on the stack and "pop" the oldest one off and discard it.  Create a way to view prior logs saved in the "stack".  Keep three logs by default, allow for more or less by providing a setting to control stack array length.

 

You never need to see an old log result, until you do  When you do, you just ran something and discarded the log result you wanted to review.

6 Comments
Reeza
Super User

Like in SAS Studio where you can click on the clock icon and see the old code but instead see the log?

PhilC
Rhodochrosite | Level 12

I'm not familiar, ....  Yes and No.  The website I'm reading uses a clock icon to schedule a process.  I don't want to confuse this with that.  But I probably do want something like the "Submission History Button".  If there is submission history, shouldn't there be a history for both code and log?

 

How-to-run-SAS-Studio-5-program-on-a-schedule 

PhilC
Rhodochrosite | Level 12

There is a discussion about how to use GitHub with Enterprise Guide, to keep track of changing code.  I just want a history of the most recent runs.

LeliaM
SAS Employee
Status changed to: Open

I will pass your feature request to development so they can look into providing this ability in a future release of SAS Studio.

Casey_SAS
SAS Employee
Status changed to: Under Consideration
 
rgfgdx
Calcite | Level 5

I agree strongly with this. Save the Results and Log of previous Runs, please! I am just using EG 8.2 after spending 12 years using Base SAS and when using large datasets and rerunning often when debugging and doing data manipulation, it slows me down greatly to not have previous logs and results to look back to. It does not make any sense to me why this is not available. It's incredibly annoying.