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

[BUG] - CSV Loader usable issue in Document Store #3159

Open
nmoturi opened this issue Sep 6, 2024 · 5 comments
Open

[BUG] - CSV Loader usable issue in Document Store #3159

nmoturi opened this issue Sep 6, 2024 · 5 comments
Labels
question Further information is requested

Comments

@nmoturi
Copy link

nmoturi commented Sep 6, 2024

Describe the bug
A clear and concise description of what the bug is.

Process issue using the CSV loader in Document Store. Below is the error

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
    Document Store, Add a new Document Loader - CSV Loader with Recursive Character Text Splitter
  2. Click on '....'
    Process
  3. See error

[ERROR]: unhandledRejection: Invalid URL

TypeError: Invalid URL

at new URL (node:internal/url:797:36)

at parseUrl (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/url-parser/dist-cjs/index.js:29:21)

at toEndpointV1 (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:119:41)

at customEndpointProvider (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:239:65)

Expected behavior
A clear and concise description of what you expected to happen.

Process the document

Screenshots
If applicable, add screenshots to help explain your problem.

image

Setup

  • Installation [e.g. docker, npx flowise start, pnpm start]
    Docker Installation
  • Flowise Version [e.g. 1.2.11]
    v2.0.7
  • OS: [e.g. macOS, Windows, Linux]
    Linux
  • Browser [e.g. chrome, safari]
    Chrome
@HenryHengZJ
Copy link
Contributor

works for me:
image

image

image

@HenryHengZJ HenryHengZJ added the question Further information is requested label Sep 9, 2024
@nmoturi
Copy link
Author

nmoturi commented Sep 10, 2024

Thanks, Henry. That's very strange. I have precisely the same flow. The logs indicate the below error, is there any reason why it's trying to access aws-sdk or this is normal..?

-Naran

at new URL (node:internal/url:797:36)

at parseUrl (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/url-parser/dist-cjs/index.js:29:21)

at toEndpointV1 (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:119:41)

at customEndpointProvider (/usr/local/lib/node_modules/flowise/node_modules/@aws-sdk/client-s3/node_modules/@smithy/middleware-endpoint/dist-cjs/index.js:239:65)

@HenryHengZJ
Copy link
Contributor

I'm not sure, but does it happen only on one CSV? Can you try other CSV as well?

@nmoturi
Copy link
Author

nmoturi commented Sep 17, 2024 via email

@moturi12
Copy link

This issue is resolved, I was using the S3 for blob storage and pointing to wrong endpoint
Thanks,
Naran

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants