Closed jackson-theisen closed 3 months ago
Thanks for the report, it sounds as if it's getting in some sort of recursive loop which doesn't sound right. Unfortunately DFS resolution is a very tricky thing to work with. The best thing you can do is try to share as much details about the environment that you can. Things like
I do understand that the trace log can expose environment details so it may not be possible to share but sharing as much information as you can is ideal for me to try and figure out what might be going wrong here.
@jborean93 I ultimately pivoted to a different approach and have since torn down the infrastructure that would allow me to capture the information you've requested. I greatly appreciate your willingness to help and apologize I wasn't able to dig deeper on this issue. Will close this out
No worries, I appreciate you opening the bug report and sharing as much info as you could before. If you ever come across this again we can certainly try to revisit it!
I am attempting to write files to a DFS server share that has hundreds of directories. It appears that regardless of the
path
passed in tosmbclient.open_file()
, it will attempt to read the entire file tree viaget_smb_tree()
. In my case, this results in[ERROR] RecursionError: maximum recursion depth exceeded while calling a Python object
.My hacky attempt at fixing the issue was to increase the recursion depth limit via
sys.setrecursionlimit()
, which ultimately failed and is not ideal regardless of whether it works.Here is the relevant code snippet i'm using:
and here is the full stack trace:
This is not necessarily a bug, but rather a request for guidance on any potential misconfigurations or solutions to get around the issue. Thanks!