CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead

[06parv]

CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead from cryptography.utils import int_from_bytes, int_to_bytes

from jose import jwt /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/jose/jwt.py:13: in from jose import jws /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/jose/jws.py:11: in from jose import jwk /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/jose/jwk.py:9: in from jose.backends.base import Key /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/jose/backends/init.py:3: in from jose.backends.cryptography_backend import CryptographyRSAKey as RSAKey # noqa: F401 /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/jose/backends/cryptography_backend.py:18: in from cryptography.utils import int_from_bytes, int_to_bytes /opt/hostedtoolcache/Python/3.8.7/x64/lib/python3.8/site-packages/cryptography/utils.py:104: in getattr warnings.warn(obj.message, obj.warning_class, stacklevel=2) E cryptography.utils.CryptographyDeprecationWarning: int_from_bytes is deprecated, use int.from_bytes instead

@mpdavis

[cahna]

Also seeing this. Our logging+alerting service caught a spike in python errors logged after latest deployment. Not a big deal to add an ignore rule, though.

[cahna]

This is a duplicate of #208