search

TransformerOptimus / SuperAGI

<⚡️> SuperAGI - A dev-first open source autonomous AI agent framework. Enabling developers to build, manage & run useful autonomous agents quickly and reliably.
https://superagi.com/
MIT License
15.55k stars 1.87k forks source link

Agent can think once but not twice. #205

Closed roberthartmann closed 1 year ago

roberthartmann commented 1 year ago

Hi,

I need your help. I've been reading the topics #165 #184 #160 #192 and #200 but I still seem to be to blind to find the mistake.

My agent manages to define the tasks, write down what time it is and then starts thinking.

The 172.18.0.1 is hammered, and nothing happens.

Sure enough I looked at the PineCone Environment and API Key in the config.yaml they are correct.

The entry point.sh and wait-for-it.sh are set to LF since I run it in Win 10 with Docker

The agent_executor.py in the SuperAPI/Jobs sub folder shows try: if parsed_config["LTM_DB"] == "Pinecone": memory = VectorFactory.get_vector_storage("PineCone", "super-agent-index1", OpenAiEmbedding()) else: memory = VectorFactory.get_vector_storage("PineCone", "super-agent-index1", OpenAiEmbedding()) except: print("Unable to setup the pincone connection...") memory = None

        user_tools = session.query(Tool).filter(Tool.id.in_(parsed_config["tools"])).all()

As it is supposed to be with the free version of PineCone.

The ChatGPT ist 3.5 Turbo sice I don't have the Version 4.

So the only question that remains is: what did I not see? There is something mentioned about the test.py but I really don't get it. I even changed the "LTM_DB: To "super-agent-index1"

image

I really hope someone can help me.

luciferlinx101 commented 1 year ago

Hey @roberthartmann can you elaborate the issue? Also before that can you try docker compose up --build and check for logs and wait a little more and check if you just see thinking yet, also I would like to know all agent details which you used like goals, name, description, and other agent configurations so that we can reproduce the same.

luciferlinx101 commented 1 year ago

Also, do try checking out the updated readme if it helps.

CodeManMike commented 1 year ago

Hey dude, what I did is to go to pinecone and create my own custom index of dimensions 10000 and then past that in the agent executor. Just give it your own name and replace both reference in the python file

roberthartmann commented 1 year ago

Hi,

I composed it (yet again)... nothing changed ...

here are the logs of it. there is something about the next.config.js which I don't understand. I will post it after the logs of the compose up

C:\Users\Robert\Desktop\SuperAGI> docker compose up --build [+] Building 1.7s (32/32) FINISHED => [celery internal] load build definition from DockerfileCelery 0.1s => => transferring dockerfile: 259B 0.0s => [celery internal] load .dockerignore 0.1s => => transferring context: 51B 0.0s => [backend internal] load .dockerignore 0.1s => => transferring context: 51B 0.0s => [backend internal] load build definition from Dockerfile 0.1s => => transferring dockerfile: 387B 0.0s => [gui internal] load build definition from Dockerfile 0.1s => => transferring dockerfile: 149B 0.0s => [gui internal] load .dockerignore 0.1s => => transferring context: 2B 0.0s => [celery internal] load metadata for docker.io/library/python:3.9 0.9s => [gui internal] load metadata for docker.io/library/node:lts 0.8s => [backend 1/6] FROM docker.io/library/python:3.9@sha256:603ac689b89c2a59791a4e7cd3d727f2a673ac3df02dabbd97b0d85bb1eca4e7 0.0s => [celery internal] load build context 0.2s => => transferring context: 17.08kB 0.2s => [backend internal] load build context 0.2s => => transferring context: 17.08kB 0.1s => [gui 1/5] FROM docker.io/library/node:lts@sha256:8cdf7234449f35e579f7491137807ddb3a089f028862f7ab69af437cc9f47ff1 0.0s => [gui internal] load build context 0.1s => => transferring context: 4.48kB 0.0s => CACHED [gui 2/5] WORKDIR /app 0.0s => CACHED [gui 3/5] COPY package.json ./ 0.0s => CACHED [gui 4/5] RUN npm install 0.0s => CACHED [gui 5/5] COPY . . 0.0s => [gui] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:0928b2b45009d3c7eb608202aa3b3c35ff83162c4d22c662ad9e60822a0a9a8c 0.0s => => naming to docker.io/library/superagi-gui 0.0s => CACHED [backend 2/6] WORKDIR /app 0.0s => CACHED [celery 3/6] COPY requirements.txt . 0.0s => CACHED [celery 4/6] RUN pip install --no-cache-dir -r requirements.txt 0.0s => CACHED [celery 5/6] COPY . . 0.0s => CACHED [celery 6/6] COPY config.yaml . 0.0s => [celery] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:05d5009b0eec9b3715e04dad10512d34dbd91d836a3d580513b35c8159d6be3e 0.0s => => naming to docker.io/library/superagi-celery 0.0s => CACHED [backend 3/9] COPY requirements.txt . 0.0s => CACHED [backend 4/9] RUN pip install --no-cache-dir -r requirements.txt 0.0s => CACHED [backend 5/9] COPY . . 0.0s => CACHED [backend 6/9] COPY config.yaml ./config.yaml 0.0s => CACHED [backend 7/9] COPY entrypoint.sh /entrypoint.sh 0.0s => CACHED [backend 8/9] COPY wait-for-it.sh /wait-for-it.sh 0.0s => CACHED [backend 9/9] RUN chmod +x /entrypoint.sh /wait-for-it.sh 0.0s => [backend] exporting to image 0.0s => => exporting layers 0.0s => => writing image sha256:296f676621b716bc8d6a15b3f746056419638cd4505194e0d2ede498c377fa63 0.0s => => naming to docker.io/library/superagi-backend 0.0s [+] Running 5/0 ✔ Container superagi-superpostgres-1 Created 0.0s ✔ Container superagi-superredis-1 Created 0.0s ✔ Container superagi-gui-1 Created 0.0s ✔ Container superagi-celery-1 Created 0.0s ✔ Container superagi-backend-1 Created 0.0s Attaching to superagi-backend-1, superagi-celery-1, superagi-gui-1, superagi-superpostgres-1, superagi-superredis-1 superagi-superpostgres-1 | superagi-superpostgres-1 | PostgreSQL Database directory appears to contain a database; Skipping initialization superagi-superpostgres-1 | superagi-superpostgres-1 | 2023-06-06 19:37:54.776 UTC [1] LOG: starting PostgreSQL 15.3 (Debian 15.3-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit superagi-superpostgres-1 | 2023-06-06 19:37:54.799 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 superagi-superpostgres-1 | 2023-06-06 19:37:54.799 UTC [1] LOG: listening on IPv6 address "::", port 5432 superagi-superredis-1 | 1:C 06 Jun 2023 19:37:54.816 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo superagi-superredis-1 | 1:C 06 Jun 2023 19:37:54.816 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=1, just started superagi-superredis-1 | 1:C 06 Jun 2023 19:37:54.816 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.816 monotonic clock: POSIX clock_gettime superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.817 * Running mode=standalone, port=6379. superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.817 # Server initialized superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.817 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.818 Loading RDB produced by version 7.0.11 superagi-super__redis-1 | 1:M 06 Jun 2023 19:37:54.818 RDB age 9 seconds superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.818 * RDB memory usage when created 1.18 Mb superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.818 Done loading RDB, keys loaded: 11, keys expired: 0. superagi-super__redis-1 | 1:M 06 Jun 2023 19:37:54.818 DB loaded from disk: 0.000 seconds superagi-superredis-1 | 1:M 06 Jun 2023 19:37:54.818 * Ready to accept connections superagi-superpostgres-1 | 2023-06-06 19:37:54.852 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" superagi-superpostgres-1 | 2023-06-06 19:37:54.912 UTC [29] LOG: database system was shut down at 2023-06-06 19:37:45 UTC superagi-superpostgres-1 | 2023-06-06 19:37:54.935 UTC [1] LOG: database system is ready to accept connections superagi-backend-1 | wait-for-it.sh: waiting 60 seconds for superpostgres:5432 superagi-backend-1 | wait-for-it.sh: superpostgres:5432 is available after 0 seconds superagi-gui-1 | superagi-gui-1 | > super-agi@0.1.0 dev superagi-gui-1 | > next dev superagi-gui-1 | superagi-gui-1 | - ready started server on 0.0.0.0:3000, url: http://localhost:3000 superagi-gui-1 | - warn Invalid next.config.js options detected: superagi-gui-1 | - warn The root value has an unexpected property, webpackDevMiddleware, which is not in the list of allowed properties (amp, analyticsId, assetPrefix, basePath, cleanDistDir, compiler, compress, configOrigin, crossOrigin, devIndicators, distDir, env, eslint, excludeDefaultMomentLocales, experimental, exportPathMap, generateBuildId, generateEtags, headers, httpAgentOptions, i18n, images, modularizeImports, onDemandEntries, optimizeFonts, output, outputFileTracing, pageExtensions, poweredByHeader, productionBrowserSourceMaps, publicRuntimeConfig, reactStrictMode, redirects, rewrites, sassOptions, serverRuntimeConfig, skipMiddlewareUrlNormalize, skipTrailingSlashRedirect, staticPageGenerationTimeout, swcMinify, target, trailingSlash, transpilePackages, typescript, useFileSystemPublicRoutes, webpack). superagi-gui-1 | - warn See more info here: https://nextjs.org/docs/messages/invalid-next-config superagi-backend-1 | INFO [alembic.runtime.migration] Context impl PostgresqlImpl. superagi-backend-1 | INFO [alembic.runtime.migration] Will assume transactional DDL. superagi-backend-1 | INFO: Will watch for changes in these directories: ['/app'] superagi-backend-1 | INFO: Uvicorn running on http://0.0.0.0:8001 (Press CTRL+C to quit) superagi-backend-1 | INFO: Started reloader process [1] using WatchFiles superagi-celery-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-celery-1 | /usr/local/lib/python3.9/site-packages/celery/platforms.py:840: SecurityWarning: You're running the worker with superuser privileges: this is superagi-celery-1 | absolutely not recommended! superagi-celery-1 | superagi-celery-1 | Please specify a different user using the --uid option. superagi-celery-1 | superagi-celery-1 | User information: uid=0 euid=0 gid=0 egid=0 superagi-celery-1 | superagi-celery-1 | warnings.warn(SecurityWarning(ROOT_DISCOURAGED.format( superagi-celery-1 |
superagi-celery-1 | -------------- celery@09da00a5279f v5.2.7 (dawn-chorus) superagi-celery-1 | --- * ----- superagi-celery-1 | -- *** ---- Linux-5.15.90.1-microsoft-standard-WSL2-x86_64-with-glibc2.31 2023-06-06 19:38:06 superagi-celery-1 | - --- --- superagi-celery-1 | - ---------- [config] superagi-celery-1 | - ---------- .> app: superagi:0x7f95c5f76eb0 superagi-celery-1 | - ---------- .> transport: redis://superredis:6379/0 superagi-celery-1 | - ---------- .> results: redis://super__redis:6379/0 superagi-celery-1 | - --- --- .> concurrency: 10 (prefork) superagi-celery-1 | -- *** ---- .> task events: OFF (enable -E to monitor tasks in this worker) superagi-celery-1 | --- * ----- superagi-celery-1 | -------------- [queues] superagi-celery-1 | .> celery exchange=celery(direct) key=celery superagi-celery-1 | superagi-celery-1 | superagi-celery-1 | [tasks] superagi-celery-1 | . execute_agent superagi-celery-1 | superagi-backend-1 | Connected to the database! @ postgresql://superagi:password@superpostgres/super_agi_main superagi-celery-1 | [2023-06-06 19:38:08,378: INFO/MainProcess] Connected to redis://superredis:6379/0 superagi-celery-1 | [2023-06-06 19:38:08,398: INFO/MainProcess] mingle: searching for neighbors superagi-celery-1 | [2023-06-06 19:38:09,427: INFO/MainProcess] mingle: all alone superagi-celery-1 | [2023-06-06 19:38:09,481: INFO/MainProcess] celery@09da00a5279f ready. superagi-gui-1 | - event compiled client and server successfully in 8.5s (775 modules) superagi-gui-1 | - wait compiling... superagi-gui-1 | - event compiled client and server successfully in 4.1s (775 modules) superagi-backend-1 | INFO: Started server process [20] superagi-backend-1 | INFO: Waiting for application startup. superagi-backend-1 | INFO: Application startup complete.

next.config.js

/* @type {import('next').NextConfig} / const nextConfig = { assetPrefix: process.env.NODE_ENV === "production" ? "/" : "./", webpackDevMiddleware: config => { config.watchOptions = { poll: 1000, aggregateTimeout: 300, } return config } }

module.exports = nextConfig

there is another interesting message:

superagi-gui-1 | - wait compiling /_error (client and server)... superagi-gui-1 | - event compiled client and server successfully in 1198 ms (776 modules) superagi-gui-1 | Do not add stylesheets using next/head (see tag with href="https://fonts.googleapis.com/css2?family=Inter:wght@300;400;500;600;700&display=swap"). Use Document instead. superagi-gui-1 | See more info here: https://nextjs.org/docs/messages/no-stylesheets-in-head-component superagi-backend-1 | INFO: 172.18.0.1:55880 - "GET /agents/get/project/ HTTP/1.1" 307 Temporary Redirect superagi-backend-1 | INFO: 172.18.0.1:55916 - "OPTIONS /users/add HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:55902 - "GET /tools/get HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:55894 - "GET /organisations/get/1 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:55880 - "POST /users/add HTTP/1.1" 201 Created superagi-backend-1 | INFO: 172.18.0.1:55924 - "GET /projects/get/organisation/1 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:55932 - "GET /agents/get/project HTTP/1.1" 422 Unprocessable Entity superagi-backend-1 | INFO: 172.18.0.1:55932 - "GET /tools/get HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:55924 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:56596 - "OPTIONS /agents/create HTTP/1.1" 200 OK superagi-celery-1 | [2023-06-06 19:41:06,927: INFO/MainProcess] Task execute_agent[91259a5a-b0e2-412f-9f4b-172a9cb94152] received superagi-backend-1 | INFO: 172.18.0.1:56596 - "POST /agents/create HTTP/1.1" 201 Created superagi-celery-1 | [2023-06-06 19:41:06,930: WARNING/ForkPoolWorker-7] Execute agent:2023-06-06T19:41:06.767925,9 superagi-backend-1 | INFO: 172.18.0.1:56596 - "GET /agents/get/project/1 HTTP/1.1" 200 OK superagi-celery-1 | [2023-06-06 19:41:07,028: WARNING/ForkPoolWorker-7] Agent Under Execution : superagi-celery-1 | [2023-06-06 19:41:07,028: WARNING/ForkPoolWorker-7] Agent(id=6, name='say hi 2', project_id=1, description='say hi') superagi-backend-1 | INFO: 172.18.0.1:56610 - "GET /agentexecutions/get/agent/6 HTTP/1.1" 200 OK superagi-celery-1 | [2023-06-06 19:41:07,029: WARNING/ForkPoolWorker-7] Agent Execution : superagi-celery-1 | [2023-06-06 19:41:07,029: WARNING/ForkPoolWorker-7] AgentExecution(id=9, name=New Run,status='RUNNING', last_execution_time='2023-06-06 19:41:06.573139', agent_id=6) superagi-celery-1 | [2023-06-06 19:41:07,047: WARNING/ForkPoolWorker-7] Configuration superagi-backend-1 | INFO: 172.18.0.1:56596 - "GET /agents/get/details/6 HTTP/1.1" 200 OK superagi-celery-1 | [2023-06-06 19:41:07,047: WARNING/ForkPoolWorker-7] superagi-backend-1 | INFO: 172.18.0.1:56610 - "GET /agentexecutionfeeds/get/execution/0 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:56596 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-celery-1 | [2023-06-06 19:41:07,048: WARNING/ForkPoolWorker-7] [AgentConfiguration(id=51, key=goal, value=['say hi']), AgentConfiguration(id=52, key=agent_type, value=Don't Maintain Task Queue), AgentConfiguration(id=53, key=constraints, value=['~4000 word limit for short term memory. Your short term memory is short, so immediately save important information to files.', 'If you are unsure how you previously did something or want to recall past events, thinking about similar events will help you remember.', 'No user assistance', 'Ensure the command and args are as per current plan and reasoning', 'Exclusively use the commands listed in double quotes e.g. "command name"']), AgentConfiguration(id=54, key=tools, value=[7, 8, 9]), AgentConfiguration(id=55, key=exit, value=No exit criterion), AgentConfiguration(id=56, key=iteration_interval, value=500), AgentConfiguration(id=57, key=model, value=gpt-3.5-turbo), AgentConfiguration(id=58, key=permission_type, value=God Mode), AgentConfiguration(id=59, key=LTM_DB, value=Pinecone), AgentConfiguration(id=60, key=memory_window, value=10)] superagi-celery-1 | [2023-06-06 19:41:11,561: INFO/ForkPoolWorker-7] error_code=None error_message='You exceeded your current quota, please check your plan and billing details.' error_param=None error_type=insufficient_quota message='OpenAI API error received' stream_error=False superagi-celery-1 | [2023-06-06 19:41:11,562: WARNING/ForkPoolWorker-7] Exception: superagi-celery-1 | [2023-06-06 19:41:11,562: WARNING/ForkPoolWorker-7] superagi-celery-1 | [2023-06-06 19:41:11,562: WARNING/ForkPoolWorker-7] You exceeded your current quota, please check your plan and billing details.
superagi-celery-1 | [2023-06-06 19:41:11,562: WARNING/ForkPoolWorker-7] Exception Occured in celery job superagi-celery-1 | [2023-06-06 19:41:11,563: WARNING/ForkPoolWorker-7] 'content' superagi-celery-1 | [2023-06-06 19:41:11,568: INFO/ForkPoolWorker-7] Task execute_agent[91259a5a-b0e2-412f-9f4b-172a9cb94152] succeeded in 4.638191753001593s: None superagi-backend-1 | INFO: 172.18.0.1:44422 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:53286 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:54416 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:48278 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:45082 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:40882 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:40828 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:60690 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-superpostgres-1 | 2023-06-06 19:42:55.000 UTC [27] LOG: checkpoint starting: time superagi-superpostgres-1 | 2023-06-06 19:42:57.118 UTC [27] LOG: checkpoint complete: wrote 23 buffers (0.1%); 0 WAL file(s) added, 0 removed, 0 recycled; write=2.038 s, sync=0.035 s, total=2.119 s; sync files=20, longest=0.016 s, average=0.002 s; distance=51 kB, estimate=51 kB superagi-backend-1 | INFO: 172.18.0.1:55216 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:47188 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:49066 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:38360 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:38372 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:49870 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:34612 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:41870 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:53472 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:49090 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:47660 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:48398 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK superagi-backend-1 | INFO: 172.18.0.1:45594 - "GET /agentexecutionfeeds/get/execution/9 HTTP/1.1" 200 OK

roberthartmann commented 1 year ago

@CodeManMike how can i rename the pinecone index name while having a free account?

if i knew that having subscription would solve the problem i'd be in for that

roberthartmann commented 1 year ago

@luciferlinx101 the agent was named "say hi" the comment was "say hi" and the task was "say "hi"" all settings were standard, out of the box presets

CodeManMike commented 1 year ago

@CodeManMike how can i rename the pinecone index name while having a free account?

if i knew that having subscription would solve the problem i'd be in for that

Hey mate, so don't rename the index, delete any index that you might have on pincone. I had one from autogpt, and then create a new index

neelayan7 commented 1 year ago

@roberthartmann is this issue still persisting?