Evaluate whether we could change the destruction order of the closure in the ExecutorFuture class

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Service Arch
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The goal of this ticket is to evaluate whether we could change the destruction order of the closure in the ExecutorFuture class: right now is destroyed after setting the future as ready. This has caused some issues, like this one, where the code was assuming that the objects captured by the lamda were destroyed before setting the future as ready.

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Sergi Mateo Bellido
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: