Replies: 4 comments
-
what are the files you have in |
Beta Was this translation helpful? Give feedback.
-
But the presence of the |
Beta Was this translation helpful? Give feedback.
-
i could write up an MR with the changes I made to make things work and you could take a look if you like @SudhanPlayz , if you don't want to make the change that is okay too |
Beta Was this translation helpful? Give feedback.
-
I guess I do not have permission to contribute to this project, but the code change I made locally is quite simple. I would rather not have a fork to maintain, so I would love to see it make it back into this project somehow.
It was as simple as adding this to both the DiscordMusicBot.js#LoadEvents and DiscordMusicBot.js#LoadCommands, right after we begin iterating through the files. Would love to see this make it into the codebase. Let me know if I can help further. EDIT: I see now that contributions are only allowed for the v5 branch, I've been working entirely with what is on master so I'll need to look into v5 I guess |
Beta Was this translation helpful? Give feedback.
-
I am running my own Heroku project, and taking the source code here + following the documentation I was able to complete a Heroku deploy pretty easily. Only, I found a single problem that was occurring whenever I would attempt to run (using a worker dyno).
The logs weren't entirely clear what was happening, so I added a little more explicit logging and this is what I found was being output during startup:
A little more research on these
.wh..wh..opq
files lead me to this: https://github.com/opencontainers/image-spec/blob/main/layer.md#whiteoutsThis appears to be a result of the layering of images that Heroku steps through, that is then causing an issue when the bot attempts to iterate through the
/events/
/commands/
directories.Locally, I was able to reproduce the same issue by creating this file (or really any random file) in the
/events/
or/commands/
dirs and then starting the app. I made some quick hacky changes locally to get past this (confirm that the files within these directories end with .js before trying to process them), but I'd rather not have to maintain a fork going forward to get around this issue.I would be happy to open a suggestion PR if you agree this is something you would like to see changed for this project, but I'm assuming that my use-case is in the minority here so I understand if you do not want to make any changes to help with this issue.
Beta Was this translation helpful? Give feedback.
All reactions