pinecone-io / chatbot-demo Goto Github PK

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When running the app, Pinecone runs first (and works) but then this error appears in terminal:

06:53:33.619 Ably: Auth.requestToken(): token request signing call returned error; err = [ErrorInfo: Error response received from server: 404 body was: <Buffer 3c 21 44 4f 43 54 59 50 45 20 68 74 6d 6c 3e 3c 68 74 6d 6c 20 6c 61 6e 67 3d 22 65 6e 22 3e 3c 68 65 61 64 3e 3c 73 74 79 6c 65 20 64 61 74 61 2d 6e ... 2520 more bytes>] {
  code: NaN,
  statusCode: 404,
  cause: undefined
}

Expected Behavior

Connect to Ably, I guess?

Steps To Reproduce

1. Create .env file and fill in all missing keys
2. Launch the application with npm run dev

Relevant log output

No response

Environment

- MacOS
- Python 3.11.1

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Web browser console output:

Failed to fetch visitor data on mount: FPJSAgentError: Failed to load the JS script of the agent 2 next-dev.js:20:25
visitorData?.visitorId! undefined

Expected Behavior

expected to show visitor id as not undefined

Steps To Reproduce

1. npm run dev
2. create .env
3. fix the import error in chat.tsx './embedded' to './matches'
4. then we get errors and don't recieve any messages back after we talk to pinecone gpt

Relevant log output

Web browser console output:

`Failed to fetch visitor data on mount: FPJSAgentError: Failed to load the JS script of the agent 2 next-dev.js:20:25`
`visitorData?.visitorId! undefined `

Environment

- **OS**: MacOS Firefox
- **Language version**: latest
- **Pinecone client version**: latest

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

I have launched the application with everything needed. I have created conversation in cockroachdb and when I launch the application I get the following error:

Error adding entry: SequelizeDatabaseError: there is no unique or exclusion constraint matching the ON CONFLICT specification

Expected Behavior

Have the chatbot answer my questions

Steps To Reproduce

1.Create .env file
2. Launch the application with npm run dev

Relevant log output

No response

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response

Is this your first time submitting a feature request?

• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing functionality

Describe the feature

add LLM memory to chat

const vectorStore = new MemoryVectorStore(new OpenAIEmbeddings());
    const memory = new VectorStoreRetrieverMemory({
      // 1 is how many documents to return, you might want to return more, eg. 4
      vectorStoreRetriever: vectorStore.asRetriever(1),
      memoryKey: "history",
    });

    // Build an LLM chain that will improve the user prompt
    const inquiryChain = new LLMChain({
      llm,
      prompt: new PromptTemplate({
        template: templates.inquiryTemplate,
        inputVariables: ["userPrompt", "conversationHistory"],
      }),
      memory: memory,
    });

Describe alternatives you've considered

No response

Who will this benefit?

everyone looking at the repository from coming from the article: https://www.pinecone.io/learn/javascript-chatbot/

Are you interested in contributing this feature?

yes would like to contribute :)

Anything else?

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When running 'npm run dev' command in the chatbot-demo project, a "Module not found" error occurs in the file src/pages/api/chat.ts at line 15. The import statement import { Metadata, getMatchesFromEmbeddings } from './embeddings' fails to resolve the './embeddings' module.

Expected Behavior

The import statement should successfully resolve the './embeddings' module and no "Module not found" error should occur.

Steps To Reproduce

1. Clone the chatbot-demo project from the Pinecone repository.
2. Run 'npm install' to install dependencies.
3. Run 'npm run dev' command to start the development server.

Relevant log output

error - ./src/pages/api/chat.ts:15:0
Module not found: Can't resolve './embeddings'
  13 |
  14 | import { ConversationLog } from './conversationLog';
> 15 | import { Metadata, getMatchesFromEmbeddings } from './embeddings';
  16 | import { templates } from './templates';
  17 |
  18 |

Environment

- **OS**: Darwin Kernel Version 21.6.0
- **Language version**: node v19.8.1
- **Pinecone client version**:

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When I run the command npm run dev, and redirected to UI, as I entered the text in textbox I am getting this error at backend terminal -
name: 'SequelizeDatabaseError',
parent: error: relation "conversations" does not exist
at Parser.parseErrorMessage (/home/chatbot-demo/node_modules/pg-protocol/dist/parser.js:287:98)
at Parser.handlePacket (/home/chatbot-demo/node_modules/pg-protocol/dist/parser.js:126:29)
at Parser.parse (/home/chatbot-demo/node_modules/pg-protocol/dist/parser.js:39:38)
at TLSSocket. (/home/chatbot-demo/node_modules/pg-protocol/dist/index.js:11:42)
at TLSSocket.emit (node:events:511:28)
at addChunk (node:internal/streams/readable:332:12)
at readableAddChunk (node:internal/streams/readable:305:9)
at Readable.push (node:internal/streams/readable:242:10)
at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23) {
length: 110,
severity: 'ERROR',
code: '42P01',
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: 'errors.go',
line: '171',
routine: 'NewUndefinedRelationError',
sql: "SELECT entry, speaker, created_at FROM conversations WHERE user_id = 'roie' ORDER By created_at DESC LIMIT 10",
parameters: undefined
},
original: error: relation "conversations" does not exist

Expected Behavior

It should run smoothly

Steps To Reproduce

Run npm run dev

Relevant log output

No response

Environment

- **OS**: linux
- **Language version**:Python 3.8.10
- **Pinecone client version**:

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When asking a question in the chat window, the app obviously finds the answer (see error message below), but doesn't output it in the chat dialogue (see screenshot)

See output from terminal below:

[ 'https://www.virke.no/arbeidsgiverstotte/pensjon/' ]
The retirement age in Norway varies between 62 and 75 years old. Employers can choose from four types of pension plans, but must follow any agreements made in a collective bargaining agreement. Employees have the right to reduce their working hours starting at age 62, but the reduction cannot result in a reduced position. There are no limits on how much the working hours can be reduced, but it must not cause significant inconvenience to the company. Virke offers a personal handbook and membership benefits, including legal advice on employment law.
The content does not provide information on the retirement age.

Based
 on
 the
 given
 context
,
 unfortunately
,
 there
 is
 no
 specific
 information
 about
 the
 retirement
 age
 in
 Norway
.
 However
,
 you
 can
 refer
 to
 Vir
ke
's
 website
 for
 more
 information
 about
 the
 pension
 plans
 and
 benefits
 available
 for
 employees
 and
 employers
 in
 Norway
.
 The
 following
 link
 will
 take
 you
 to
 the
 relevant
 page
:
 [
Source
](
https
://
www
.v
ir
ke
.no
/ar
be
id
sg
iver
st
otte
/p
ens
jon
/
).

Here is my table in cockroacdb:

Expected Behavior

Answer the user in the chat window – not just in terminal

Steps To Reproduce

1. Run the app
2. Ask a question you know is in the documentation

Relevant log output

No response

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

error - ./src/pages/api/chat.ts:15:0
Module not found: Can't resolve './embeddings'
13 |
14 | import { ConversationLog } from './conversationLog';

15 | import { Metadata, getMatchesFromEmbeddings } from './embeddings';
16 | import { templates } from './templates';
17 |
18 |

https://nextjs.org/docs/messages/module-not-found

Expected Behavior

Works

Steps To Reproduce

• Clone
• npm run dev
• Navigate to demo
• Type message
• Error appears in browser and console saying:

error - ./src/pages/api/chat.ts:15:0
Module not found: Can't resolve './embeddings'
  13 | 
  14 | import { ConversationLog } from './conversationLog';
> 15 | import { Metadata, getMatchesFromEmbeddings } from './embeddings';
  16 | import { templates } from './templates';
  17 | 
  18 | 

https://nextjs.org/docs/messages/module-not-found

Relevant log output

No response

Environment

- **OS**: Mac
- **Language version**: Node 18
- **Pinecone client version**: `"@pinecone-database/pinecone": "^0.1.5",`

Additional Context

Found this demo from: https://www.pinecone.io/learn/javascript-chatbot/

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When submitting a prompt, i get the following error message

Expected Behavior

It should fetch the data from pinecone and return the relevant response

Steps To Reproduce

run npm run dev
type 'test' in chat and hit submit

Relevant log output

Error submitting message: SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON

Environment

No response

Additional Context

No response

Is this a new bug?

• I believe this is a new bug
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When entering the URL below as per the tutorial (without my url and index name):

https://localhost:3000/api/crawl?urls=url1,url2&limit=10&indexName=yourIndexName

it should upsert the relevant document into pinecone index, however it consoles the following error message:

"Uncaught Error: self signed certificate in certificate chain"

I've tried with a website URL as well as a PDF document and get the same output

Expected Behavior

it should upsert the relevant document into pinecone index,

Steps To Reproduce

npm run start
enter:
https://localhost:3000/api/crawl?urls=url1,url2&limit=10&indexName=yourIndexName
(with own url/document pdf)

Relevant log output

Uncaught Error: self signed certificate in certificate chain

getServerError @ client.js:1
eval @ index.js:598
setTimeout (async)
eval @ index.js:586
asyncGeneratorStep @ _async_to_generator.js:13
_next @ _async_to_generator.js:31
Promise.then (async)
asyncGeneratorStep @ _async_to_generator.js:22
_next @ _async_to_generator.js:31
eval @ _async_to_generator.js:36
eval @ _async_to_generator.js:28
_hydrate @ index.js:641
hydrate @ index.js:528
eval @ next-dev.js:40
Promise.then (async)
eval @ next-dev.js:35
./node_modules/next/dist/client/next-dev.js @ main.js?ts=1689008685415:236
options.factory @ webpack.js?ts=1689008685415:661
__webpack_require__ @ webpack.js?ts=1689008685415:37
__webpack_exec__ @ main.js?ts=1689008685415:1072
(anonymous) @ main.js?ts=1689008685415:1073
webpackJsonpCallback @ webpack.js?ts=1689008685415:1209
(anonymous) @ main.js?ts=1689008685415:9

Environment

- **OS**:
- **Language version**:
- **Pinecone client version**:

Additional Context

No response