External/card-drop
4
0
Fork 0
Code Issues 22 Pull requests 1 Actions Packages Projects 1 Releases 24 Wiki Activity

When claiming legendary cards, the embed will fail to update the interaction, but will save the card to the database #245

New issue
Closed
opened 2024-05-29 14:48:16 +01:00 by Helpdesk · 1 comment
Helpdesk commented 2024-05-29 14:48:16 +01:00
Member
Copy link

Current behaviour

The card will be saved to the user's inventory, but the interaction fails to update the embed. This seems to only affect legendary cards.

image

Expected behaviour

The embed should update to say it was claimed by another user, like other cards.

## Current behaviour The card will be saved to the user's inventory, but the interaction fails to update the embed. This seems to only affect legendary cards. ![image](/attachments/4b1c69e0-445b-4d45-8a72-e2652c004e56) ## Expected behaviour The embed should update to say it was claimed by another user, like other cards.
image.png
60 KiB
Helpdesk added the
type
bug
 label 2024-05-29 14:48:20 +01:00
Vylpes self-assigned this 2024-05-29 17:16:55 +01:00
Vylpes started working 2024-05-29 17:17:20 +01:00
Vylpes added this to the 0.5.2 milestone 2024-05-29 17:36:05 +01:00
Vylpes added this to the 0.6 Sprint 7 project 2024-05-29 17:36:08 +01:00
Vylpes stopped working 2024-05-29 17:42:36 +01:00
25 minutes 16 seconds
Vylpes commented 2024-05-29 17:44:00 +01:00
Owner
Copy link

A fix has been implemented and pending release. The issue was to do with the command trying to reupload the attachment, which it had limited time to do. This was only affecting legendaries due to their large size compared to the other files.

This has been fixed by defering the update as well as making it only update the embed and reuse the already-uploaded attachments

A fix has been implemented and pending release. The issue was to do with the command trying to reupload the attachment, which it had limited time to do. This was only affecting legendaries due to their large size compared to the other files. This has been fixed by defering the update as well as making it only update the embed and reuse the already-uploaded attachments
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
develop
renovate/ts-jest-29.x-lockfile
hotfix/0.6.4
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.2
v0.5.1
v0.5.0
v0.4.2
v0.4.1
v0.4.0
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.8
v0.1.7
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
blocked

   
duplicate

   
question

   
requires documentation
  
type
admin

  
type
bug

  
type
change

  
type
defect

  
type
dependencies

  
type
epic

  
type
spike

  
type
story

  
type
subtask

  
won't fix
No labels
blocked
duplicate
question
requires documentation
type
admin
type
bug
type
change
type
defect
type
dependencies
type
epic
type
spike
type
story
type
subtask
won't fix
Milestone
Clear milestone
No items
No milestone
0.5.2
Projects
Clear projects
No items
No project
0.6 Sprint 7
Assignees
Clear assignees
No assignees
Vylpes
2 participants
Notifications
Total time spent: 25 minutes 16 seconds
Vylpes
25 minutes 16 seconds
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: External/card-drop#245
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?