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

Failed to publish notifications after signing the doc #292

New Issue
Closed
opened 2024-12-27 10:46:22 +00:00 by endo · 3 comments
endo commented 2024-12-27 10:46:22 +00:00
Member
Copy Link

I've signed the doc we were testing on the call today

image

but got the error message "Failed to publish notifications "

image
I've signed the doc we were testing on the call today ![image](/attachments/447447d7-d6d9-448c-828f-522ea09ada0a) but got the error message "Failed to publish notifications " <img width="332" alt="image" src="attachments/3f083033-9a3b-4242-8838-7e13ddd87c46">
image.png
25 KiB
image.png
23 KiB
staging.sigit.io-1735296368258.log
18 KiB
endo added reference staging 2024-12-27 10:48:06 +00:00
endo added the
Kind/Bug
 label 2024-12-27 10:48:11 +00:00
endo added this to the MVP milestone 2024-12-27 10:48:30 +00:00
endo added this to the MVP project 2024-12-27 10:49:06 +00:00
enes commented 2024-12-27 12:20:14 +00:00
Member
Copy Link

Related to #290

Related to https://git.nostrdev.com/sigit/sigit.io/issues/290
enes added a new dependency 2024-12-27 12:21:07 +00:00
#290 Extension and sigit can have different "logged in" users
enes was assigned by endo 2024-12-30 09:46:41 +00:00
enes moved this to Pending in MVP on 2025-01-20 19:17:27 +00:00
enes moved this to Pending in MVP on 2025-01-20 19:17:29 +00:00
enes moved this to Pending in MVP on 2025-01-20 19:17:37 +00:00
enes moved this to Pending in MVP on 2025-01-20 19:17:45 +00:00
enes moved this to Pending in MVP on 2025-01-20 19:18:24 +00:00
enes commented 2025-01-20 20:34:57 +00:00
Member
Copy Link

Unable to replicate the issue.

I believe that issue was initially caused by swapping extension and not logging out when creating an event, that was fixed soon after and now the user will be forcefully logged out as soon as we detect a mismatch between auth pubkey and extension pubkey whould should stop this from happening again.

Nonetheless, @endo I'd like to test again with that account just in case. To make sure the issue is localized to this malformed sigit.

Unable to replicate the issue. I believe that issue was initially caused by swapping extension and not logging out when creating an event, that was fixed soon after and now the user will be forcefully logged out as soon as we detect a mismatch between auth pubkey and extension pubkey whould should stop this from happening again. Nonetheless, @endo I'd like to test again with that account just in case. To make sure the issue is localized to this malformed sigit.
enes commented 2025-01-24 09:36:38 +00:00
Member
Copy Link

Unable to replicate. The Sigit in question published successfully during the demo.

Unable to replicate. The Sigit in question published successfully during the demo.
enes closed this issue 2025-01-24 09:36:38 +00:00
enes moved this to Done in MVP on 2025-01-24 09:37:11 +00:00
Sign in to join this conversation.
staging
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/Bug
Milestone
No items
No Milestone MVP
Projects
Clear projects
No project MVP
Assignees
Clear assignees
No Assignees enes
2 Participants
Notifications
Due Date
No due date set.
Depends on
#290 Extension and sigit can have different "logged in" users
sigit/sigit.io
Reference: sigit/sigit.io#292
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?