Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

syncing site settings exception #8241

Closed
diracdeltas opened this issue Apr 11, 2017 · 3 comments · Fixed by #8242
Closed

syncing site settings exception #8241

diracdeltas opened this issue Apr 11, 2017 · 3 comments · Fixed by #8242

Comments

@diracdeltas
Copy link
Member

diracdeltas commented Apr 11, 2017

Test plan

  1. 'Syncing' tests should pass
  2. Set isProduction to true in js/constants/appConfig
  3. Sync to the profile starting with "duality" (sent via slack DM)
  4. You should not see any console errors
  5. Go http://expectnothing.com/ and verify that shields are down

Original issue description

syncing to serg's profile on the production sync server throws this error:

An uncaught exception occurred in the main process Uncaught Exception:
TypeError: Cannot read property '1' of undefined
    at applySiteSettingRecord (/Users/yan/repos/browser-laptop/js/state/syncUtil.js:156:48)
    at applySyncRecord (/Users/yan/repos/browser-laptop/js/state/syncUtil.js:201:7)
    at Immediate.setImmediate (/Users/yan/repos/browser-laptop/js/state/syncUtil.js:180:5)
    at runCallback (timers.js:651:20)
    at tryOnImmediate (timers.js:624:5)
    at processImmediate [as _immediateCallback] (timers.js:596:5)
@diracdeltas diracdeltas added this to the 0.14.2 milestone Apr 11, 2017
@diracdeltas diracdeltas self-assigned this Apr 11, 2017
diracdeltas added a commit that referenced this issue Apr 12, 2017
fix #8241

applySiteSettingRecord should not need to check if there is a diff between
the existing record and the new record; this is the job of reducers.

Auditors: @ayumi

Test Plan:
1. 'Syncing' tests should pass
2. Set isProduction to true in js/constants/appConfig
3. Sync to the profile starting with "duality" (sent via slack DM)
4. You should not see any console errors
5. Go http://expectnothing.com/ and verify that shields are down
bsclifton pushed a commit that referenced this issue Apr 12, 2017
fix #8241

applySiteSettingRecord should not need to check if there is a diff between
the existing record and the new record; this is the job of reducers.

Auditors: @ayumi

Test Plan:
1. 'Syncing' tests should pass
2. Set isProduction to true in js/constants/appConfig
3. Sync to the profile starting with "duality" (sent via slack DM)
4. You should not see any console errors
5. Go http://expectnothing.com/ and verify that shields are down
@cezaraugusto
Copy link
Contributor

@diracdeltas is there a member-only area where I could get this profile?

@alexwykoff
Copy link
Contributor

While trying this test I found that about:preferences#security per site settings (like fullscreen for youtube) would not sync, but about:preferences#shields would sync.

So while there is no exception, it's unclear if the issue is fully resolved.

@diracdeltas
Copy link
Member Author

it's just for shields

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

Successfully merging a pull request may close this issue.

5 participants