Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #19
Closed
Open
Issue created Sep 02, 2014 by Tiago de Freitas Pereira@tiago.pereiraMaintainer2 of 2 checklist items completed2/2 checklist items

The toolchain editor generates invalid toolchains

  • Let say that you have 3 blocks A, B and C. The block A is a dataset block and the blocks B and C are regular blocks. When you create a connection between blocks A and B, the connection uses the synchronization channel from A. Right after that, when you try to create a connection between the blocks A and C (using the same field on the "A" side), the synchronization channel is null, which invalidates the toolchain. Additionally, it is not possible to fix it.

  • In the same example as above (blocks A,B and C), when you create a connection between the blocks A and B, it is not possible to create a connection between A and C (using the same field in the "A" side). The only possible way is to create a connection between C and A. I know this is the same thing, but it is not intuitive.

Assignee
Assign to
Time tracking