Updates binderhub chart to 1.0.0-0.dev.git.3673.h040c9bbe

[jupyterhub-bot]

Updates mybinder to depend on the binderhub chart version 1.0.0-0.dev.git.3673.h040c9bbe from version 1.0.0-0.dev.git.3548.h83da55db.

	Before	After
Chart.yaml's version	1.0.0-0.dev.git.3548.h83da55db	1.0.0-0.dev.git.3673.h040c9bbe
Chart.yaml's appVersion	null	null

PRs

125 commits between 83da55db and 040c9bbe, not searching for PRs

jupyterhub/binderhub@83da55d...040c9bb

Related

• Chart source code: https://github.com/jupyterhub/binderhub/tree/HEAD/helm-chart
• Chart changelog:
• Application changelog: https://github.com/jupyterhub/binderhub/blob/HEAD/CHANGES.md

[manics]

This requires changes to our tests or it'll fail to deploy, see the description of
#3154

[manics]

#3189 failed on staging:
https://github.com/jupyterhub/mybinder.org-deploy/actions/runs/12947617899/job/36116473982
presumably because it's coupled to this PR. If it's working merging this PR should now pass on staging.

[manics]

/test-this-pr

[jupyterhub-bot]

This Pull Request is now being tested 🎉 See the test progress in GitHub Actions.

[jupyterhub-bot]

Job status: success
Branch 'test-this-pr/3156' has been deleted

[manics]

The donate button needs a fix

[rgaiacs]

@manics where did you get the screenshot from? My understanding is that the button is defined in

mybinder.org-deploy/mybinder/values.yaml

Lines 174 to 192 in c46ce00

	banner_message: |
	<a class="btn" style="width:fit-content;height:fit-content;padding:10px;background-color:#e66581;color:white;font-weight:bold;position:absolute;top:0px;bottom:0px;margin:auto 0;right:4px;"
	onmouseover="this.style.backgroundColor='#d15b75'" onmouseout="this.style.backgroundColor='#e66581'"
	href="https://jupyter.org/about#donate" target="_blank">
	🤍 Donate to mybinder.org!
	</a>
	<div style="text-align:center;">
	Thanks to <a href="https://www.ovh.com/">OVH</a>, <a href="https://notebooks.gesis.org">GESIS Notebooks</a> and <a href="https://2i2c.org">2i2c</a> for supporting us! 🎉
	</div>
	<div style="text-align:center;">
	mybinder.org has updated the base image to Ubuntu 22.04! See the <a href="https://repo2docker.readthedocs.io/en/latest/howto/breaking_changes.html">upgrade guide</a> for details.
	</div>
	about_message: |
	<p>mybinder.org is public infrastructure operated by the <a href="https://jupyterhub-team-compass.readthedocs.io/en/latest/team.html#binder-team">Binder Project team</a>.<br /><br />
	The Binder Project is a member of <a href="https://jupyter.org">Project Jupyter</a>.
	Donations are managed by <a href="https://lf-charities.org">LF Charities</a>, a US 501c3 non-profit.<br /><br />
	For abuse please email: <a href="mailto:[email protected]">[email protected]</a>, to report a
	security vulnerability please see: <a href="https://mybinder.readthedocs.io/en/latest/faq.html#where-can-i-report-a-security-issue">Where can I report a security issue</a><br /><br />
	For more information about the Binder Project, see <a href="https://mybinder.readthedocs.io/en/latest/about.html">the About Binder page</a></p>

[minrk]

/test-this-pr

[jupyterhub-bot]

This Pull Request is now being tested 🎉 See the test progress in GitHub Actions.

[jupyterhub-bot]

Job status: success
Branch 'test-this-pr/3156' has been deleted

[minrk]

/test-this-pr

[jupyterhub-bot]

This Pull Request is now being tested 🎉 See the test progress in GitHub Actions.

[jupyterhub-bot]

Job status: success
Branch 'test-this-pr/3156' has been deleted

[minrk]

Donate button looks right now:

Going to give this a try!

FWIW, when the connection is lost, our event stream error message is now slightly different:

Error in event stream: TypeError: Load failed

I don't remember exactly what the wording was before.

This is not a regression, but something we can still improve in a later PR. I encountered this because I was messing around with the page watching a build while a new deploy was running. When the BinderHub server restarts, users see this message and it's very unclear that what they probably need to do is just reconnect (refresh the page).

[minrk]

needed to restart prod-deploy which failed the first time because the proxied hetzner-2i2c hadn't yet deployed the updated template when the prod test ran. This shouldn't happen often.

[minrk]

@rgaiacs you're right. The screenshot I assume is from staging.mybinder.org. We can test deploying changes only to staging with the "test this pr" comments, then check staging by hand to make sure everything's working before merging.