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

Epilogue "cannot be resolved or is not a field" #3

Closed
zeroClearAmerican opened this issue Oct 30, 2024 · 3 comments · May be fixed by #2
Closed

Epilogue "cannot be resolved or is not a field" #3

zeroClearAmerican opened this issue Oct 30, 2024 · 3 comments · May be fixed by #2

Comments

@zeroClearAmerican
Copy link
Member

zeroClearAmerican commented Oct 30, 2024

No build errors, proper usage of Epilogue annotation logging, but during simulation this error is encountered:

Error at frc.robot.RobotLogger.update(RobotLogger.java:29): Unhandled exception: java.lang.Error: Unresolved compilation problem: 
        containerLogger cannot be resolved or is not a field

        at frc.robot.RobotLogger.update(RobotLogger.java:29)
        at frc.robot.RobotLogger.update(RobotLogger.java:1)
        at edu.wpi.first.epilogue.logging.ClassSpecificLogger.tryUpdate(ClassSpecificLogger.java:64)
        at edu.wpi.first.epilogue.Epilogue.update(Epilogue.java:34)
        at edu.wpi.first.epilogue.Epilogue.lambda$0(Epilogue.java:55)
        at edu.wpi.first.wpilibj.TimedRobot.startCompetition(TimedRobot.java:146)
        at edu.wpi.first.wpilibj.RobotBase.runRobot(RobotBase.java:350)
        at edu.wpi.first.wpilibj.RobotBase.lambda$startRobot$0(RobotBase.java:418)
        at java.base/java.lang.Thread.run(Unknown Source)
@zeroClearAmerican
Copy link
Member Author

here is a screenshot of the auto-generated RobotLogger class encountering the issue:
image

@zeroClearAmerican
Copy link
Member Author

Opened issue in 2025Beta per official recommendation:
wpilibsuite/2025Beta#20

@zeroClearAmerican
Copy link
Member Author

Closing due to being a duplicate of wpilibsuite/allwpilib#7103 and having a workaround that allows simulation

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

Successfully merging a pull request may close this issue.

1 participant