<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tailscale/tool/node, branch debug-testwrapper</title>
<subtitle>The easiest, most secure way to use WireGuard and 2FA</subtitle>
<id>http://git.waynecole.info/tailscale/atom?h=debug-testwrapper</id>
<link rel='self' href='http://git.waynecole.info/tailscale/atom?h=debug-testwrapper'/>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/'/>
<updated>2023-08-21T15:37:26Z</updated>
<entry>
<title>tool: force HTTP/1.1 in curl to prevent hang behind load balancer</title>
<updated>2023-08-21T15:37:26Z</updated>
<author>
<name>Val</name>
<email>valerie@tailscale.com</email>
</author>
<published>2023-08-21T15:21:51Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/commit/?id=c85d7c301a94a37212b41b7c856b1be192c2a673'/>
<id>urn:sha1:c85d7c301a94a37212b41b7c856b1be192c2a673</id>
<content type='text'>
When running in our github CI environment, curl sometimes hangs while closing
the download from the nodejs.org server and fails with INTERNAL_ERROR. This is
likely caused by CI running behind some kind of load balancer or proxy that
handles HTTP/2 incorrectly in some minor way, so force curl to use HTTP 1.1.

Updates #8988

Signed-off-by: Val &lt;valerie@tailscale.com&gt;
</content>
</entry>
<entry>
<title>tool/{node,yarn}: update node and yarn tools</title>
<updated>2023-08-10T21:29:29Z</updated>
<author>
<name>Sonia Appasamy</name>
<email>sonia@tailscale.com</email>
</author>
<published>2023-08-10T18:34:38Z</published>
<link rel='alternate' type='text/html' href='http://git.waynecole.info/tailscale/commit/?id=53c722924bb2d834d051f1344804764638af02de'/>
<id>urn:sha1:53c722924bb2d834d051f1344804764638af02de</id>
<content type='text'>
Syncing these up with what we've got in corp.

Updates tailscale/corp#13775

Signed-off-by: Sonia Appasamy &lt;sonia@tailscale.com&gt;
</content>
</entry>
</feed>
