Skip to content

[Hotfix] [Dev] fix duplicates in emails #157

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

Merged

Conversation

maxceem
Copy link
Contributor

@maxceem maxceem commented Oct 2, 2019

Fix for the issue which is tracked in Connect App appirio-tech/connect-app#3216

Additionally, make a fix for a potential issue. See commit message for details.

So far I guess we don't have such a case as there were no issues raised.
But if some messages don't have initiatorUserId, there would be an error during requesting user details.
Copy link

@vikasrohit vikasrohit left a comment

Choose a reason for hiding this comment

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

LGTM. @maxceem I don't think we should ever miss the initatorUserId in the even payload and if it is happening somewhere, we might need to debug it. However, on the other hand, there might be a case where the event is not triggered by a user but it is system event, in which case we might not have the initiator user id. But still, we can supply a system user id in such cases to uniquely identify the initiator.
However, I don't think the safety check would harm us any way. So, we should be good for now.

@vikasrohit vikasrohit merged commit f7ca1c2 into topcoder-platform:dev Oct 3, 2019
@vikasrohit
Copy link

Just to confirm @maxceem we are not merging this hotfix to master, right?

@maxceem
Copy link
Contributor Author

maxceem commented Oct 3, 2019

Just to confirm @maxceem we are not merging this hotfix to master, right?

I was thinking that we would like to merge it to master as a hotfix. Looks like I've accidentally created it agains the dev.

@vikasrohit
Copy link

Okay, if we have the front end changes for it in our next hotfix for 2.4.15.2, we can create hotfix against master for this repo as well. No issue with that as well.

@maxceem
Copy link
Contributor Author

maxceem commented Oct 3, 2019

Okay, if we have the front end changes for it in our next hotfix for 2.4.15.2, we can create hotfix against master for this repo as well. No issue with that as well.

This issue only requires changes in the tc-notifications repo in this PR. No frontend changes are required. So it can be merged now as a hotfix, or it can be wait until the next release of the tc-notificatons repo if this issue is not urgent.

@vikasrohit
Copy link

Okay. Lets create hotfix for it against master as well. We would merge it with Connect 2.4.15.2

@maxceem maxceem changed the title [Hotfix] [Prod] fix duplicates in emails [Hotfix] [Dev] fix duplicates in emails Oct 3, 2019
@maxceem
Copy link
Contributor Author

maxceem commented Oct 3, 2019

Here is PR against master #158

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.

2 participants