Skip to content
This repository was archived by the owner on Sep 6, 2021. It is now read-only.

creating a new function that checks for uuid/olderUuid, if they are null they are populated and set in PreferencesManager#14374

Open
SnchitGrover wants to merge 5 commits intoadobe:masterfrom
SnchitGrover:snchit_fix_for_uuid_ingest
Open

creating a new function that checks for uuid/olderUuid, if they are null they are populated and set in PreferencesManager#14374
SnchitGrover wants to merge 5 commits intoadobe:masterfrom
SnchitGrover:snchit_fix_for_uuid_ingest

Conversation

@SnchitGrover
Copy link
Copy Markdown
Contributor

@SnchitGrover SnchitGrover commented May 30, 2018

…ull they are populated and set in PreferencesManager
@vickramdhawal vickramdhawal self-requested a review May 30, 2018 10:14
@vickramdhawal
Copy link
Copy Markdown
Collaborator

@niteskum Can you take a look at these changes ?

userGuids.userUuid = userUuid;
userGuids.olderUuid = olderUuid;

return result.resolve(userGuids);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think you should be returning result.resolve(userGuids).promise().


PreferencesManager.setViewState("UUID", userGuids.uuid);
PreferencesManager.setViewState("OlderUUID", userGuids.olderuuid);
return result.resolve(userGuids);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I think you should be returning result.resolve(userGuids).promise().

if (userUuid && olderUuid) {
oneTimeHealthData.uuid = userUuid;
oneTimeHealthData.olderuuid = olderUuid;
return result.resolve(oneTimeHealthData);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

you can remove the return here and just have result.resolve()


userGuids.uuid = userUuid;
userGuids.olderuuid = olderUuid;
return result.resolve(userGuids);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

you can remove the return here and just have result.resolve()

}
};

return result.resolve(ingestData);
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

you can remove the return here and just have result.resolve()

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I dont see a need for a return here.

}
}
});
return result.resolve();
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

what is this dialog for ? Should the result be resolved once the dialog is shown ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

dialog is to display the healthData json and adobe analytics json.
result should be resolved when dialog is displayed.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

then should we not move it inside the function ?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

or maybe we can add an always() and resolve it there.

@abose
Copy link
Copy Markdown
Contributor

abose commented Jun 2, 2018

@SnchitGrover there are quite a lot of redundant commits. can you squash some of them appropriately?


// So we are going to get the Machine hash in either of the cases.
if (appshell.app.getMachineHash) {
appshell.app.getMachineHash(function (err, macHash) {
Copy link
Copy Markdown
Contributor

@abose abose Jun 2, 2018

Choose a reason for hiding this comment

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

This looks like machine fingerprinting in health reports. Why is this change made? This looks like it might affect the 'anonymous' part of our health data metrics. UUIDs were deliberately made random to prevent traceability.
@petetnt @swmitra

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

@abose This functionality was already baked into brackets. I just moved it to a function so that can be called from multiple places.

Copy link
Copy Markdown
Contributor

@abose abose Jun 2, 2018

Choose a reason for hiding this comment

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

ah! got it. It just occurred to me that this is machine fingerprinting then. That is not a recommended practice for anonymous logging services. But the legality of that in desktop software might be different to that of hosted services. I think we should consider just using the randomly generated UUID[generated on the first launch as is the current behavior] here instead of hardwareID hashes that can uniquely identify a machine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants