BulkOverwrite has stopped functioning
In the last 5 months have there been any breaking changes to how commands register? I created 2 sapphirecli slash commands and one has appeared after several days (roll), the other one (createchannel) was pushed 2 hours ago and has not shown up in the BulkOverwritten guild yet.
Solution:Jump to solution
I think I might be deleting/creating my container incorrectly, is this not enough to update a running container?
37 Replies
in index.ts
also added these to lib/setup.ts
no if there would be a new semver major version of sapphire would've been published. Semver doesn't allow breaking changes in patch or minor versions.
make sure you're compiling your TS code
and clean dist to be sure
hmm would this still apply given that it’s a docker image that is recreated every commit and deleted/pulled every time? no volumes either
it wouldnt, but make sure that your docker builds are working and not failing during build
don’t think they are, I have it set up through GH actions and it wouldn’t pass the pipeline unless it succeeded
so is the pipeline green?
yes sir it is
one second
Any other ideas @Favna ? It still hasn’t shown up which is making me think it’s my code.. https://github.com/masonbesmer/lyra-sapphire/blob/main/src/commands/CreateChannel.ts
GitHub
lyra-sapphire/src/commands/CreateChannel.ts at main · masonbesmer/l...
A rewrite of Night City's Discord bot, in TypeScript, using SapphireJS. Now using GitHub Actions! - masonbesmer/lyra-sapphire
Can you try setting the default behaviour to overwrite instead of bulk?
I can't recall what it was, would have to search this forum, but there was a weird bug with bulk before
Maybe if you search this channel for BulkOverwrite you can find that thread again
I think I tried that already but I only gave it 10 or so minutes to update and it hadn’t: https://github.com/masonbesmer/lyra-sapphire/commit/6ef2e6dea65c38f883cfdc09de0110cadcf219cf
I can try it again though and leave it for a few hours
commands should always register instantly
waiting a few hours does nothing
that's something of way back in the day only
oh. I’ll try it again and see if it randomly works this time
Good to know though
has to be something wrong with my code 🙄 still not appeared overnight
@vladdy thy hath been summoned
huh
which cmd doesnt show up
CreateChannel
I think I may have just figured it out, but im veryifying rq
Solution
I think I might be deleting/creating my container incorrectly, is this not enough to update a running container?
you're doing What
oh
this is why you use docker compose 👀
:whatge:
done
is it perchance a dropin replacement?
no you need to write a compose file
but you'd do well to do that
btw ithink the issue is your categoryID option, idk if it can have upper case letters
but it should log to the console....
do you have any listeners for
CommandApplicationCommandRegistryError
?I have this as
control.sh
(which in turn is added to PATH) on my linux machines
so I just run control update <service>
and boom it updatesI could also use the logs from when you started the bot when it was running with VerboseOverwrite
yes, that is what caused me to think it was my deployment method, because when i forcefully updated the container, it started showing that error
it appears that was the only issue though
I have fixed the command temporarily and it now functions properly
root cause analysis: PICNIC
now this is nice
PICNIC?
I mean I know what a picnic is but I've never heard it used as abbreviation
Problem In Chair, Not In Computer
oohhh
got a very, very noob question for you: do I push my docker-compose.yml to my git repo and let it be built in to the image, or do i only put it on my production server? I'm not exactly 100% sure how compose works
I do a mix. On the repo is a compose file but it's meant for Dev. The prod server has a separate one because it has env vars for credentials and such.
That prod one we backup periodically by gzipping it together with some other files and actually tonight I'm going to explore the new feature of EaseUS Todo Backup free that can auto sync over SFTP (3-2-1 backups)
that's what I figured. thank you, found a nice site to convert from docker run to docker compose so I am switching over rn and probably going to adopt your script