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

[cuebot] Cuebot unable to dispatch frames #1572

Closed
lithorus opened this issue Nov 5, 2024 · 7 comments · Fixed by #1573
Closed

[cuebot] Cuebot unable to dispatch frames #1572

lithorus opened this issue Nov 5, 2024 · 7 comments · Fixed by #1573
Labels
bug Something isn't working

Comments

@lithorus
Copy link
Contributor

lithorus commented Nov 5, 2024

Describe the bug
It seems like the recent changes broke job dispatching from cuebot

It errors out with :

2024-11-05 23:08:55.764  INFO 32971 --- [pool-1-thread-1] c.i.spcue.util.CueExceptionUtil          : Caught unexpected exception caused by: java.lang.NullPointerException
2024-11-05 23:08:55.764  INFO 32971 --- [pool-1-thread-1] c.i.spcue.util.CueExceptionUtil          : StackTrace: 
java.lang.NullPointerException
	at com.imageworks.spcue.dispatcher.commands.DispatchBookHost$1.wrapDispatchCommand(DispatchBookHost.java:90)
	at com.imageworks.spcue.dispatcher.commands.DispatchCommandTemplate.execute(DispatchCommandTemplate.java:36)
	at com.imageworks.spcue.dispatcher.commands.DispatchBookHost.run(DispatchBookHost.java:114)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)

To Reproduce
Steps to reproduce the behavior:

  1. Start cuebot
  2. Start rqd using the cuebot
  3. cuebot will spit out errors instead of running any frames

Expected behavior
That frames are dispatched by cuebot

Version Number
3341bcb

@lithorus lithorus added the bug Something isn't working label Nov 5, 2024
@DiegoTavares
Copy link
Collaborator

Please take a look at #1570 New opencue.properties are required now for dispatcher.memory attributes

@lithorus
Copy link
Contributor Author

lithorus commented Nov 5, 2024

But they are not part of the default config?

@DiegoTavares
Copy link
Collaborator

@lithorus
Copy link
Contributor Author

lithorus commented Nov 5, 2024

I'm also using the default config and I get the error as above. It's the master branch with no local changes.

@DiegoTavares
Copy link
Collaborator

Let me double check on my end

@DiegoTavares
Copy link
Collaborator

Ohh, it might be the autowiring that's causing a nullpointException. I've reverting the last commit to master

DiegoTavares added a commit to DiegoTavares/OpenCue that referenced this issue Nov 5, 2024
DiegoTavares added a commit to DiegoTavares/OpenCue that referenced this issue Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants