-
Notifications
You must be signed in to change notification settings - Fork 132
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
Change "advance-zed" workflow to "advance-super" #3180
Conversation
@@ -34,22 +34,19 @@ jobs: | |||
# that caused it to wait, reducing push failures down below. | |||
ref: ${{ github.ref }} | |||
# We need a token with permission to push. | |||
token: ${{ secrets.ZQ_UPDATE_PAT }} | |||
token: ${{ secrets.PAT_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That Actions secret called ZQ_UPDATE_PAT
hasn't been updated in 4 years and this is the only Workflow that's been using it. Since it has "ZQ" in its name I'm inclined to get rid of it, and since we have another secret called PAT_TOKEN
that's used in other Workflows and that one is only 2 years old, I'm game to give that one a shot on the assumption it probably has the appropriate permissions. Once we see this Workflow run successfully with PAT_TOKEN
I'll delete the ZQ_UPDATE_PAT
secret from the GitHub config.
# Mock for pcap slice opening to avoid hanging Actions Runner. | ||
# See https://github.com/brimdata/zui/pull/2987 | ||
echo "application/vnd.tcpdump.pcap; /usr/bin/true" >> /home/runner/.mailcap |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're not keeping the pcap-centric functionality alive in the app anymore it seems it should be safe to drop this hack.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me!
Back in October, 2024 via brimdata/super#5347 I disabled the auto-update of the Zed dependency in the Zui repo because changes in super were starting to happen that would break the app. We were focused on other things at the time so we didn't prioritize getting them back in sync and keeping them that way. Now that @jameskerr has recently done the work to start turning Zui into SuperDB Desktop and we've got the app working again with a recent super commit, it seems like it's time to get this auto-update workflow running again so the app will always have the benefit of the latest super changes and we'll know immediately when something breaks it.
While we're at it, here I've done some de-Zed-ing of the workflow in question. Once this is merged and it's prepared to receive the updates from the super side, I'll put up a PR in the super repo to make sure the merge commit notifications are sent with the correct event name and such that it'll match what's done here.