"Failed - Network Error" when exporting Contacts

[estellecomment]

In Chrome.

I can export reports just fine.
No console errors, no API errors.
The file is called download, instead of contacts-<timestamp>.json when it's working.

I'm suspecting the getHref(res), in ajaxDownload module, with res = array[998], is too big to run. When I reduce it to array[5] it goes through.

[SCdF]

@estellecomment would you say this is the same as #2694 ? As in, this is occurring because you have a very large data set on a feature that otherwise works? I think this should have the same priority as #2694: i.e. not hugely important unless a client is having trouble.

[estellecomment]

It's JSON instead of XML, but otherwise yes.

[SCdF]

OK cool I dropped it out of the sprint.

[nice-snek]

hi frand @abbyad, please triage before the end of this sprint.

--..,_                        _,.--.
       ''.'.                .''__ o  ';__.
          '.'.            .'.''  '---''  '
            '.''--....--''.'
              ''--....--''

[abbyad]

@estellecomment has this been resolved by #3107 or #3109?

[estellecomment]

Nope, still happening. I'm leaving it open, I'm not sure the feature is being used, but it's definitely broken.

Now I get this api error :

Server error:
 { code: 503,
  message: 
   { Error: connect ECONNREFUSED 127.0.0.1:5985
       at Object.exports._errnoException (util.js:1023:11)
       at exports._exceptionWithHostPort (util.js:1046:20)
       at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1090:14)
     code: 'ECONNREFUSED',
     errno: 'ECONNREFUSED',
     syscall: 'connect',
     address: '127.0.0.1',
     port: 5985 } }

[SCdF]

@estellecomment port 5985 is lucene. You probably aren't running lucene, and apparently it's required.

[estellecomment]

o_O
Thanks for the fact-checking!

With lucene running, the bug is still happening, and error from api is

Server error:
 { code: 503, message: { code: 500 } }

Database log says

[info] [<0.3011.0>] 127.0.0.1 - - GET /_session 200
[info] [<0.2867.0>] 127.0.0.1 - - GET /medic/ 401

(401??)
With admin user, locally.

[SCdF]

@estellecomment I don't want to sound like a magician, but have you tried running it twice?

[estellecomment]

https://www.youtube.com/watch?v=nn2FB1P_Mn8

[estellecomment]

I just did, also with one eye closed, still happening. Anything specific you're looking for? :)

[SCdF]

Just checking. I've found when I setup lucene locally it always fails the first time.

[medic-bot]

Hi @vimemo,

This ticket has not been touched in 90 days. Is it still relevant?

(See triaging old issues for more detail)

[vimemo]

This is still an issue. It has to do with sorting by name.
For some reason, orderBy: 'name', returns the error described before:
Server error:
{ code: 503, message: { code: 500 } }

The json is downloaded correctly when removing the sorting/orderBy.
Do we need an index for lucene to work?
Do we need a different syntax?

[garethbowen]

@SCdF Is this related to your CSV export work?

[SCdF]

Good catch, yeah! This will be "fixed" by it being reimplemented in #3594 . I'm going to close this as a wontfix, since the Lucene export api will be deprecated in the work I'm doing.