test pr

.buildkite/hooks/post-checkout

@@ -8,14 +8,17 @@ source ci/env.sh
 # previous CI job
 #
 (
-  containers=$(docker ps -q)
-  if [[ $(hostname) != metrics-solana-com && -n $containers ]]; then
-    echo "+++ Killing stale docker containers"
-    docker ps
+  echo "+++ Killing stale docker containers"
+  while read -r line; do
+    read -r id image _ <<<"$line"
 
-    # shellcheck disable=SC2086 # Don't want to double quote $containers
-    docker kill $containers
-  fi
+    if [[ $image =~ "solanalabs/rust" ]]; then
+      if docker kill "$id" >/dev/null; then
+        echo "kill $id $image"
+      fi
+      continue
+    fi
+  done < <(docker ps | tail -n +2)
 )
 
 # Processes from previously aborted CI jobs seem to loiter, unclear why as one
@@ -37,6 +40,6 @@ source ci/env.sh
 # HACK: These are in our docker images, need to be removed from CARGO_HOME
 #  because we try to cache downloads across builds with CARGO_HOME
 # cargo lacks a facility for "system" tooling, always tries CARGO_HOME first
-cargo uninstall cargo-audit || true
-cargo uninstall svgbob_cli || true
-cargo uninstall mdbook || true
+cargo uninstall cargo-audit &>/dev/null || true
+cargo uninstall svgbob_cli &>/dev/null || true
+cargo uninstall mdbook &>/dev/null || true

.github/workflows/client-targets.yml

@@ -71,3 +71,12 @@ jobs:
         with:
           command: build
           args: -p solana-client --target ${{ matrix.target }}
+      - name: Send Slack notifiaction
+        if: failure()
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_NOTIFICATIONS_BOT_TOKEN }}
+        uses: voxmedia/github-action-slack-notify-build@v1
+        with:
+          channel: ${{ secrets.SLACK_CHANNEL }}
+          status: FAILED
+          color: danger

.github/workflows/docs.yml

@@ -13,54 +13,95 @@ on:
       - v[0-9]+.[0-9]+
 
 jobs:
-  docs-build:
+  check:
+    outputs:
+      continue: ${{ steps.check.outputs.need_to_build }}
     runs-on: ubuntu-20.04
     steps:
       - name: Checkout
         uses: actions/checkout@v3
         with:
           fetch-depth: 0
 
+      - name: Get commit range (push)
+        if: ${{ github.event_name == 'push' }}
+        run: |
+          echo "COMMIT_RANGE=${{ github.event.before }}..$GITHUB_SHA" >> $GITHUB_ENV
+
+      - name: Get commit range (pull_request)
+        if: ${{ github.event_name == 'pull_request' }}
+        run: |
+          echo "COMMIT_RANGE=${{ github.event.pull_request.base.sha }}..${{ github.event.pull_request.head.sha }}" >> $GITHUB_ENV
+
+      - name: Get file status
+        run: |
+          set +e
+          git diff --name-only $COMMIT_RANGE | grep \
+            -e '.github/workflows/docs.yml' \
+            -e 'docs/**'
+          echo "FILE_CHANGED=$?" >> $GITHUB_ENV
+
       - name: Check
         id: check
+        shell: bash
         run: |
           source ci/env.sh
-          echo "::set-output name=tag::$CI_TAG"
           eval "$(ci/channel-info.sh)"
-          echo "::set-output name=channel::$CHANNEL"
+          TAG=$CI_TAG
 
-      - name: Get specific changed files
-        id: changed-files-specific
-        uses: tj-actions/changed-files@v19
-        with:
-          files: |
-            docs/**
+          echo "TAG: $TAG"
+          echo "CHANNEL: $CHANNEL"
+          echo "FILE_CHANGED: $FILE_CHANGED"
 
-      - name: Pre Build
-        id: prebuild
-        run: |
-          echo "::set-output name=need_to_build::${{
-            steps.check.outputs.tag != ''
-            ||
-            (
-              (steps.check.outputs.channel == 'edge' || steps.check.outputs.channel == 'beta')
-              &&
-              steps.changed-files-specific.outputs.any_change != ''
-            )
-          }}"
-        shell: bash
+          echo need_to_build="$(
+            if [ "$TAG" != '' ]
+            then
+              echo 1
+            elif [ $FILE_CHANGED = 0 ] && ( [ "$CHANNEL" = "beta" ] || [ "$CHANNEL" = "edge" ] )
+            then
+              echo 1
+            else
+              echo 0
+            fi
+          )" >> $GITHUB_OUTPUT
+
+  build_and_deploy:
+    needs:
+      - check
+    if: ${{ needs.check.outputs.continue == 1 }}
+    # the name is used by .mergify.yml as well
+    name: build & deploy docs
+    runs-on: ubuntu-20.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v3
 
       - name: Setup Node
-        if: ${{ steps.prebuild.outputs.need_to_build == 'true' }}
         uses: actions/setup-node@v3
         with:
-          node-version: 14
+          node-version: 16
 
       - name: Build
-        if: ${{ steps.prebuild.outputs.need_to_build == 'true' }}
         working-directory: docs
         run: |
           npm install
           ./build.sh
         env:
           VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}
+          VERCEL_SCOPE: ${{ secrets.VERCEL_SCOPE }}
+
+  notification:
+    if: failure()
+    runs-on: ubuntu-20.04
+    needs:
+      - check
+      - build_and_deploy
+    steps:
+      - name: Send Slack notifiaction
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_NOTIFICATIONS_BOT_TOKEN }}
+        uses: voxmedia/github-action-slack-notify-build@v1
+        with:
+          channel: ${{ secrets.SLACK_CHANNEL }}
+          status: FAILED
+          color: danger

.github/workflows/export-github-repo.yml

@@ -25,3 +25,12 @@ jobs:
           chmod +x ./ci/export-github-repo.sh
           ./ci/export-github-repo.sh web3.js/ solana-web3.js
         shell: bash
+      - name: Send Slack notifiaction
+        if: failure()
+        env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_NOTIFICATIONS_BOT_TOKEN }}
+        uses: voxmedia/github-action-slack-notify-build@v1
+        with:
+          channel: ${{ secrets.SLACK_CHANNEL }}
+          status: FAILED
+          color: danger

.github/workflows/release-artifacts-auto.yml

@@ -8,6 +8,10 @@ on:
     tags:
       - v[0-9]+.[0-9]+.[0-9]+
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   release-artifacts:
     uses: ./.github/workflows/release-artifacts.yml
@@ -17,3 +21,17 @@ jobs:
       AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
       AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}
       AWS_S3_BUCKET: ${{ secrets.AWS_S3_BUCKET }}
+
+  send-slack-notification:
+    runs-on: ubuntu-20.04
+    needs:
+      - release-artifacts
+    if: failure()
+    steps:
+      - env:
+          SLACK_BOT_TOKEN: ${{ secrets.SLACK_NOTIFICATIONS_BOT_TOKEN }}
+        uses: voxmedia/github-action-slack-notify-build@v1
+        with:
+          channel: ${{ secrets.SLACK_CHANNEL }}
+          status: FAILED
+          color: danger

.github/workflows/release-artifacts.yml

@@ -47,9 +47,9 @@ jobs:
         id: build
         shell: bash
         run: |
-          choco install openssl
-          export OPENSSL_DIR="C:\Program Files\OpenSSL-Win64"
+          export OPENSSL_DIR="C:\Program Files\OpenSSL"
           choco install protoc
+          export PROTOC="C:\ProgramData\chocolatey\lib\protoc\tools\bin\protoc.exe"
           source /tmp/env.sh
           echo "::set-output name=tag::$CI_TAG"
           eval "$(ci/channel-info.sh)"

.gitmodules

@@ -0,0 +1,3 @@
+[submodule "firedancer"]
+	path = firedancer
+	url = [email protected]:tinydancer-io/firedancer.git

CONTRIBUTING.md

@@ -250,20 +250,12 @@ confused with 3-letter acronyms.
 
 ## Design Proposals
 
-Solana's architecture is described by docs generated from markdown files in
-the `docs/src/` directory, maintained by an *editor* (currently @garious). To
-add a design proposal, you'll need to include it in the
-[Accepted Design Proposals](https://docs.solana.com/proposals/accepted-design-proposals)
-section of the Solana docs.  Here's the full process:
-
-1. Propose a design by creating a PR that adds a markdown document to the
-   `docs/src/proposals` directory and references it from the [table of
-   contents](docs/src/SUMMARY.md). Add any relevant *maintainers* to the PR
-   review.
-2. The PR being merged indicates your proposed change was accepted and that the
-   maintainers support your plan of attack.
-3. Submit PRs that implement the proposal. When the implementation reveals the
-   need for tweaks to the proposal, be sure to update the proposal and have that
-   change reviewed by the same people as in step 1.
-4. Once the implementation is complete, submit a PR that moves the link from
-   the Accepted Proposals to the Implemented Proposals section.
+Solana's architecture is described by docs generated from markdown files in the `docs/src/`
+directory and viewable on the official [Solana Documentation](https://docs.solana.com) website.
+
+Current design proposals may be viewed on the docs site:
+
+1. [Accepted Proposals](https://docs.solana.com/proposals/accepted-design-proposals.md).
+2. [Implemented Proposals](https://docs.solana.com/implemented-proposals/implemented-proposals.md)
+
+New design proposals should follow this guide on [how to submit a design proposal](./docs/src/proposals.md#submit-a-design-proposal).