-
Notifications
You must be signed in to change notification settings - Fork 724
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Serving UI doesn't return flow result #3279
Comments
Hi @RenatoSGR, thanks for reaching us, could you please provide the promptflow version you are using? We tried with latest promptflow package seems it works well. |
Hi @brynn-code this is my versions: pf --version Some colleagues also facing the same issue when inside of a container. It anwser on the logs, but not on the frontend like yours. That behavior that you're showing, I can replicate but running locally without a container. The Dockerfile generated by promptflow extension:FROM docker.io/continuumio/miniconda3:latest WORKDIR / COPY ./flow/requirements.txt /flow/requirements.txt RUN apt-get update && apt-get install -y runit gcc RUN conda create -n promptflow-serve python=3.9.16 pip=23.0.1 -q -y && COPY ./flow /flow EXPOSE 8080 COPY ./connections/* /connections/ RUN rm -rf /var/runit RUN chmod -R +x /var/runit |
Got it, so the point is container, we will try to repro it. |
Update: we have reproduced the bug, investigating., |
Thanks, keep in mind my first comment where I provide the working index.js and index.html (from a previous commit, with less features like + new chat on the left pane) |
@RenatoSGR Hi, we are fixing this issue, but we find a workaround for this issue, maybe you could have a try to see if this can unblock you:
|
Hi @brynn-code it works like you said. For now this will unblock me for sure. Thanks |
…work (#3333) # Description Please add an informative description that covers that changes made by the pull request and link all relevant issues. Reason: Flow name was calculated with relative path which could be empty string in the build scenario and then caused chat UI can't show the result. Related: #3279 Should be included in promptflow 1.12.0 # All Promptflow Contribution checklist: - [ ] **The pull request does not introduce [breaking changes].** - [ ] **CHANGELOG is updated for new features, bug fixes or other significant changes.** - [ ] **I have read the [contribution guidelines](../CONTRIBUTING.md).** - [ ] **Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: [suggested workflow](../CONTRIBUTING.md#suggested-workflow).** ## General Guidelines and Best Practices - [ ] Title of the pull request is clear and informative. - [ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, [see this page](https://github.com/Azure/azure-powershell/blob/master/documentation/development-docs/cleaning-up-commits.md). ### Testing Guidelines - [ ] Pull request includes test coverage for the included changes. --------- Signed-off-by: Brynn Yin <biyi@microsoft.com>
Hi, the fix of this bug has been merged, it will be included in the promptflow 1.12.0. |
Describe the bug
When running a docker container with the current version of promptflow, the flow is running well, but the frontend app created by the promptflow not showing any answer. The docker container logs are showing the correct flow and answer, but not the frontend.
I needed to use this commit version of promptflow for indez.js and index.html to see everything working properly:
How To Reproduce the bug
Steps to reproduce the behavior, how frequent can you experience the bug:
Expected behavior
Frontend app working properly and showing the question and answer of the promptflow
Screenshots
Additional context
As I said, if I run the old version of index.js and index.html, it works smoothly without this issue.
The text was updated successfully, but these errors were encountered: