Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add check for status and replied at #97

Merged
merged 3 commits into from
Jun 26, 2023
Merged

fix: add check for status and replied at #97

merged 3 commits into from
Jun 26, 2023

Conversation

im-adithya
Copy link
Member

Fixes #94

@im-adithya im-adithya requested a review from kiwiidb June 23, 2023 12:26
"replyEventId": resp.ID,
"appId": nostrEvent.AppId,
}).Info("Published reply")
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what should we do in the else case? what other state can status be? and I think we should log/save that one, too.
otherwise we do not know if/when/why this happens.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made changes, please review again

"replyEventId": resp.ID,
"appId": nostrEvent.AppId,
}).Info("Failed to publish reply")
} else {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you know what other status it can have? and when this could happen?

@bumi bumi merged commit 38068af into main Jun 26, 2023
@bumi bumi deleted the task-replied-at branch June 26, 2023 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

replied_at timestamp is not saved
3 participants