Tribe
Tribe
Explore posts from servers
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
Does anyone know if the gateway events require any ports besides 80 or 443?
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
the job that pulls depends on the job that builds and pushes
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
I believe I have narrowed down the cause. It seem to work when I build the image locally, push it to dockerhub and then pull it to my remote VM and run it. The point of failure is when I build it in a gitub action and then push to dockerhub. But its the same command so I am really unsure what the difference is that could be causing events to fail just from building the same exact image on gibhub vs local.
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
The ready isnt actually firing even once, I put a console log in the event handler that does go off the few times everything has fired up and worked, but the ready event log isnt actually included in this log. This is just the debug and warn evens being logged along with a few other logs from my script.
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
Preparing to connect to the gateway...
[WS => Manager] Fetched Gateway Information
URL: wss://gateway.discord.gg
Recommended Shards: 1
[WS => Manager] Session Limit Information
Total: 1000
Remaining: 987
[WS => Shard 0] Connecting to wss://gateway.discord.gg?v=10&encoding=json
[WS => Shard 0] Waiting for event hello for 60000ms
[WS => Shard 0] Preparing first heartbeat of the connection with a jitter of 0.3040686103552612; waiting 12542ms
[WS => Shard 0] Waiting for identify throttle
[WS => Shard 0] Identifying
shard id: 0
shard count: 1
intents: 33283
compression: none
[WS => Shard 0] Waiting for event ready for 15000ms
Logged in: true
[WS => Shard 0] Shard received all its guilds. Marking as fully ready.
Successfully registered 2 command(s) with 1 guild(s).
[WS => Shard 0] First heartbeat sent, starting to beat every 41250ms
[WS => Shard 0] Heartbeat acknowledged, latency of 25ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 27ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 23ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 22ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 29ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
Preparing to connect to the gateway...
[WS => Manager] Fetched Gateway Information
URL: wss://gateway.discord.gg
Recommended Shards: 1
[WS => Manager] Session Limit Information
Total: 1000
Remaining: 987
[WS => Shard 0] Connecting to wss://gateway.discord.gg?v=10&encoding=json
[WS => Shard 0] Waiting for event hello for 60000ms
[WS => Shard 0] Preparing first heartbeat of the connection with a jitter of 0.3040686103552612; waiting 12542ms
[WS => Shard 0] Waiting for identify throttle
[WS => Shard 0] Identifying
shard id: 0
shard count: 1
intents: 33283
compression: none
[WS => Shard 0] Waiting for event ready for 15000ms
Logged in: true
[WS => Shard 0] Shard received all its guilds. Marking as fully ready.
Successfully registered 2 command(s) with 1 guild(s).
[WS => Shard 0] First heartbeat sent, starting to beat every 41250ms
[WS => Shard 0] Heartbeat acknowledged, latency of 25ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 27ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 23ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 22ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 29ms.
[WS => Shard 0] Heartbeat acknowledged, latency of 21ms.
Here is the log when it stops responding to events, the ready event also does not fire as well but everything else logs wise looks healthy (to me). Does anything stand out that could be an issue?
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
Will have to keep an eye on it with these logs running, I recently moved the container to digital ocean which seemed to have fixed the issue. However it does seem to happen intermittently
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
So upon looking into this, I am getting the token returned from the login method, but no the ready event is not firing
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/9/2023 in #djs-questions
Docker ports on GCP & AWS
Logs in but I haven’t checked if ready is firing. Deployed it to digital ocean last night and seemed to work fine. So appears to be isolated to GCP VMs
14 replies
DIAdiscord.js - Imagine an app
Created by Not Toby on 10/9/2023 in #djs-questions
Slash Command Error - I have no idea why
await existingCommand.edit({
name: 'enter your name',
description: 'enter your desc',
options: your options,
})
await existingCommand.edit({
name: 'enter your name',
description: 'enter your desc',
options: your options,
})
14 replies
DIAdiscord.js - Imagine an app
Created by Not Toby on 10/9/2023 in #djs-questions
Slash Command Error - I have no idea why
I would just pass in the edits as an object
14 replies
DIAdiscord.js - Imagine an app
Created by Not Toby on 10/9/2023 in #djs-questions
Slash Command Error - I have no idea why
Looks like you arent passing anything into await existingCommand.edit(); which would explain why your payload to register the command is completely undefined
14 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 10/25/2022 in #djs-questions
awaitMessageComponent method on InteractionResponse
Discord.js version ^14.6.0 No error, interaction just times out.
3 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
thats a lotta versions to support at once
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
wow
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
youre right I had copied over the URL from discord docs which doesn't have the version in the URL so I guess it does fall back to a really old version
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
hmmm maybe I have a typo somewhere, will double check and follow up
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
yeah it does
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/16/2022 in #djs-questions
permissions_new from API
10
15 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/1/2022 in #djs-questions
Mentionables breaking on mobile
you know Ive always seen that just never put any thought as to why
11 replies
DIAdiscord.js - Imagine an app
Created by Tribe on 8/1/2022 in #djs-questions
Mentionables breaking on mobile
thanks
11 replies