Local embedding failed with 2 different characters and 2 different twitter profiles while posting simultaneously

[0xbuild-oss]

Describe the bug

When a user has 2 different characters with 2 different twitter profiles they are unable to post simultaneously and receive the following errors:

You:  ["⚠ Local embedding not supported in browser, falling back to remote embedding"]

 ⚠ WARNINGS
   Local embedding failed, falling back to remote
   {}

 ⛔ ERRORS
   API Response:
   {"error":"Not Found"}

 ⛔ ERRORS
   Full error details:
   {}

 ⛔ ERRORS
   Error generating new tweet:
   {}
   

To Reproduce

The user has set the twitter secrets for each agent in their own character files, but is still getting the errors above when trying to run it.

Expected behavior

Should be able to post simultaneously from 2 different characters with 2 different Twitter profiles without receiving local embedding issues.

Additional context
@augchan42

[tcm390]

I just tested it with the latest main branch and couldn't reproduce the issue. May I ask which branch you're using?

[tamil2223]

i'm using latest main branch, below is the error i'm getting when i try with 1 or 2 different characters with 1 or 2 different twitter profiles they are unable to post simultaneously and receive.

[augchan42]

This is failing at chat completions step, not embeddings. Does your endpoint support that URL? I will take a look soon.

…

On Tue, Dec 17, 2024, 12:54 PM Tamilarasu Ravi ***@***.***> wrote: i'm using latest main branch, below is the error i'm getting when i try with 1 or 2 different characters with 1 or 2 different twitter profiles they are unable to post simultaneously and receive. Screenshot.2024-12-17.at.10.23.17.png (view on web) <https://github.com/user-attachments/assets/761f4dfc-27df-466e-b518-a7ca86259240> — Reply to this email directly, view it on GitHub <#1127 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AE32LKPJQAYURQUDGAOIJDD2F6VBLAVCNFSM6AAAAABTVE4BY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXGUYDKNBRGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[tamil2223]

yes, my endpoint supports the URL,

yesterday there was an issue with "anthropic" URL, but merging with latest main resolved that, but today there was an issue with "open ai" URL.

on logFetch function the URL path is always relative, if i make it as an absolute path, then i get an error like "missing x-api-key header" for open ai, which i have already placed it on .env file.

This is failing at chat completions step, not embeddings. Does your endpoint support that URL? I will take a look soon.
…
On Tue, Dec 17, 2024, 12:54 PM Tamilarasu Ravi @.> wrote: i'm using latest main branch, below is the error i'm getting when i try with 1 or 2 different characters with 1 or 2 different twitter profiles they are unable to post simultaneously and receive. Screenshot.2024-12-17.at.10.23.17.png (view on web) https://github.com/user-attachments/assets/761f4dfc-27df-466e-b518-a7ca86259240 — Reply to this email directly, view it on GitHub <#1127 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE32LKPJQAYURQUDGAOIJDD2F6VBLAVCNFSM6AAAAABTVE4BY2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBXGUYDKNBRGY . You are receiving this because you were mentioned.Message ID: @.>

[augchan42]

I'm able to run 1 or 2 twitter clients simultaneously. This trying from main branch. However, I run into another issue, which are double posts.

I launched two characters from agent dir like:

(.env) hosermage@LAPTOP-1RPE37PF:~/forked-projects/eliza/agent$ node --loader ts-node/esm src/index.ts "--isRoot" "--character=characters/yangzhongxiu.character.json,characters/pix.character.json"

These two character files are from the agent/characters folder

Each character file has twitter settings->secrets in the json

"settings": {
        "secrets": {
            "TWITTER_DRY_RUN": "false",
            "TWITTER_USERNAME": "",
            "TWITTER_PASSWORD": "",
            "TWITTER_EMAIL": "",
            "TWITTER_COOKIES": ""
        },
        "voice": {
            "model": "en_US-male-medium"
        }
    },

make sure you are using vpn if you are blocked from your LLM Provider