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

[BUG] runtime error: "ValueError: high is out of bounds for int32" #347

Open
rogerioxavier opened this issue Jun 19, 2023 · 1 comment
Open
Labels
bug Something isn't working

Comments

@rogerioxavier
Copy link

rogerioxavier commented Jun 19, 2023

Bug description

When training the all recommender systems models with NVIDIA Merlin at:
...
history = model.fit( train_data, epochs=3, batch_size=512, pre=predict_last )
...
runtime error: "ValueError: high is out of bounds for int32"

Steps/Code to reproduce bug

  1. I solved it like this:
    at file C:\Users\Xavier\AppData\Roaming\Python\Python310\site-packages\merlin\core\dispatch.py line 778
    from:
    seeds = random_state.randint(0, 2 ** 32, size=global_size)
    to:
    seeds = random_state.randint(0, 2 ** 32, size=global_size, dtype='int64') # include ", dtype='int64'"

Expected behavior

After the change in line 778 setting the type, all models trained normally.

Environment details

  • Merlin version: (23.5.0)
  • Platform: Windows, Lenovo GPU NVIDIA GeForce GTX 1650
  • Python version: 3.10.0
  • PyTorch version (GPU?):
  • Tensorflow version (GPU?): 2.10.0

Additional context

with pip install protobuf==3.20.0

@rogerioxavier rogerioxavier added the bug Something isn't working label Jun 19, 2023
@karlhigley karlhigley changed the title [BUG] [BUG] runtime error: "ValueError: high is out of bounds for int32" Jun 20, 2023
@karlhigley karlhigley transferred this issue from NVIDIA-Merlin/Merlin Jun 20, 2023
@karlhigley
Copy link
Contributor

@rogerioxavier It seems like you already have a solution for this issue, which sounds right to me. I'd be happy to review/merge a PR if you'd be willing to open one (so that you get credited as a contributor for the fix), or we can apply the fix ourselves if you'd rather we did it that way. Thoughts?

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

No branches or pull requests

2 participants