Implement move constructor for ReplicationStateTransitionGuard instead of default one

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • ALL
    • Repl 2025-05-12
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Default move c'tors on certain platforms seem to keep source field of type std::function<> rather than set them to nullptr. That results double call of release callback during destruction(in move_to and move_frome objects). Based on c++ spec move c'tor for std::function keeps source object in valid but unspecified state.

            Assignee:
            Solomon Lifshits (Inactive)
            Reporter:
            Solomon Lifshits (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: