DreamExposure / DisCal-Discord-Bot

DisCal is a Discord Bot that links up to a Google Calendar to create, delete, edit, and announce events and more!
GNU General Public License v3.0
112 stars 44 forks source link

Announcements Creation can't be confirmed #67

Closed smnc closed 3 years ago

smnc commented 4 years ago

Who is the bug affecting?

Users issuing commands

What is affected by this bug?

The bot

When does this occur?

Where on the platform does it happen?

Announcement Creation Wizard

How do we replicate the issue?

Try to create an announcement

Expected behavior (i.e. solution)

!a confirm should save the announcement and close the wizard

Other Comments

May be related to https://github.com/DreamExposure/DisCal-Discord-Bot/issues/63 ?

smnc commented 4 years ago

I've been unable to replicate this. I've tried in multiple servers on 3 different shards, on both internal and external calendars.

NovaFox161 commented 4 years ago

I am also unable to replicate this. I'll need more information from the user(s) having issues in order to dig into the code.

smnc commented 4 years ago

Not an expert, but I didn't see any obvious errors in the log that correlated either. dc-ticket-1747 and 1752 if you want to follow up with the users.

NovaFox161 commented 4 years ago

Looks like it may be related to announcement editing and not actually creating a new announcement. I'll have to check if that guess is right, but that appears to be the case in 1747. 1752 is unclear as for if its while creating a new announcement or editing an announcement.

smnc commented 4 years ago

Adding ticket 1762 to the list

NovaFox161 commented 4 years ago

1747 seems to have resolved itself on its own. No idea what is different as the only code changes related to this are deployed on shard 1.

smnc commented 4 years ago

1825 looks like another one.

NovaFox161 commented 3 years ago

I'm going to assume this has either been patched by my own code changes, or this issue was externally caused and has resolved itself as we have not been getting any new reports regarding this issue nor have we ever been able to replicate this.