Data ingestion drag & drop is glitchy

Vectara Platform Q&A
1

The drag-and-drop interface on the data ingestion tab acts glitchy for me. I usually have to do some combination of repeated drag-and-drops and refreshing to get it to upload. Here’s an example, I had to drag twice and on the 2nd try it just got stuck on “Processing”.

screencast

After a few more tries and refreshing it eventually worked.

I’m using Chrome on Ubuntu 22.04. I got similar results in Firefox.

2

Hey, thanks for raising this! That looks like a frustrating bug. I’m a UI engineer at Vectara and I’ll fix this. Could you give me a little more info that will help me reproduce this bug?

  • How many files are you dragging and dropping when you hit this bug?
  • Roughly, how large is the largest file?
  • How large is the total filesize of the files you’re dragging and dropping?

Last question: do you see any errors in the Chrome Developer Tools Console when this bug happens? Could you take a screenshot of the error? Here are steps for finding the Chrome Developer Tools Console: Finding Your Browser's Developer Console | Balsamiq

Thanks again.

3

Sure.
I’ve only dragged one file at a time. The one in the gif was a PDF 3.8MB in size. The largest file I’ve uploaded is an 8.6MB PDF.

There is a warning (starts with “DevTools failed”) that pops up when I reload the page. Then an error that pops up when I drag something into the upload box:

image
image1260×312 38.2 KB

Here’s the full stack trace:

DevTools failed to load source map: Could not parse content for https://console.vectara.com/rudder-analytics.min.js.map: Unexpected token '<', "<!doctype "... is not valid JSON
DataUpload.js:601 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'isFile')
    at DataUpload.js:601:15
    at l (runtime.js:63:40)
    at Generator._invoke (runtime.js:294:22)
    at Generator.next (runtime.js:119:21)
    at o (asyncToGenerator.js:3:20)
    at s (asyncToGenerator.js:25:9)
    at asyncToGenerator.js:32:7
    at new Promise (<anonymous>)
    at asyncToGenerator.js:21:12
    at Fe (DataUpload.js:609:2)
(anonymous) @ DataUpload.js:601
l @ runtime.js:63
(anonymous) @ runtime.js:294
(anonymous) @ runtime.js:119
o @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
Fe @ DataUpload.js:609
Pe @ DataUpload.js:590
(anonymous) @ DataUpload.js:179
l @ runtime.js:63
(anonymous) @ runtime.js:294
(anonymous) @ runtime.js:119
o @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
(anonymous) @ DataUpload.js:175
onDrop @ DataUpload.js:458
Pe @ react-dom.production.min.js:54
je @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
Uo @ react-dom.production.min.js:105
No @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
uu @ react-dom.production.min.js:274
Fe @ react-dom.production.min.js:52
Wo @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73
Promise.then (async)
o @ asyncToGenerator.js:13
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
(anonymous) @ DataUpload.js:175
onDrop @ DataUpload.js:458
Pe @ react-dom.production.min.js:54
je @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
Uo @ react-dom.production.min.js:105
No @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
uu @ react-dom.production.min.js:274
Fe @ react-dom.production.min.js:52
Wo @ react-dom.production.min.js:109
Kt @ react-dom.production.min.js:74
qt @ react-dom.production.min.js:73

FWIW it works fine on Windows 10 Pro, I couldn’t reproduce it there.

4

Thank you! This is super helpful. I’ll let you know when we have a fix for this.

5

@tango Just wanted to give you an update. I have a fix in place and it will ship within the next week. I’ll let you know when that happens. Thanks for your patience!

1 Like