Skip to content
PR Checks to confuse and delight

fix(dal): The order in which we process dependencies between components is inconsistent, so we must always check if the component is in the dependency graph before adding it as Petgraph doesn't prevent nodes with duplicate node weights from being inserted #3144

Sign in to view logs

fix(dal): The order in which we process dependencies between components is inconsistent, so we must always check if the component is in the dependency graph before adding it as Petgraph doesn't prevent nodes with duplicate node weights from being inserted

fix(dal): The order in which we process dependencies between components is inconsistent, so we must always check if the component is in the dependency graph before adding it as Petgraph doesn't prevent nodes with duplicate node weights from being inserted #3144

Workflow file for this run

.github/workflows/pr.yml at aebbf29
# This is essentially a dummy to allow us to set
# buildkite/si-merge-queue as a status check. This
# is run during a PR, but the Buildkite check is run
# in the merge queue
name: PR Checks to confuse and delight
on:
pull_request:
jobs:
si-merge-queue:
name: buildkite/si-merge-queue
runs-on: ubuntu-latest
steps:
- run: echo "Success!"