Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: B35
    • Fix Version/s: B38
    • Component/s: doc
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: All

    • Issuezilla Id:
      1,729

      Description

      Consider modifying the send-uuid workaround logic to account for those cases
      where a user may intentionally set the send-uuid flag to false. When a user
      does this, the notifier might end up overriding the user's preferred setting.

        Activity

        Hide
        Chris Kasso added a comment -

        I am assuming that in 2.4 the notifier send-uuid workaround logic will be removed.

        For 2.3 we can introduce a new, global UC property:

        [notifier]
        _enabled_send_uuid_check = True

        This property will control whether the notifier will perform the send-uuid
        workaround. If the property if False or absent the notifier will not perform
        the workaround.

        In 2.4 we can either:

        1) Automatically have this property removed when any of the UC clients are run.

        or

        2) Have it removed the first time the user manually changes the send-uuid
        setting via the send-uuid checkbox on Authority Properties (issue 1730).

        It really depends on how aggressive we want to be about turning off the workaround.

        Show
        Chris Kasso added a comment - I am assuming that in 2.4 the notifier send-uuid workaround logic will be removed. For 2.3 we can introduce a new, global UC property: [notifier] _enabled_send_uuid_check = True This property will control whether the notifier will perform the send-uuid workaround. If the property if False or absent the notifier will not perform the workaround. In 2.4 we can either: 1) Automatically have this property removed when any of the UC clients are run. or 2) Have it removed the first time the user manually changes the send-uuid setting via the send-uuid checkbox on Authority Properties (issue 1730). It really depends on how aggressive we want to be about turning off the workaround.
        Hide
        Chris Kasso added a comment -

        New property enabled_send_uuid_check -> enable_send_uuid_check

        Show
        Chris Kasso added a comment - New property enabled_send_uuid_check -> enable_send_uuid_check
        Hide
        Chris Kasso added a comment -

        Refining my thinking on this a bit:

        For a 2.3 client the absence of the _enable_send_uuid_check option would
        indicate that it should be added to defaults.cfg and set to True.

        For a 2.3 client the presence of the _enable_send_uuid_check would control
        whether the send-uuid workaround would be enabled.

        For a 2.4 client we may choose to:

        1) Always set the _enable_send_uuid_check to False to stop any 2.3 clients from
        performing the send-uuid check.

        2) Only set _enable_send_uuid_check to False when the user modifies the
        send-uuid checkbox on the Authority Properties.

        Show
        Chris Kasso added a comment - Refining my thinking on this a bit: For a 2.3 client the absence of the _enable_send_uuid_check option would indicate that it should be added to defaults.cfg and set to True. For a 2.3 client the presence of the _enable_send_uuid_check would control whether the send-uuid workaround would be enabled. For a 2.4 client we may choose to: 1) Always set the _enable_send_uuid_check to False to stop any 2.3 clients from performing the send-uuid check. 2) Only set _enable_send_uuid_check to False when the user modifies the send-uuid checkbox on the Authority Properties.
        Hide
        Chris Kasso added a comment -

        I don't think we need to make any code changes. The existing workaround is
        only enabled if optin.usage.reporting is True.

        In the short term we could RN the need for a user who manually changes the
        send-uuid flag to False that they must also set the optin.usage.reporting to
        False as well. This will prevent the workaround from resetting the send-uuid flag.

        In 2.4/3.0 we can remove the workaround from the notifier and if we want to be
        real aggressive we can force optin.usage.reporting to false to turn off this
        workaround in the older code in case the notifier is not upgraded to the latest
        version.

        I'm going to reassign this issue to Mike and we can discuss whether a RN item is
        necessary.

        Show
        Chris Kasso added a comment - I don't think we need to make any code changes. The existing workaround is only enabled if optin.usage.reporting is True. In the short term we could RN the need for a user who manually changes the send-uuid flag to False that they must also set the optin.usage.reporting to False as well. This will prevent the workaround from resetting the send-uuid flag. In 2.4/3.0 we can remove the workaround from the notifier and if we want to be real aggressive we can force optin.usage.reporting to false to turn off this workaround in the older code in case the notifier is not upgraded to the latest version. I'm going to reassign this issue to Mike and we can discuss whether a RN item is necessary.
        Hide
        Mike Fitch added a comment -

        After talking with Chris, I updated the Usage Metrics page on the the wiki
        (http://wiki.updatecenter.java.net/Wiki.jsp?page=UsageMetricsUC2) instead of
        putting in a Release Notes item.

        Show
        Mike Fitch added a comment - After talking with Chris, I updated the Usage Metrics page on the the wiki ( http://wiki.updatecenter.java.net/Wiki.jsp?page=UsageMetricsUC2 ) instead of putting in a Release Notes item.

          People

          • Assignee:
            Mike Fitch
            Reporter:
            ckamps
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: