Skip to content

sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='nul' mode='w' encoding='cp932'> #1404

@AkiraRy

Description

@AkiraRy

TL;DR

I don't know if it is weaviate's fault but i figured out i should make an issue nevertheless. Simply running a file containing those 2 imports will reproduce this bug on my machine. Anywhere, doesn't even need to be in a project. I don't really know how can i trace the actual file which leaves an open connection. Any help will be greatly appreciated.
I'm not sure which library's fault this is but i submitted issues to llama-cpp-python and here.

How to reproduce this bag?

import llama_cpp as llm
import weaviate

What is the expected behavior?

Libraries simply load without any warnings.

What is the actual behavior?

When I load those 2 libraries together I get this warning
sys:1: ResourceWarning: unclosed file <_io.TextIOWrapper name='nul' mode='w' encoding='cp932'>

Supporting information

I use conda to manage libraries.
weaviate-client=4.9.3
llama-cpp-python=0.3.1
python=3.11.10

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions