Gary Casey comments

Results 395 comments of


                                            Gary Casey

Pad block errors on initial notifications

Oh ok I thought you were proposing something new. (Can't read diagram on my phone!) Yes that's what Jagan & I were discussing; we have two ways of doing it...

Can't onboard with existing atsign in buzz

1. Are the old ways of things marked as deprecated? 2. If we are maintaining the "old ways", then their implementation needs to be changed so that internally they use...

Notifications being marked as delivered but client app does not see them

It is likely that #617 would have then (in some cases) further compounded the flakiness by triggering #621

MASTER TICKET : GCP/Travelers - Atsign on Marketplace

Placeholder. Will be updated as we get more clarity about what we want to do

Failed to get shared key while encrypting / decrypting message

@sachins-geekyants can you confirm this has been fixed?

Option to delete notifications

This is more a question for Kevin / Colin as it is a prioritization call

Synchronisation error

Thanks @ralfeus - an unexpected consequence of some fairly recent changes. We'll fix the bug and add some tests to cover this scenario.

Synchronisation error - Invalid or corrupted pad block

Thanks @kalluriramkumar ... did you look into why the error message says `Failed to decrypt @baboon9blue:@baboon9blue:shared_key@81bored7@81bored7` instead of `Failed to decrypt @baboon9blue:shared_key@81bored7` ?

Synchronisation error - Invalid or corrupted pad block

Great - have you created a ticket to track fixing that bug?