You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Publisher log should show what versions of the interpreters were used to deploy a project to Connect. The request was to show all three interpreters and indicate if they were a dependency of the deployment as well as the versions being requested in the generated deployment manifest file.
The use case was for a project that had Quarto, R, and Python. Originally, it only had Quarto and R. As the user expanded it to also use Python, their deployments were not successful. In the end, the user saw no indication from the Publisher UX that Python was not configured as part of the project. They were also trying, ahead of adding Python to the project, to use a specific version of Python.
The user felt there should be better feedback and breadcrumbs around the experience to support self-diagnostics. They suggested that if the publisher log had included some indication of each interpreter's usage and version, then they would have been more self-sufficient in her ability to resolve her issue.
This issue becomes more needed when the versions are not auto-populated into the config file:
Captured from discussion w/ Katie...
The Publisher log should show what versions of the interpreters were used to deploy a project to Connect. The request was to show all three interpreters and indicate if they were a dependency of the deployment as well as the versions being requested in the generated deployment manifest file.
The use case was for a project that had Quarto, R, and Python. Originally, it only had Quarto and R. As the user expanded it to also use Python, their deployments were not successful. In the end, the user saw no indication from the Publisher UX that Python was not configured as part of the project. They were also trying, ahead of adding Python to the project, to use a specific version of Python.
The user felt there should be better feedback and breadcrumbs around the experience to support self-diagnostics. They suggested that if the publisher log had included some indication of each interpreter's usage and version, then they would have been more self-sufficient in her ability to resolve her issue.
This issue becomes more needed when the versions are not auto-populated into the config file:
The text was updated successfully, but these errors were encountered: