Updating sets on Discord driver unsuccessful

[LuciousLisa]

SeAT v4
SeAT Connector v2.0.2
Discord Connector v5.0.0

Expected result: being able to choose Discord roles so that they can be assigned.
Current result: no Discord roles available to assign to SeAT roles, corp titles, etc.

Steps to reproduce:

• On Discord: drag bot role to top of roles list in server settings
• On SeAT: navigate to Connector > Settings
• Select Discord in drivers dropdown, click Update Sets button
• Keep an eye on Horizon jobs to see the job DriverUpdateSets running (orange pause icon)
• After several minutes, see Horizon job get red cross icon, indicating failure (note that the job does not show under Failed Jobs in Horizon)
• Navigate to Connector > Access Management
• Select type: Role Filters, select role: Full members
• Type in Set field Mem (from Members role available on Discord)
• Result: No results found

Please let me know if I'm doing something wrong or if there's something else I could be doing to resolve this issue. If not, then please consider this a bug report. If more info is needed I'll be happy to provide logs, screenshots etc.

[warlof]

After several minutes, see Horizon job get red cross icon, indicating failure (note that the job does not show under Failed Jobs in Horizon)

What's the reason of the failure? You should get it by going in the job. In all case, if the job is failing, you can't get anything in SeAT.

[LuciousLisa]

Where should I be able to find a reason for the failure? I'll add the following screenshots to illustrate what I'm seeing in Horizon.

• Job running: https://i.imgur.com/sLQxV9x.png
• Clicking View detail during the job results in this page: https://i.imgur.com/ewDxl48.png
• Job failed: https://i.imgur.com/4fdUYjj.png
• Clicking the (now clickable) DriverUpdateSets text results in in this page, which won't load. Note that other failed jobs can be clicked to view more details, such as a stack trace: https://i.imgur.com/ATIYrWG.png
• It doesn't show up in the list of failed jobs: https://i.imgur.com/HQsogSg.png

I understand that failed jobs result in a lack of data. Please advice on how to proceed to resolve this issue.

[AstralDestiny]

GuzzleHttp\Exception\ClientException: Client error: GET https://discord.com/api/guilds/734916090597212221/roles resulted in a 401 Unauthorized response:

{"message": "401: Unauthorized", "code": 0}
in /var/www/seat/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php:113

I pretty much get this, Don't know what I'm doing wrong if anything?
Same steps as the above but confused on the 401 Unauthorized response when I try and pull roles.

[AstralDestiny]

Warlof\Seat\Connector\Jobs\DriverUpdateSets
Stack Trace from Horizon https://pastebin.com/KXsGThnD
And
Warlof\Seat\Connector\Jobs\DriverApplyPolicies
Stack Trace from Horizon https://pastebin.com/r9MRx3yj

DATA:
{ client: null, driver: "discord", tags: [ "connector", "discord" ], job: null, connection: null, queue: "high", chainConnection: null, chainQueue: null, delay: null, middleware: [ ], chained: [ ] }

[AstralDestiny]

Ah nvm Got it all working :)

[LuciousLisa]

Ah nvm Got it all working :)

Would you mind telling us how? I have yet to receive a reply from the dev and would love to solve this as well. Please provide the steps you took to resolve the problem.

[AstralDestiny]

Ah nvm Got it all working :)

Would you mind telling us how? I have yet to receive a reply from the dev and would love to solve this as well. Please provide the steps you took to resolve the problem.

I thought I needed
warlof/seat-discord-connector and warlof/seat-connector for the discord driver to function but no just needed the First :)

[kevinouw]

@AstralDestiny https://eve-seat.slack.com/archives/CAPC5V8QK/p1602192886111900

[LuciousLisa]

Note that neither of these solutions (remove connector & reassign bot) have resulted in a fix for this issue.

[warlof]

Hi,

what about this check on the bot app ?
seems a new thing, according to some user, it seems to fix the sync.