Issues CSV export fails when given an issue where `author` is nil

I'm not sure if this is due to the size of the export, or a particular issue tripping things up.

I couldn't see anything in sentry

It could also be Sidekiq MemoryKiller , but I can't see memory usage going near 1GB on Grafana - Sidekiq Workers (ExportCsvWorker). Although I believe SIDEKIQ_MEMORY_KILLER_MAX_RSS is set to 1000000kb, the graph could be excluding shared memory.

@jamedjo This also happens for the GitHub importer.

@dbalexandre Caused by MemoryKiller? Or just the silent failure in general.

Looks like this might not be due to size. I was able to find logs in kibana by searching for ExportCsvWorker.

Looks like the failure was due to an authorless issue (https://gitlab.com/gitlab-org/gitlab-ce/issues/7077)

From the kibana log:

2017-03-17T17:01:23.213Z 24077 TID-otlefxntc WARN: {"context":"Job raised exception","job":{"class":"ExportCsvWorker","args":[654619,13083,{"scope":"all","state":"opened","project_id":13083,"sort":"created_desc"}],"retry":3,"queue":"export_csv","jid":"2758920dd1f19d8278f81ddd","created_at":1489769967.6072545,"enqueued_at":1489770069.8991404,"error_message":"Issue#author_name delegated to author.name, but author is nil: #<Issue id: 1022226, title: "Authorless issue", assignee_id: nil, author_id: 371411, project_id: 13083, ...

changed title from Attempting to export gitlab-ce issues as CSV fails silently to {+Issues CSV export fails when given an issue where author is nil+}

added ~874214 ~91797 reproduced on GitLab.com labels

changed milestone to %9.0

@jamedjo Silent failure in general that we think that the root cause is the MemoryKiller, because some customers could import some large projects in their instances that were failing on GitLab.com disabling it. Thanks for the tips about logs in Kibana, I'll have a look

mentioned in merge request !1454 (merged)

closed via commit b805ae34c496ff9d37ef1008d2a932d2cb9c1f98

mentioned in commit 4e5e15d5