Describe the bug When running slackdump, channels.json has <code

Intersting, I had never had an emtpy channels output: are you

Also, would you mind running it with trace option and share a trace fi

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

channels.json empty/null about slackdump HOT 4 CLOSED

rusq commented on May 30, 2024

channels.json empty/null

from slackdump.

Comments (4)

rusq commented on May 30, 2024

Intersting, I had never had an emtpy channels output:

are you running export on the full account or guest (is your Slack account - a workspace member account or multichannel guest)?
If you run ./slackdump -c does it list the channels?

from slackdump.

rusq commented on May 30, 2024

Also, would you mind running it with trace option and share a trace file in the private dropbox? This would be a great help in understanding what's going on:

./slackdump -v -export bug -download -trace trace.out list of channels

Could you please also confirm that it actually exports the channel contents, and only channels.json is null?

from slackdump.

csaket commented on May 30, 2024

Must have been a temporary glitch for our slack account.
I am able to get the data correctly now.

from slackdump.

rusq commented on May 30, 2024

@csaket I found out what's causing it, because stumbled on my own.

When running the export for only DMs, the channels.json, which lists the public channels contains just null, because there are no public channels requested.

I just submitted the #160 , it fixes this behaviour by initialising channels with empty list. This will prevent slack-export-viewer from crashing in surprise.

from slackdump.

Recommend Projects