Detect Chrome phased rollouts










2















How can phased rollouts be debugged in Chrome?
Is there a screen which shows "you are in rollout group A" or B ?



Same #Chrome Version 70.0.3538.102 (Official Build) (64-Bit)
version, for me the cert does not work (first screenshot), for my colleague it still does (second screenshot).



The About Screen shows the same version.



enter image description hereenter image description here










share|improve this question




























    2















    How can phased rollouts be debugged in Chrome?
    Is there a screen which shows "you are in rollout group A" or B ?



    Same #Chrome Version 70.0.3538.102 (Official Build) (64-Bit)
    version, for me the cert does not work (first screenshot), for my colleague it still does (second screenshot).



    The About Screen shows the same version.



    enter image description hereenter image description here










    share|improve this question


























      2












      2








      2








      How can phased rollouts be debugged in Chrome?
      Is there a screen which shows "you are in rollout group A" or B ?



      Same #Chrome Version 70.0.3538.102 (Official Build) (64-Bit)
      version, for me the cert does not work (first screenshot), for my colleague it still does (second screenshot).



      The About Screen shows the same version.



      enter image description hereenter image description here










      share|improve this question
















      How can phased rollouts be debugged in Chrome?
      Is there a screen which shows "you are in rollout group A" or B ?



      Same #Chrome Version 70.0.3538.102 (Official Build) (64-Bit)
      version, for me the cert does not work (first screenshot), for my colleague it still does (second screenshot).



      The About Screen shows the same version.



      enter image description hereenter image description here







      google-chrome rollout






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 14 '18 at 16:12







      Alex

















      asked Nov 14 '18 at 16:02









      AlexAlex

      15.4k1173114




      15.4k1173114






















          1 Answer
          1






          active

          oldest

          votes


















          3














          Unfortunately, this is (intentionally) difficult.



          Since you know exactly what feature is causing trouble, you can force it with either --enable-features=LegacySymantecPKI or --disable-features=LegacySymantecPKI.



          If you want to roll the dice, that's --reset-variation-state, and you can view the current variations at chrome://version. Since the variation state only has 13 bits of entropy1, there will be a large overlap in which variations are toggled together, so you'll have a hard time determining which hashed feature in this list corresponds to LegacySymantecPKI, Disabled, and Enabled.



          There's a feature request to show the unhashed field trial names: https://crbug.com/653634.



          There's a design doc for the hashing here: https://cs.chromium.org/chromium/src/components/variations/variations_murmur_hash.h






          share|improve this answer






















            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304281%2fdetect-chrome-phased-rollouts%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            3














            Unfortunately, this is (intentionally) difficult.



            Since you know exactly what feature is causing trouble, you can force it with either --enable-features=LegacySymantecPKI or --disable-features=LegacySymantecPKI.



            If you want to roll the dice, that's --reset-variation-state, and you can view the current variations at chrome://version. Since the variation state only has 13 bits of entropy1, there will be a large overlap in which variations are toggled together, so you'll have a hard time determining which hashed feature in this list corresponds to LegacySymantecPKI, Disabled, and Enabled.



            There's a feature request to show the unhashed field trial names: https://crbug.com/653634.



            There's a design doc for the hashing here: https://cs.chromium.org/chromium/src/components/variations/variations_murmur_hash.h






            share|improve this answer



























              3














              Unfortunately, this is (intentionally) difficult.



              Since you know exactly what feature is causing trouble, you can force it with either --enable-features=LegacySymantecPKI or --disable-features=LegacySymantecPKI.



              If you want to roll the dice, that's --reset-variation-state, and you can view the current variations at chrome://version. Since the variation state only has 13 bits of entropy1, there will be a large overlap in which variations are toggled together, so you'll have a hard time determining which hashed feature in this list corresponds to LegacySymantecPKI, Disabled, and Enabled.



              There's a feature request to show the unhashed field trial names: https://crbug.com/653634.



              There's a design doc for the hashing here: https://cs.chromium.org/chromium/src/components/variations/variations_murmur_hash.h






              share|improve this answer

























                3












                3








                3







                Unfortunately, this is (intentionally) difficult.



                Since you know exactly what feature is causing trouble, you can force it with either --enable-features=LegacySymantecPKI or --disable-features=LegacySymantecPKI.



                If you want to roll the dice, that's --reset-variation-state, and you can view the current variations at chrome://version. Since the variation state only has 13 bits of entropy1, there will be a large overlap in which variations are toggled together, so you'll have a hard time determining which hashed feature in this list corresponds to LegacySymantecPKI, Disabled, and Enabled.



                There's a feature request to show the unhashed field trial names: https://crbug.com/653634.



                There's a design doc for the hashing here: https://cs.chromium.org/chromium/src/components/variations/variations_murmur_hash.h






                share|improve this answer













                Unfortunately, this is (intentionally) difficult.



                Since you know exactly what feature is causing trouble, you can force it with either --enable-features=LegacySymantecPKI or --disable-features=LegacySymantecPKI.



                If you want to roll the dice, that's --reset-variation-state, and you can view the current variations at chrome://version. Since the variation state only has 13 bits of entropy1, there will be a large overlap in which variations are toggled together, so you'll have a hard time determining which hashed feature in this list corresponds to LegacySymantecPKI, Disabled, and Enabled.



                There's a feature request to show the unhashed field trial names: https://crbug.com/653634.



                There's a design doc for the hashing here: https://cs.chromium.org/chromium/src/components/variations/variations_murmur_hash.h







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 14 '18 at 18:26









                Josh LeeJosh Lee

                120k26215243




                120k26215243





























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53304281%2fdetect-chrome-phased-rollouts%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Use pre created SQLite database for Android project in kotlin

                    Darth Vader #20

                    Ondo