sigit/sigit.io
7
2
Fork 0
Code Issues 32 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

Retry sending file to file server #71

New Issue
Open
opened 2024-05-22 13:53:44 +00:00 by y · 2 comments
y commented 2024-05-22 13:53:44 +00:00
Owner
Copy Link

Each upload should be attempted at least twice.

Each upload should be attempted at least twice.
y added the
Kind/Enhancement
Priority
Medium
 labels 2024-05-22 13:53:56 +00:00
b added this to the MVP project 2024-05-22 15:06:08 +00:00
b commented 2024-05-22 15:19:40 +00:00
Owner
Copy Link

For info. The future plan will be to allow the user to configure the preferred blossom server(s).

For info. The future plan will be to allow the user to configure the preferred blossom server(s).
👍 1
m was assigned by b 2024-12-30 09:50:44 +00:00
m commented 2025-01-03 13:28:16 +00:00
Owner
Copy Link

In the future, we will add a "Status" modal, which would include relays publishing statuses and failing with the option to retry, etc., similar to the Nostrudel approach. I will create such a model to address this issue, and for now, I will only use it for Blossom publishing (logs and retries). Later, we can expand this modal for other needs (Relays).

In the future, we will add a "Status" modal, which would include relays publishing statuses and failing with the option to retry, etc., similar to the Nostrudel approach. I will create such a model to address this issue, and for now, I will only use it for Blossom publishing (logs and retries). Later, we can expand this modal for other needs (Relays).
b moved this to In Progress in MVP on 2025-01-10 10:14:38 +00:00
b moved this to In Progress in MVP on 2025-01-10 10:16:00 +00:00
b moved this to In Progress in MVP on 2025-01-10 10:17:08 +00:00
enes moved this to In Progress in MVP on 2025-01-20 19:28:29 +00:00
enes moved this to In Progress in MVP on 2025-01-20 19:28:31 +00:00
enes moved this to In Progress in MVP on 2025-01-24 09:37:18 +00:00
enes moved this to In Progress in MVP on 2025-01-24 14:07:29 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Enhancement
Priority
Medium
Milestone
No items
No Milestone
Projects
Clear projects
No project MVP
Assignees
Clear assignees
No Assignees m
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#71
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?