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

Unexpected JSON Metadata in Twitter Bot Replies #2423

Closed
jeongtai opened this issue Jan 17, 2025 · 13 comments
Closed

Unexpected JSON Metadata in Twitter Bot Replies #2423

jeongtai opened this issue Jan 17, 2025 · 13 comments
Labels

Comments

@jeongtai
Copy link

Describe the bug

The Eliza OS Twitter bot is responding with additional metadata in the tweet replies, instead of just the intended message text.

To Reproduce

  1. Set up and run the Eliza OS Twitter bot
  2. Trigger a response from the bot
  3. Observe the bot's reply tweet

Expected behavior

The bot should reply with only the intended message text, e.g.:
"Agreed, decentralized information dissemination is crucial for a free society."

Screenshots

Image

Additional context

{```

"user": "LumixAgent",
"text": "Agreed, decentralized information dissemination is crucial for a free society."
}

@jeongtai jeongtai added the bug Something isn't working label Jan 17, 2025
@sharif331
Copy link

I am also seeing this most of the times.

Image

@tcm390
Copy link
Collaborator

tcm390 commented Jan 22, 2025

what modelProvider are you using?

@sharif331
Copy link

I am using GROQ, My observation is when we launch the agent initially then I see this type of issue later after 1-2 days it is mostly stable and another case I'm assuming when the action processing is very fast and the agent needs to respond to many tweets.

@tcm390
Copy link
Collaborator

tcm390 commented Jan 22, 2025

hi @sharif331 @jeongtai

Could you provide the log? I'm trying to reproduce the issue in the parseJSONObjectFromText function but can't seem to output the same result. It should always return null with the wrong formatting, so I'm not sure why it's still processing it. 🤔

@AIFlowML
Copy link
Collaborator

@sharif331 @jeongtai as requested by @tcm390 please pass the logs.
You mention it start after few days. But is it a constant error or it do only in certain cases ?

tnks

@sharif331
Copy link

sharif331 commented Jan 23, 2025

Image Image

@AIFlowML @tcm390
This is not constantly happening but this happens randomly.

@tcm390
Copy link
Collaborator

tcm390 commented Jan 23, 2025

Image Image
@AIFlowML @tcm390 This is not constantly happening but this happens randomly.

This is so helpful! Thanks, I will make a PR to fix it.

@tcm390
Copy link
Collaborator

tcm390 commented Jan 23, 2025

@sharif331 #2712 this should fix the issue, pls let me know if it works

@jeongtai
Copy link
Author

what modelProvider are you using?

I'm using openrouter model.

#.env
OPENROUTER_MODEL=deepseek/deepseek-chat
SMALL_OPENROUTER_MODEL=nousresearch/hermes-3-llama-3.1-70b
MEDIUM_OPENROUTER_MODEL=anthropic/claude-3.5-sonnet:beta
LARGE_OPENROUTER_MODEL=anthropic/claude-3.5-sonnet:beta

@tcm390
Copy link
Collaborator

tcm390 commented Jan 24, 2025

what modelProvider are you using?

I'm using openrouter model.

#.env OPENROUTER_MODEL=deepseek/deepseek-chat SMALL_OPENROUTER_MODEL=nousresearch/hermes-3-llama-3.1-70b MEDIUM_OPENROUTER_MODEL=anthropic/claude-3.5-sonnet:beta LARGE_OPENROUTER_MODEL=anthropic/claude-3.5-sonnet:beta

Could you check the latest develop branch? The fix has been merged pls lmk if it fixes the issue

@jeongtai
Copy link
Author

Is that your fix thing? (#2423 (comment))

@tcm390
Copy link
Collaborator

tcm390 commented Jan 24, 2025

Is that your fix thing? (#2423 (comment))

yea, #2712 , #2730 should fix the issue. They have been merged into the develop branch

@tcm390
Copy link
Collaborator

tcm390 commented Jan 28, 2025

It seems there hasn't been any feedback or updates on this issue for quite some time. I'll go ahead and close this issue for now.
If the issue arises again or there's more information to share, please feel free to reopen it or create a new issue. @jeongtai @sharif331

@tcm390 tcm390 closed this as completed Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants