Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

:1: Error: Unexpected token ' ' found. #199

Open
sylvainbannier opened this issue Nov 25, 2016 · 1 comment
Open

:1: Error: Unexpected token ' ' found. #199

sylvainbannier opened this issue Nov 25, 2016 · 1 comment

Comments

@sylvainbannier
Copy link

I get this unclear error with the appended file

:1: Error: Unexpected token ' ' found. Expecting one of :TITLE1, :TITLE2, :TITLE3, :TITLE4, :HLINE, :HTMLBLOB, :WORD, :REF, :HREF, :INLINEFUNCSTART, :ITALIC, :BOLD, :CODE, :BOLDITALIC, :FCOLSTART, :PRE, :BULLET1, :BULLET2, :BULLET3, :BULLET4, :NUMBER1, :NUMBER2, :NUMBER3, :NUMBER4, :BLOCKFUNCSTART, :eof
<nowiki> 

Commenting (or changing) the 2 lines prefixed with /* COMMENT THESE 2 LINES TO "FIX" THE BUG */ allows me to complete the build.

Either the error message is incorrect, or this is a bug.

My planning :

project client "Site internet du client"  2016-10-19 - 2017-01-31 {
  timezone "Europe/Paris"
  timeformat "%Y-%m-%d"
  dailyworkinghours 8
  weekstartsmonday
  timingresolution 30min
  /* now 2016-10-19-00:00 */

  scenario plan "Planning actuel" {
    scenario original "Planning initial"
  }
}

leaves holiday "La Toussaint"	2016-11-01
leaves holiday "Armistice"	2016-11-11
leaves holiday "Noël"	2016-12-25
leaves holiday "Jour de l'an"	2017-01-01
leaves annual 2016-12-26 - 2017-01-02

flags meeting, delivery, training, input, delayed

### COMPTES

account cost "Charges"
account rev "Facturations"
balance cost rev

### RESSOURCES

resource "MOE"{
  resource r_cp "r_cp" {
    leaves annual 2016-10-31
    leaves annual 2016-11-2
    leaves annual 2016-12-26 - 2017-01-02
    leaves project 2016-11-14

    workinghours mon 9:00 - 13:00
    workinghours tue 9:00 - 13:00
    workinghours wed 9:00 - 13:00
    workinghours thu 9:00 - 13:00
    workinghours fri 9:00 - 13:00
  }
  resource r_dev "Développeurs" {
    resource r_dev_css   " Développeur CSS   " {
    }
    resource r_dev_jahia " Développeur Jahia " {
    }
  }
  resource r_dp        " r_dp " { rate 0 efficiency 0 }
  resource r_ia        " r_ia " { rate 0 efficiency 0 }
  resource r_expert    " r_expert " { rate 0 }
  resource r_da  " r_da " {
    efficiency 0
  }
}
resource "MOA" {
  efficiency 0
  resource r_pcp "Pierre cp" {
    leaves annual 2016-10-31
    leaves annual 2016-11-10 - 2016-11-15
    leaves annual 2016-11-21
    leaves annual 2016-12-2
    leaves annual 2016-12-23 - 2017-01-02
  }
  resource r_lcom " Lynda com  "
  resource r_jspo  " Jeremie spo "
}

## MACROS

macro m_t_input [
  milestone
  flags input
]

macro m_t_delivery [
  milestone
  flags delivery
]


## PROJET

task project "client" {
  chargeset cost

  task milestones "Jalons" {
    task start "lancement" {
      start ${projectstart}
    }

    task ouverture "ouverture du musée" {
      depends !!ship
      end 2017-01-27
      milestone
    }
  }

  task contrat "contractualisation" {
    task proposition "proposition" {
      milestone
      start 2016-11-15
      original:start 2016-11-10
      flags delivery
      allocate r_ia
      journalentry 2016-11-15 "proposition en retard" {
        author r_cp
        alert yellow
        summary -8<-
          chiffrage en retard
        ->8-
        details -8<-
        ->8-
      }
      journalentry 2016-11-15 "périmètre du projet à confirmer" {
        author r_cp
        alert red
        summary -8<-
          le planning et le budget ne permettent pas de réaliser tout ce qui avait été envisagé
        ->8-
        details -8<-
          il est nécessaire de statuer sur le périmètre final
        ->8-
      }
      journalentry 2016-11-21 "Livraison du devis" {
        author r_ia
        alert green
        summary -8<-
          Devis livré
        ->8-
      }
    }
    task validation "validation" {
      flags input
      milestone
      start 2016-11-15
      depends !proposition
    }
  }

  task design "conception" {
    priority 900

    task graphic "graphisme" {
      task milestones "Jalons" {
        task deliveries "livraisons" {
          flags delivery

          task d1 "livraison initiale" {
            milestone
            end 2016-11-02
          }

          task d2 "2ème livraison" {
            milestone
            depends !!!graphic.home_desktop.ite2
            depends !!!graphic.home_mobile.ite1
            precedes !!!workshops.w2 {gaplength 1d}
            /* original:precedes !!!workshops.w2 {gaplength 2d} */
          }

          task d3 "3ème livraison" {
            milestone
            /* COMMENT THESE 2 LINES TO "FIX" THE BUG */
            depends !!!graphic.home_mobile.ite2
            depends !!!graphic.home_desktop.ite3
          }

          task d4 "livraison finale" {
            milestone
            depends !!!graphic.home_mobile
            depends !!!graphic.home_desktop
          }
        }

        task inputs "pré-requis" {
          flags input
          task nv1 "pistes agence" {
            milestone
            end 2016-10-21
          }
          task nv2 "police et logo agence" {
            milestone
            end 2016-11-22
            original:end 2016-11-09

            journalentry 2016-11-15 "retours de agence manquants" {
              author r_cp
              alert red
              summary -8<-
                non livré
              ->8-
              details -8<-
                risque de décaler la conception.
                Que fait-on pour ne pas être bloqués ?
              ->8-
            }
            journalentry 2016-11-23 "retour logo + gamme chromatique" {
              alert green
              summary -8<-

              ->8-
              details -8<-

              ->8-
            }
          }
          task rfc1 "Commentaires sur home desktop" {
            milestone
            end 2016-11-09
          }
          task rfc2 "Commentaires sur home desktop(2) et mobile" {
            milestone
            depends !!!workshops.w2
          }
          task rfc3 "Commentaires sur 2ème version home desktop et mobile" {
            milestone
            depends !!!reviews.ite3
          }
          task v1 "validation finale" {
            milestone
            depends !!!reviews.ite4
          }
        }
      }

      task workshops "Réunions" {
        priority 1000
        allocate r_cp {mandatory}, r_pcp {mandatory}, r_da {mandatory}
        task w1 "brief initial" {
          flags meeting
          length 3h
          start 2016-10-21-10:00
        }

        task w2 "atelier retours home desktop(2) et mobile" {
          flags meeting
          allocate r_lcom {mandatory}
          length 3h
          start 2016-11-16-10:00
        }
      }

      task reviews "Relecture" {
        priority 900
        allocate r_pcp {mandatory}, r_lcom {mandatory}
        limits { dailymax 1h {resources r_pcp, r_lcom} }

        task ite1 "1ère itération" {
          depends !!milestones.deliveries.d1
          length 2d
        }

        task ite2 "2ème itération" {
          depends !!milestones.deliveries.d2
          length 1d
          original:length 2d
        }

        task ite3 "3ème itération" {
          depends !!milestones.deliveries.d3
          length 4d
          original:length 2d
        }

        task ite4 "4ème itération" {
          /* tâche absente initialement */
          /* depends !!milestones.deliveries.d4 */
          length 1d
        }
      }


      task graphic "Conception" {
        allocate r_da

        journalentry 2016-11-15 "Retard sur la livraison home mobile et 2ème itération desktop" {
          author r_cp
          alert yellow
          summary -8<-
            absence de retours de agence en cause
            doit-on adapter le planning de validation pour en tenir compte ?
          ->8-
        }

        journalentry 2016-11-15 "remarques sur l'accessibilité des couleurs non prises en compte" {
          author r_da
          alert yellow
          summary -8<-
            Faute de retour de agence sur les couleurs il n'était pas possible de traiter les demandes de corrections sur l'accessibilité des couleurs
          ->8-
        }

        journalentry 2016-11-15 "Consommation du budget DA" {
          author r_cp
          alert yellow
          summary -8<-
            le budget de DA est consommé
          ->8-
          details -8<-
            nous manquerons de budget pour travailler à l'adaptation des composants
          ->8-
        }
        /* journalentry 2016-11-16 "peu de retour sur le design" { */
        /*   author r_cp */
        /*   alert green */
        /*   summary -8<- */
        /*     peu de retours sur le design => levée du risque sur la consommation du budget DA */
        /*   ->8- */
        /* } */

        task home_desktop "maquette accueil desktop" {
          task ite1 "1ère itération" {
            depends !!!milestones.inputs.nv1
            precedes !!!milestones.deliveries.d1
            limits { dailymax 2h }
          }

          task ite2 "2ème itération" {
            length 3d
            original:length 2d
            original:depends !!!milestones.inputs.nv2
            depends !!!milestones.inputs.rfc1
            limits { dailymax 2h }
          }

          task ite3 "3ème itération" {
            length 2d
            depends !!!milestones.inputs.rfc2
            limits { dailymax 2h }
          }

          task ite4 "4ème itération" {
            /* tâche absente initialement */
            length 2d
            depends !!!milestones.inputs.rfc3
            limits { dailymax 2h }
          }
        }

        task home_mobile "maquette accueil mobile" {
          task ite1 "1ère itération" {
            depends !!!milestones.inputs.rfc1
            length 3d
            original:length 2d
            limits { dailymax 2h }
          }
          task ite2 "2ème itération" {
            depends !!!milestones.inputs.rfc2
            length 2d
            limits { dailymax 2h }
          }
          task ite3 "3ème itération" {
            depends !!!milestones.inputs.rfc3
            length 2d
            limits { dailymax 2h }
          }
        }
      }
    }

    task spec "Spécifications fonctionnelles" {
      priority 900
      depends !!contrat
      depends !graphic.workshops.w2

      task milestones "Jalons" {
        task "démarrage" {
          precedes !!workshop
          milestone
        }
        task "livraison" { ${m_t_delivery}
          depends !!write
        }
        task "livraison des retours" {
          milestone
          flags input
          depends !!review
        }
        task "livraison version finale" { ${m_t_delivery}
          depends !!write2
        }
        task "validation finale" {
          milestone
          flags input
          depends !!review2
        }
      }
      task workshop "atelier" {
        allocate r_dev_jahia {mandatory}, r_cp {mandatory}, r_pcp {mandatory}
        start 2016-11-18-9:30
        limits {dailymax 3h {resources r_dev_jahia, r_cp, r_pcp } }
        length 3h
        flags meeting
      }

      task write "rédaction" {
        depends !workshop
        allocate r_cp
        effort 2d
        journalentry 2016-11-23 "livraison specicifications blog" {
          alert green
        }
      }
      task review "relecture" {
        depends !write
        allocate r_pcp
        length 2d
        limits {dailymax 1h}
      }
      task write2 "corrections" {
        depends !review
        allocate r_cp
        effort 0.5d
      }
      task review2 "relecture" {
        depends !write2
        allocate r_pcp
        length 1d
        limits {dailymax 1h}
      }
    }
  }

  task impl "implémentation" {
    depends !design
    task dev "développement" {
      task "CSS" {
        allocate r_dev_css
        effort 14.5d
        limits {weeklymax 4.5d}
      }
      task "jahia" {
        allocate r_dev_jahia
        limits {dailymax 4h}
        effort 9d
      }
    }
    task qa "test" {
      depends !dev
      allocate r_cp, r_dev_jahia, r_dev_css
      length 5d
      limits {
        maximum 2d { resources r_cp, r_dev_css}
        maximum 1d { resources r_dev_jahia }
      }
    }
    task "livraison pour recette" {${m_t_delivery}
      depends !qa
    }
  }

  task training "formation" {
    task training_prepare "préparation de la formation" {
      priority 900
      length 1d
      allocate r_dev_jahia
      depends !!impl.dev
    }

    task training "formation" {
      depends !!impl
      priority 900
      length 1d
      allocate r_dev_jahia {mandatory}, r_pcp {mandatory}
      flags training
    }
  }

  task review "recette" {
    depends !training
    task review "retours de recette" {
      length 5d
      allocate r_pcp
      limits {dailymax 2h}
    }

    task fix "corrections" {
      depends !review
      allocate r_cp, r_dev_jahia, r_dev_css
      limits {
        maximum 2d { resources r_cp, r_dev_css}
        maximum 1d { resources r_dev_jahia }
      }
      length 5d
    }

    task "validation finale" {${m_t_input}
      depends !fix
    }
  }

  task contrib "contribution" {
    priority 900
    depends !training
    end ${projectend}
    allocate r_pcp
    limits {dailymax 2h}
  }

  task ship "mise en production" {
    priority 1000
    effort 1d
    allocate r_dev_jahia
    depends !review
  }

  task release "ouverture du site internet" {${m_t_input}
    depends !ship
    note "branchement du nom de domaine"
  }

  task management "gestion de projet" {
    task "comité de projet" {
      priority 1000
      allocate r_cp {mandatory}, r_pcp {mandatory}
      limits { weeklymax 1h }
      start 2016-11-15
      end ${projectend}
    }
    task "suivi et préparations" {
      journalentry 2016-11-15 "Suivi de projet faible" {
        author r_cp
        alert green
        summary -8<-
          la charge de suivi de projet et de préparation des réunions est plutôt faible (2h/semaine)
        ->8-
        details -8<-
          risque sur le cardrage des développements ou sur le coût de production
          vu en comité de suivi : prise en compte du faible budget.
          OK pour formalisme minimaliste
        ->8-
      }
      allocate r_cp
      limits {weeklymax 2h}
      start ${projectstart}
      end ${projectend}
    }
    task "comités de suivi" {
      allocate r_cp {mandatory},r_pcp {mandatory},  r_lcom {mandatory}, r_jspo {mandatory}, r_ia {mandatory}, r_dp {mandatory}
      priority 1000
      task "1er comité de suivi" {
        flags meeting
        start 2016-11-15-16:00
        length 2h
      }
      task "2ème comité de suivi" {
        flags meeting
        start 2016-12-14-10:00
        length 2h
      }
      task "3ème comité de suivi" {
        flags meeting
        start 2017-01-11-10:00
        length 2h
      }
    }
  }

}

navigator navbar {
  hidereport 0
}

## MACROS RAPPORTS

macro m_package_report [
textreport "${2}" {
  formats html
  center '<[report id="${1}"]>'
  purge title
}
]

macro m_resource_dashboard [
textreport "${2}" {
  formats html
  center -8<-
    <[report id="tasks_${1}"]>
    ----
    <[report id="charges_${1}"]>
  ->8-

  purge title
}
]

macro cellcolor [
cellcolor (input) "#D5B046"
cellcolor (delivery) "#E46BA3"
cellcolor (meeting) "#6BE4C0"
]

macro datecellcolor [
cellcolor (delayed) "#FF0000"
]

macro m_r_subtask [
taskreport ${1} "${1}" {
  columns bsi { title 'ordre' }, name {width 300 title "tâche" ${cellcolor} }, start {title "début" ${datecellcolor}}, end { title "fin" ${datecellcolor} }, effort { title "Jour/Homme" }, duration {title "durée"}, chart {  scale day width 500 }

  timeformat "%Y-%m-%d"
  hideresource ~(isleaf() & isleaf_())
  sortresources name.up
  formats html
  taskroot ${2}
  /* hidetask treelevel()>${3} */
  loadunit days
}
]

macro m_r_subtask_for [
taskreport ${1} "${1}" {
  columns bsi { title 'ordre' }, name {width 300 title "tâche" ${cellcolor} }, start {title "démarrage" }, end { title "fin le / attendu le" }, daily {}

  timeformat "%Y-%m-%d"
  hideresource ~(isleaf() & isleaf_())
  sortresources name.up
  formats html
  taskroot ${2}
  hidetask ~((isdutyof(${3},plan) | input | delivery) & ~(plan.end < ${now}))
  loadunit days
}
]

macro m_r_tasks_for_resource [
taskreport tasks_${1} "tasks_${1}" {
  columns bsi { title 'ordre' }, name {width 300 title "tâche" ${cellcolor} }, start {title "démarrage" }, end { title "fin le / attendu le" }, daily {}

  timeformat "%Y-%m-%d"
  hideresource ~(isleaf() & isleaf_())
  sortresources name.up
  formats html
  hidetask ~((isdutyof(${1},plan)) & ~(plan.end < ${now}))
  loadunit days
}
]

macro m_r_charges_for_resource [
resourcereport charges_${1} "charges_${1}" {
  columns no, name {title "nom"}, effort {title "nombre de jours"}, weekly {  }
  loadunit days
  # We only like to show leaf tasks for leaf resources.
  sorttasks plan.start.up
  hideresource ~(plan.id = "${1}")
  hidetask ~(isleaf() & isleaf_())
}
]
#"

${m_r_subtask "contrat" "project.contrat"}
${m_r_subtask "conception" "project.design"}
${m_r_subtask "specs" "project.design.spec"}
${m_r_subtask "graphic" "project.design.graphic"}
${m_r_subtask "impl" "project.impl"}
${m_r_subtask "review" "project.review"}

textreport frame "" {
  header -8<-
    == client ==
    <[navigator id="navbar"]>
  ->8-
  footer "----"
  textreport index "index" {
    formats html
    title "Vue d'ensemble"
    center '<[report id="overview"]>'
  }

  textreport "status" {
    title "Avancement"
    formats html
    center -8<-
      <[report id="status.dashboard"]>
      ----
      <[report id="status.completed"]>
      ----
      <[report id="status.ongoing"]>
      ----
      <[report id="status.future"]>
    ->8-
  }

  textreport wps "phases" {
    title "Phases"
    ${m_package_report "contrat" "Contractualisation"}
    textreport "design" {
      title "Conception"
      ${m_package_report "conception" "Vue d'ensemble"}
      ${m_package_report "specs" "Conception fonctionnelle"}
      ${m_package_report "graphic" "Conception graphique"}
    }
    ${m_package_report "impl" "Implémentation"}
    ${m_package_report "review" "Recette"}
  }

  textreport "milestones" {
    title "Jalons"
    formats html
    center '<[report id="milestones"]>'
  }

  textreport "ContactList" {
    title "Contacts et disponibilités"
    formats html
    center '<[report id="contactList"]>'
  }
  textreport "ResourceGraph" {
    formats html
    title "Plan de charge"
    ${m_package_report "charge_general" "Plan de charge général"}
    textreport "moe" {
      title "MOE"
      ${m_resource_dashboard "r_dev_jahia" "Développeur Jahia"}
      ${m_resource_dashboard "r_dev_css" "Développeur CSS"}
      ${m_resource_dashboard "r_cp" "Chef de projet"}
    }
    textreport "moa" {
      title "MOA"
      ${m_resource_dashboard "r_pcp" "Pierre cp"}
      ${m_resource_dashboard "r_jspo" "Jérémie spo"}
      ${m_resource_dashboard "r_lcom" "Lynda com"}
    }
  }

  /* textreport "complet" { */
  /*   formats html */
  /*   title "Complet" */
  /*   center '<[report id="full"]>' */
  /* } */

  textreport "meetings" {
    formats html
    title "Réunions"
    center '<[report id="meetings"]>'
  }
}

# A traditional Gantt chart with a project overview.
taskreport overview "" {
  columns bsi { title 'WBS' },
          name {title "phase" width 200}, start {title "début"}, end {title "fin"}, duration {title "durée (jours)"}, chart { scale week }
          ,effort {title "jours/homme"}
          /* ,cost {title "coût"}, revenue {title "facturation"}  */
  timeformat "%d/%m"
  /* loadunit shortauto */
  loadunit days
  hideresource 1
  balance cost rev
  sorttasks tree.up
  caption 'les efforts sont en jours/homme'
  hidetask (treelevel() > 2) | (plan.id = "project.milestones") | (plan.id = "project.management")
}

taskreport full "" {
  columns bsi { title 'WBS' },
          name {title "tâche" width 300}, start {title "début"}, end {title "fin"}, effort {title "jour/homme"}, duration { title "durée" }, cost {title "coût"},
          revenue {title "facturation"}
  timeformat "%d/%m"
  /* loadunit days */
  balance cost rev
  hideresource ~(isleaf() & isleaf_())
  sortresources name.up
  numberformat "-" "" " " "," 2
  loadunit shortauto
  /* hidetask (treelevel() > 2) */
}

# Macro to set the background color of a cell according to the alert
# level of the task.
macro AlertColor [
  cellcolor plan.alert = 0 "#00D000" # green
  cellcolor plan.alert = 1 "#D0D000" # yellow
  cellcolor plan.alert = 2 "#D00000" # red
]

taskreport status "" {
  columns bsi { width 50 title 'WBS' }, name { width 150 },
          start { width 100 }, end { width 100 },
          effort { width 100 },
          alert { tooltip plan.journal
                          != '' "<-query attribute='journal'->" width 150 },
          status { width 150 }

  taskreport dashboard "" {
    headline "Alertes et actions (<-query attribute='now'->)"
    columns name { title "tâche" ${AlertColor} width 200},
            /* resources { width 200 ${AlertColor} */
            /*             listtype bullets */
            /*             listitem "<-query attribute='name'->" */
            /*             start ${projectstart} end ${projectend} }, */
            alerttrend { title "tendance" ${AlertColor} width 80 },
            journal { width 550 ${AlertColor} }
    journalmode status_up
    journalattributes headline, author, date, summary, details
    hidetask ~hasalert(0)
    sorttasks alert.down, plan.end.up
    period %{${now} - 1w} +1w
  }
  taskreport completed "" {
    headline "Tâches terminées"
    hidetask ~(plan.end <= ${now}) & (plan.end >= %{${now} - 1w})
  }
  taskreport ongoing "" {
    columns name { width 150 title "tâche" },
            end { width 100 title "fin" },
            resources,
            alert { title "risque" tooltip plan.journal
                            != '' "<-query attribute='journal'->" width 150 },
            status { width 150 }

    /* sorttasks end.up */
    headline "Tâches en cours"
    hidetask ~((plan.start <= ${now}) & (plan.end > ${now})) | (ismilestone(plan)) | ~(isleaf()) | (meeting) | (ischildof(project.management))
  }
  taskreport future "" {
    headline "Tâches des 2 semaines à venir"
    hidetask ~((plan.start > ${now}) & (plan.start < %{${now} + 2w}))
  }
}


${m_r_tasks_for_resource "r_dev_jahia" }
${m_r_tasks_for_resource "r_dev_css" }
${m_r_tasks_for_resource "r_cp" }
${m_r_tasks_for_resource "r_pcp" }
${m_r_tasks_for_resource "r_jspo" }
${m_r_tasks_for_resource "r_lcom" }
${m_r_charges_for_resource "r_dev_jahia" }
${m_r_charges_for_resource "r_dev_css" }
${m_r_charges_for_resource "r_cp" }
${m_r_charges_for_resource "r_pcp" }
${m_r_charges_for_resource "r_jspo" }
${m_r_charges_for_resource "r_lcom" }


# A graph showing resource allocation. It identifies whether each
# resource is under- or over-allocated for.
resourcereport charge_general "charge_general" {
  headline "Plan de charge général"
  columns no, name {title "nom"}, effort {title "nombre de jours"}, rate {title "prix jour"}, weekly {  }
  loadunit days
  # We only like to show leaf tasks for leaf resources.
  hidetask ~(isleaf() & isleaf_())
  sorttasks plan.start.up
}


# A list of all tasks with the percentage completed for each task
taskreport milestones "" {
  headline "Jalons"
  /* scenarios plan, original */
  columns name, start { ${datecellcolor} }, chart

  /* taskroot project.deliveries */
  hideresource 1
  hidetask ~(delivery) & ~(input)
  /* sorttasks start.up */
}
# A list of all employees with their contact details.
resourcereport contactList "" {
  headline "Contacts et disponibilités"
  columns name,
          chart { scale day }
  hideresource ~isleaf()
  sortresources name.up
  hidetask 1
}

taskreport meetings "" {
  columns name {width 300 title "tâche"}, start {title "date"}
  sorttasks start.up
  hidetask ~(meeting)
  loadunit hours
  timeformat "%a %Y-%m-%d %k:%M"
}
@manad93
Copy link

manad93 commented Jan 5, 2022

As of now (5.1.2022), this bug still persists (taskjuggler 3.7.1, ruby 2.7.5p203 (2021-11-24 revision f69aeb8314) [x86_64-linux] , Windows Subsystem Linux 2 with Ubuntu 18.04 distro) - deleting one problamatic task dependency "solve" it.
Thanks @sylvainbannier for reporting it, it helps me a lot!

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

No branches or pull requests

2 participants