Skip to content

Warning RemovalΒ #15

@giovanni-vaccarino

Description

@giovanni-vaccarino

Description

Removing some warnings:

  • 1
   /opt/hostedtoolcache/Python/3.12.11/x64/lib/python3.12/site-packages/faiss/loader.py:49: DeprecationWarning: numpy.core._multiarray_umath is deprecated and has been renamed to numpy._core._multiarray_umath. The numpy._core namespace contains private NumPy internals and its use is discouraged, as NumPy internals can change without warning in any release. In practice, most real-world usage of numpy.core is to access functionality in the public NumPy API. If that is the case, use the public NumPy API. If not, you are using NumPy internals. If you would still like to access an internal attribute, use numpy._core._multiarray_umath.__cpu_features__.
    from numpy.core._multiarray_umath import __cpu_features__

  • 2
 <frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: builtin type SwigPyPacked has no __module__ attribute

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: builtin type SwigPyObject has no __module__ attribute

<frozen importlib._bootstrap>:488
  <frozen importlib._bootstrap>:488: DeprecationWarning: builtin type swigvarlink has no __module__ attribute

  • 3
tests/unit/chunking/test_common.py::test_save_chunks_handles_error
  /home/runner/work/resources-ai-chatbot-plugin/resources-ai-chatbot-plugin/chatbot-core/tests/unit/chunking/test_common.py:38: PytestMockWarning: Mocks returned by pytest-mock do not need to be used as context managers. The mocker fixture automatically undoes mocking at the end of a test. This warning can be ignored if it was triggered by mocking a context manager. https://pytest-mock.readthedocs.io/en/latest/usage.html#usage-as-context-manager
    with mocker.patch("builtins.open", side_effect=raise_oserror):

  • 4

There is a deprecation warning related to ConversationBufferMemory usage in LangChain:

# LangChainDeprecationWarning on 
memory = ConversationBufferMemory(return_messages=True)

To fix this, please refer to the migration guide:
https://python.langchain.com/docs/versions/migrating_memory/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions