On newer releases since the most recent AdvantageKit Alpha release, the thread that captures console data isn't getting any console data. I suspect it is because AdvantageKit uses a journalctl command to monitor data:
journalctl -f -u robot.service -n all -o cat _SYSTEMD_INVOCATION_ID=$(systemctl show -p InvocationID --value robot.service)
However the user of the robot service has since changed from "root" to "systemcore", meaning there are not sufficient permissions to get the journal, and nothing is printed to stdout, only a stderr message stating that there are insufficient permissions, meaning that the thread starts properly, but never actually returns any console information to the Logger.
A clean solution could be to add the systemcore user to the "systemd-journal" group, or as an AdvantageKit-side workaround, using sudo.
Apologies if this is the wrong place to post this, it just felt appropriate as it was more closely coupled with the development of Systemcore than other AdvantageKit issues.
On newer releases since the most recent AdvantageKit Alpha release, the thread that captures console data isn't getting any console data. I suspect it is because AdvantageKit uses a journalctl command to monitor data:
journalctl -f -u robot.service -n all -o cat _SYSTEMD_INVOCATION_ID=$(systemctl show -p InvocationID --value robot.service)However the user of the robot service has since changed from "root" to "systemcore", meaning there are not sufficient permissions to get the journal, and nothing is printed to stdout, only a stderr message stating that there are insufficient permissions, meaning that the thread starts properly, but never actually returns any console information to the Logger.
A clean solution could be to add the systemcore user to the "systemd-journal" group, or as an AdvantageKit-side workaround, using sudo.
Apologies if this is the wrong place to post this, it just felt appropriate as it was more closely coupled with the development of Systemcore than other AdvantageKit issues.