-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple adopath additions in profile.do breaks the kernel #378
Comments
You should never need to touch or delete anything in that folder. Given that the error is
It seems like that should be completely orthogonal to your |
@kylebarron sorry for the confusion; I only did that to recreate a fresh install state but it doesn't really matter whether the cache files are in place or not; the problem is always there. To demonstrate the problem again clearly, I did the following:
in other words, none of the ado paths specified in
after which kernel becomes unresponsive. Here is the log: console_debug.log I can replicate this every single time: whenever there is an incongruence between the adopaths defined in |
I don't know how adopaths work, (I don't even use Stata anymore), but I'm guessing you're overwriting a path that the kernel expects. See here we define a custom adopath: stata_kernel/stata_kernel/stata_session.py Line 104 in 393feaa
|
@gaksaray There are different things here:
Since they don't appear in your log, I wonder whether your profile.ado is in the right place. What is
?
|
It is always read by the kernel just fine if it consists only one or two ado paths. Things get weird if the does more than that.
|
@gaksaray I am a bit confused, so let me recap:
Does this also happen if you put things in |
Exactly correct so far.
No, it doesn't crash. (This is because the previous steps have already produced log files in
It gives me a prompt. I type
Unfortunately it does. I am attaching a screen record to demonstrate this whole process: |
@gaksaray I see. My guess is that this has to do with how Stata's automation feature on Windows interacts with
For whatever reason Stata isn't registering |
Problem persists:
Kernel works fine. But this is expected. The problem seems to occur only when there are 3 or more adopaths in
Kernel works fine. I confirm that
Works fine. All three globals are defined properly within kernel.
I added
Again, no effect. Same problem:
It seems to be isolated to multiple adopath calls. |
Problem description
Kernel doesn't start when my
profile.do
contains more than one ado-path additions.For example, if my
profile.do
contains:everything works fine.
But, if my
profile.do
contains:I get the following:
and kernel keeps dying repeatedly;
Or, if I don't delete the contents of ~/.stata_kernel_cache before running jupyter, I get
.exit, clear
after I try to run a command in jupyter):So for some reason multiple ado-path additions causes the kernel to die before start.
Debugging log
console_debug.log
Other information
The text was updated successfully, but these errors were encountered: