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

Torch new update breaks Stanza workflow #1524

Closed
KPCOFGS opened this issue Feb 6, 2025 · 1 comment
Closed

Torch new update breaks Stanza workflow #1524

KPCOFGS opened this issue Feb 6, 2025 · 1 comment

Comments

@KPCOFGS
Copy link

KPCOFGS commented Feb 6, 2025

Describe the bug
File "/home/user/.pyenv/versions/3.12.7/lib/python3.12/site-packages/torch/serialization.py", line 1494, in load
raise pickle.UnpicklingError(_get_wo_message(str(e))) from None
_pickle.UnpicklingError: Weights only load failed. This file can still be loaded, to do so you have two options, do those steps only if you trust the source of the checkpoint.
(1) In PyTorch 2.6, we changed the default value of the weights_only argument in torch.load from False to True. Re-running torch.load with weights_only set to False will likely succeed, but it can result in arbitrary code execution. Do it only if you got the file from a trusted source.
(2) Alternatively, to load with weights_only=True please check the recommended steps in the following error message.
WeightsUnpickler error: Unsupported global: GLOBAL numpy.core.multiarray._reconstruct was not an allowed global by default. Please use torch.serialization.add_safe_globals([_reconstruct]) or the torch.serialization.safe_globals([_reconstruct]) context manager to allowlist this global if you trust this class/function.

Check the documentation of torch.load to learn more about types accepted by default with weights_only https://pytorch.org/docs/stable/generated/torch.load.html.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Presidio model configuration workflow website
  2. Copy the workflow and run it

Expected behavior
Stanza should run properly without issue

@omri374
Copy link
Contributor

omri374 commented Feb 6, 2025

This is fixed in #1522 but not released yet. We will likely release a new version next week.

@KPCOFGS KPCOFGS closed this as completed Feb 6, 2025
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

2 participants