Closed yanggaome closed 1 month ago
Promptflow uploads your code snapshot to remote run, for flow.dag.yaml it's usually the dictory contains the flow.dag.yaml. For your case, could you share more on how do you specify the target flow? I guess somehow it treats the current working directory as the code snapshot root.
To add up to @wangchao1230 's comment, the reason we need to upload the whole working directory when flow runs in remote is because we need to make sure all current flow's dependency can be found in remote. Uploading working directory will make sure the flow runs in same environment between local & cloud. For example, if you used a customized evaluator, we need to upload the whole working directory to make sure the customized evaluator can be load successfully in remote. But if you only used built-in evaluators, I think some improvements can be done to skip uploading the whole working directory and only upload the flow YAML file. +@luigiw @singankit for comment here.
Hi, we're sending this friendly reminder because we haven't heard back from you in 30 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 7 days of this comment, the issue will be automatically closed. Thank you!
Describe the bug
I noticed while running promptflow evaluate API, it is trying to upload my entire working directory to remote, and below case it failed because there is a special file which is a soft link it cannot be uploaded. but this file is completely irrelevant to my evaluation run, it is just a file in my working directory.
This happens when I provide a target call as a separate python class
But when the target call just invokes a promptflow (dag yml), it seems not uploading the working directory
Questions: I can definitely remove this special file to make it work, but would like to understand why it needs to upload my entire working directory? how to prevent this?
How To Reproduce the bug Steps to reproduce the behavior, how frequent can you experience the bug: 1.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Running Information(please complete the following information):
pf -v
: [e.g. 0.0.102309906]python --version
: [e.g. python==3.10.12]{ "promptflow": "1.13.0", "promptflow-azure": "1.13.0", "promptflow-core": "1.13.0", "promptflow-devkit": "1.13.0", "promptflow-evals": "0.3.1", "promptflow-tracing": "1.13.0" }
Executable '/anaconda/envs/azureml_py38/bin/python' Python (Linux) 3.9.19 | packaged by conda-forge | (main, Mar 20 2024, 12:50:21) [GCC 12.3.0]
Additional context Add any other context about the problem here.