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

Top Fetch misbehaviour when using afanasy scheduler #598

Open
nuclearpolygon opened this issue Apr 5, 2024 · 0 comments
Open

Top Fetch misbehaviour when using afanasy scheduler #598

nuclearpolygon opened this issue Apr 5, 2024 · 0 comments

Comments

@nuclearpolygon
Copy link

nuclearpolygon commented Apr 5, 2024

issue

top fetch does not report work items back

expected behaviour

When the remote TOP network is cooked, the work items on the output node of that network are saved to disk and reported back to PDG. Then these items are re-created in the TOP Fetch node. The items visible on the TOP Fetch node are those re-created items.

actual behaviour

When the remote TOP network is cooked cooking process stops and no work items appears in top fetch

steps to reproduce

  1. create topnet1 and place generic generator into it, make afanasy scheduler the default one for the network
  2. create topnet2 and place topfetch then point it to topnet1/genericgenerator1, make afanasy scheduler the default one for the network
  3. cook topnet2

cgru: 3.3.1
Houdini: 20.0.590

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

No branches or pull requests

1 participant