search

sassoftware / sas_kernel

A Jupyter kernel for SAS. This opens up all the data manipulation and analytics capabilities of your SAS system within a notebook interface. Use the Jupyter Notebook interface to execute SAS code and view results inline.
Apache License 2.0
199 stars 82 forks source link

TypeError printed when running SAS code using the SAS Kernel. #85

Closed kybowm closed 1 year ago

kybowm commented 2 years ago

Describe the bug The notebooks in binder raise an error when I try to run them.

(The issue really stems from work in my local environment, which is described below, but since the problem appears in the binder notebooks too, I assume that's an easier troubleshooting environment.)

To Reproduce Steps to reproduce the behavior:

  1. Click on "Launch Binder" on the README page of the SAS Kernel repository.
  2. Open (for instance) the "SAS SQL Example" notebook.
  3. Run the first cell. (I've gotten the error with all SAS code that I've tried to execute in the SAS Kernel.) (Result: cell execution stalls and it looks like an error instance is printed, but it doesn't print a trace.)

Expected behavior I would expect.

Screenshots image

Enviornment (please complete the following information):

Additional context In my local environment, I can run SASPy commands successfully, so I assume it is not a SASPy configuration issue. I have not previously had a working SAS Kernel instance. It's possible that I'm overlooking a simple step, but in that case, it would be nice for that step to be explained in the binder notebook.

kybowm commented 2 years ago

Update: I can execute SAS code in the Python Kernel by using the %%SAS magic.

When I run the server locally, the server returns this trace: image

shenzj1994 commented 1 year ago

I felt like SAS is not willing to do any fix on those so they can keep people using their proprietary tool like SAS Enterprise Guide. I had the same issue too. It just throws this error while it was fine using saspy with Python. It did not even prompt me to enter either config name or username/password.

tomweber-sas commented 1 year ago

lol, no, nothing that devious :) It's simply that Jared, who wrote and supported this, left and no one has been tasked with supporting it now. I haven't looked at this repo in some time, but I can take a look to see what I see. I'm not familiar with this binder automation that this is referring to; I'm trying it now and it's taking forever to start, but it just finished and came up. I can't connect to SAS that it seems to be configured to try to connect to. It just doesn't work, I don't believe the SAS it's supposed to connect to is there anymore. I'm not sure if this is really supported anymore or if it was something Jared created for some demo purposes that no longer is actually up and running. This seems like it was just something created for SGF last year, and not actually still available. The failure from the SAS_kernel provides no indication of the problem, but just using SASPy shows that the SAS server isn't available, so there's no SAS to connect to. I think removing this binder link from the repo readme is the thing to do.

tomweber-sas commented 1 year ago

Turns out this was a demo environment for SGF 2 years ago. The SAS deployment that was used for this to connect to no longer exists which is why nothing can connect from this binder environment. I just removed the binder link from the readme, since it isn't a functioning environment. I'll close this out too, since it's no longer an issue.