Skip to content
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

Cannot view conversation messages when index is 1 (the only conversation available) #452

Closed
1 task
buzby08 opened this issue Nov 10, 2024 · 1 comment · Fixed by pieces-app/cli-agent#216
Assignees

Comments

@buzby08
Copy link

buzby08 commented Nov 10, 2024

Software

Pieces CLI

Operating System / Platform

Windows

Your Pieces OS Version

10.1.12

Early Access Program

  • Yes, this is related to an Early Access Program feature.

Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.

I have one conversation in pieces. I can see this conversation in the Pieces for Developers app. In the CLI, i list all the conversations. It shows one conversation, named JARVIS, written as 1. JARVIS. I would assume that this means the index of the chat is 1. If i try the command pieces conversation 1 to view the conversation messages, i get a python error saying list index out of range. As a python programmer, i looked at the code, and then tried to run the command pieces conversation 0, in case the index is not shown correctly. This raises a pieces error saying the conversation is empty. The conversation has one message from me, and one response from the LLM. This has been confirmed from Pieces for developers app. I have provided pictures to aid.

image
image

@bishoy-at-pieces
Copy link
Contributor

Hello @buzby08 ,
Thank you for bringing this to our attention. It should be resolved in the latest version. You can upgrade to the latest version by running the following command:

pip install pieces-cli --upgrade

Make sure you are on version 1.8.2

pieces -v

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants