Skip to content
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

import wpilib in repl kills interpreter #32

Open
TheTripleV opened this issue May 21, 2021 · 4 comments
Open

import wpilib in repl kills interpreter #32

TheTripleV opened this issue May 21, 2021 · 4 comments

Comments

@TheTripleV
Copy link
Member

Importing wpilib in a repl on the roborio causes the python interpreter to be killed.

@auscompgeek
Copy link
Member

Anything interesting in dmesg?

@TheTripleV
Copy link
Member Author

Nope. It only happens as lvuser. Doesn't happen as admin though.

In both cases, it does kill and restart the robot code under a new pid.

The behavior I expected was that the robot code would be killed and the repl would stay.

@auscompgeek
Copy link
Member

I think this is expected behaviour when you SSH in as lvuser. From what I've heard, the process that runs automatically as frcUserProgram has more privileges than a regular lvuser process (despite it also running as lvuser). Someone from the WPILib team could probably confirm.

@virtuald virtuald transferred this issue from robotpy/robotpy-wpilib Nov 13, 2023
@PeterJohnson
Copy link
Member

PeterJohnson commented Nov 16, 2023

We grant extra privileges to the java executable and deployed C++ user programs, but that's done as part of our deployment. Unless you're also granting the python executable extra privileges, python will simply run as a normal lvuser process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

3 participants