bazel-website
bazel-website copied to clipboard
bazelbuild
slack.bazel.build is down
The self-inviter we're using uses the legacy token mechanism, which Slack has turned down.
Turns out that we don't need that anymore, since Slack now supports non-expiring invite links: https://bazelbuild.slack.com/join/shared_invite/zt-dzm4qj0h-maSR3EcEr8SWE1f7dA55zw#/
If you're signed in to the workspace, clicking on this link redirects you to the workspace.
If you're not signed in to the workspace. clicking on this link provides you with a sign up form. I think we can turn down the self-inviter service and configure the service behind slack.bazel.build to redirect to https://bazelbuild.slack.com/join/shared_invite/zt-dzm4qj0h-maSR3EcEr8SWE1f7dA55zw#/.
cc @philwo @fweikert
@jin Hey, sorry that I didn't follow up earlier!
AFAIK the slack.bazel.build domain currently points to Google Cloud Run. I think we can deploy a container that just serves a redirect until we figure out a better solution... I'll have a look.
Yeah, that seems like the simplest workaround for now! Thanks for taking a look.
The redirect is online! I'll update our documentation how I built and deployed the container tomorrow. :)
Yay! Thanks @philwo! This is a much better experience for signed-in users, too :)
Just tried, got a redirect eventually to "https://bazelbuild.slack.com/join/shared_invite/zt-dzm4qj0h-maSR3EcEr8SWE1f7dA55zw#/shared-invite-legacy/error : "This link is no longer active To join this workspace, you’ll need to ask the person who originally invited you for a new link."
+Yun Peng @.***>
On Tue, Feb 1, 2022 at 8:24 PM Joe Hicks @.***> wrote:
Just tried, got a redirect eventually to " https://bazelbuild.slack.com/join/shared_invite/zt-dzm4qj0h-maSR3EcEr8SWE1f7dA55zw#/shared-invite-legacy/error : "This link is no longer active To join this workspace, you’ll need to ask the person who originally invited you for a new link."
— Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel-website/issues/251#issuecomment-1027487218, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXHHHBYPX452PKJRCVQX7TUZCBVTANCNFSM4N37O2SA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message ID: @.***>
I have been looking around and it looks like this is the non-expiring Slack invitation link for bazelbuild: https://join.slack.com/t/bazelbuild/shared_invite/zt-12qiikgw6-qYqQMtD3aFxLQrA_77xV5Q
Let's redirect slack.bazel.build to the link above.
Actually, it will expire after 2000 people join with this link, but won't expire within a set timeframe.
It should be fixed now! https://github.com/bazelbuild/continuous-integration/pull/1319
On Wed, Feb 2, 2022 at 5:05 AM Joe Hicks @.***> wrote:
I have been looking around and it looks like this is the non-expiring Slack invitation link for bazelbuild: https://join.slack.com/t/bazelbuild/shared_invite/zt-12qiikgw6-qYqQMtD3aFxLQrA_77xV5Q
Let's redirect slack.bazel.build to the link above.
Actually, it will expire after 2000 people join with this link, but won't expire within a set timeframe.
— Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel-website/issues/251#issuecomment-1027554165, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA72PNS3VOXYDSZ3HA3A6HDUZCUOZANCNFSM4N37O2SA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
The link now only serves 100 people before expiring, no matter what the expiration date is.
Is there a way to remove that limit? Or we just have to update the link when we notice it doesn't work?
per discussion on slack (heh), we could set up https://github.com/rauchg/slackin
+Jason Dobies @.***>
On Thu, May 19, 2022 at 12:53 PM Xùdōng Yáng @.***> wrote:
per discussion on slack (heh), we could set up https://github.com/rauchg/slackin
— Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel-website/issues/251#issuecomment-1131956156, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAXHHHBGTNJZPKYEIJTONDTVKZWZLANCNFSM4N37O2SA . You are receiving this because you commented.Message ID: @.***>
@jin Can you look into how to setup slackin since you have the experience?
I just caught up with the history here -- slackin uses legacy Slack API tokens, which Slack stopped generating, and legacy APIs, which no longer work.
See https://github.com/rauchg/slackin/issues/417 and https://github.com/rauchg/slackin/issues/416
It appears that expiring links are a common complain towards Slack as well: https://github.com/integrations/slack/issues/1063
I think we need a different solution than rebooting Slackin.
@dwirandytlvk We just updated the invitation link, slack.bazel.build should work now.
Hello, just wanted to let the team know that the invite is currently expired
Thanks for taking a look! I just checked slack.bazel.build and it doesn't seem to work for me
I had to open https://slack.bazel.build in an incognito window but it works now, I cleared my browser history but that wasn't sufficient without incognito. Thanks for helping!