Build fails because some tree-sitter grammars failed to fetch

[766F6964]

Summary

I am currently trying to compile helix from source from the latest master branch: 3f9788d.
At the end of the compilation process, the build aborts because some tree-sitter grammars could not be fetched, see below:

   Compiling helix-view v0.6.0 (/tmp/helix/helix-view)
   Compiling helix-tui v0.6.0 (/tmp/helix/helix-tui)
error: failed to run custom build command for `helix-term v0.6.0 (/tmp/helix/helix-term)`

Caused by:
  process didn't exit successfully: `/tmp/helix/target/release/build/helix-term-c672681d574027c2/build-script-build` (exit status: 101)
  --- stdout
  Fetching 168 grammars
  65 up to date git grammars
  88 updated grammars
  	astro           now on 947e93089e60c66e681eba22283f4037841451e7
  	bass            now on 501133e260d768ed4e1fd7374912ed5c86d6fd90
  	bicep           now on d8e097fcfa143854861ef737161163a09cc2916b
  	blueprint       now on 863cea9f83ad5637300478e0559262f1e791684b
  	capnp           now on fc6e2addf103861b9b3dffb82c543eb6b71061aa
  	clojure         now on e57c569ae332ca365da623712ae1f50f84daeae2
  	cpon            now on 0d01fcdae5a53191df5b1349f9bce053833270e7
  	css             now on 769203d0f9abe1a9a691ac2b9fe4bb4397a73c51
  	cue             now on 61843e3beebf19417e4fede4e8be4df1084317ad
  	d               now on 601c4a1e8310fb2f3c43fa8a923d0d27497f3c04
  	devicetree      now on 877adbfa0174d25894c40fa75ad52d4515a36368
  	dhall           now on affb6ee38d629c9296749767ab832d69bb0d9ea8
  	dot             now on 917230743aa10f45a408fea2ddb54bbbf5fbe7b7
  	dtd             now on 6116becb02a6b8e9588ef73d300a9ba4622e156f
  	edoc            now on 74774af7b45dd9cefbf9510328fc6ff2374afc50
  	elvish          now on e50787cadd3bc54f6d9c0704493a79078bb8a4e5
  	erlang          now on ce0ed253d72c199ab93caba7542b6f62075339c4
  	forth           now on 90189238385cf636b9ee99ce548b9e5b5e569d48
  	fortran         now on f0f2f100952a353e64e26b0fa710b4c296d7af13
  	fsharp          now on 18da392fd9bd5e79f357abcce13f61f3a15e3951
  	gas             now on 60f443646b20edee3b7bf18f3a4fb91dc214259a
  	gdscript        now on a4b57cc3bcbfc24550e858159647e9238e7ad1ac
  	gemini          now on 3cc5e4bdf572d5df4277fc2e54d6299bd59a54b3
  	gleam           now on a59aadf3d7c11702cad244e7cd6b67b34ca9c16a
  	gn              now on e18d6e36a79b20dafb58f19d407bd38b0e60260e
  	godot-resource  now on b6ef0768711086a86b3297056f9ffb5cc1d77b4a
  	hare            now on 2495958aaf3f93581c87ec020164255e80655331
  	haskell         now on d7ac98f49e3ed7e17541256fe3881a967d7ffdd3
  	hcl             now on 3cb7fc28247efbcb2973b97e71c78838ad98a583
  	hosts           now on 301b9379ce7dfc8bdbe2c2699a6887dcb73953f9
  	html            now on 29f53d8f4f2335e61bf6418ab8958dac3282077a
  	hurl            now on 264c42064b61ee21abe88d0061f29a0523352e22
  	ini             now on 4d247fb876b4ae6b347687de4a179511bf67fcbc
  	javascript      now on f772967f7b7bc7c28f845be2420a38472b16a8ee
  	jinja2          now on a533cd3c33aea6acb0f9bf9a56f35dcfe6a8eb53
  	jsdoc           now on 189a6a4829beb9cdbe837260653b4a3dfb0cc3db
  	jsonnet         now on 0475a5017ad7dc84845d1d33187f2321abcb261d
  	just            now on 8af0aab79854aaf25b620a52c39485849922f766
  	kdl             now on 3ca569b9f9af43593c24f9e7a21f02f43a13bb88
  	kotlin          now on a4f71eb9b8c9b19ded3e0e9470be4b1b77c2b569
  	markdoc         now on 5ffe71b29e8a3f94823913ea9cea51fcfa7e3bf8
  	matlab          now on 6071891a8c39600203eba20513666cf93b4d650a
  	mermaid         now on d787c66276e7e95899230539f556e8b83ee16f6d
  	meson           now on 32a83e8f200c347232fa795636cfe60dde22957a
  	nasm            now on a0db15db6fcfb1bf2cc8702500e55e558825c48b
  	nu              now on 98c11c491e3405c75affa1cf004097692da3dda2
  	odin            now on b219207e49ffca2952529d33e94ed63b1b75c4f1
  	opencl          now on 8e1d24a57066b3cd1bb9685bbc1ca9de5c1b78fb
  	openscad        now on 5c3ce93df0ac1da7197cf6ae125aade26d6b8972
  	org             now on 698bb1a34331e68f83fc24bdd1b6f97016bb30de
  	pascal          now on 2fd40f477d3e2794af152618ccfac8d92eb72a66
  	passwd          now on 20239395eacdc2e0923a7e5683ad3605aee7b716
  	pem             now on be67a4330a1aa507c7297bc322204f936ec1132c
  	po              now on 417cee9abb2053ed26b19e7de972398f2da9b29e
  	ponylang        now on ef66b151bc2604f431b5668fcec4747db4290e11
  	prisma          now on eca2596a355b1a9952b4f80f8f9caed300a272b5
  	prql            now on 09e158cd3650581c0af4c49c2e5b10c4834c8646
  	qmljs           now on 0b2b25bcaa7d4925d5f0dda16f6a99c588a437f1
  	ron             now on 7762d709a0f7c1f9e269d0125a2e8a7a69006146
  	rst             now on 25e6328872ac3a764ba8b926aea12719741103f1
  	scheme          now on af3af6c9356b936f8a515a1e449c32e804c2b1a8
  	scss            now on c478c6868648eff49eb04a4df90d703dc45b312a
  	slint           now on 00c8a2d3645766f68c0d0460086c0a994e5b0d85
  	sml             now on bd4055d5554614520d4a0706b34dc0c317c6b608
  	sql             now on 25be0b8f17e9189ad9e1b875869d025c5aec1286
  	sshclientconfig now on e45c6d5c71657344d4ecaf87dafae7736f776c57
  	strace          now on 2b18fdf9a01e7ec292cc6006724942c81beb7fd5
  	t32             now on 6da5e3cbabd376b566d04282005e52ffe67ef74a
  	templ           now on ea56ac0655243490a4929a988f4eaa91dfccc995
  	todotxt         now on 0207f6a4ab6aeafc4b091914d31d8235049a2578
  	tsx             now on b1bf4825d9eaa0f3bdeb1e52f099533328acfbdf
  	typescript      now on b1bf4825d9eaa0f3bdeb1e52f099533328acfbdf
  	typst           now on e35aa22395fdde82bbc4b5700c324ce346dfc9e5
  	ungrammar       now on a7e104629cff5a8b7367187610631e8f5eb7c6ea
  	unison          now on 98c4e8bc5c9f5989814a720457cf36963cf4043d
  	uxntal          now on d68406066648cd6db4c6a2f11ec305af02079884
  	v               now on e14fdf6e661b10edccc744102e4ccf0b187aa8ad
  	vala            now on c9eea93ba2ec4ec1485392db11945819779745b3
  	verilog         now on 4457145e795b363f072463e697dfe2f6973c9a52
  	vhs             now on c6d81f34c011c29ee86dd73b45a8ecc9f2e2bdaf
  	vue             now on 91fe2754796cd8fba5f229505a23fa08f3546c06
  	wast            now on 2ca28a9f9d709847bf7a3de0942a84e912f59088
  	wat             now on 2ca28a9f9d709847bf7a3de0942a84e912f59088
  	wit             now on c917790ab9aec50c5fd664cbfad8dd45110cfff3
  	wren            now on 793d58266924e6efcc40e411663393e9d72bec87
  	xml             now on 48a7c2b6fb9d515577e115e6788937e837815651
  	yaml            now on 0e36bed171768908f331ff7dff9d956bae016efb
  	yuck            now on e3d91a3c65decdea467adebe4127b8366fa47919
  Failure 1/15: solidity Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/JoranHonig/tree-sitter-solidity/': Could not resolve host: github.com

  Failure 2/15: embedded-template Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/tree-sitter/tree-sitter-embedded-template/': Could not resolve host: github.com

  Failure 3/15: robot Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/Hubro/tree-sitter-robot/': Could not resolve host: github.com

  Failure 4/15: task Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/alexanderbrevig/tree-sitter-task/': Could not resolve host: github.com

  Failure 5/15: r Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/r-lib/tree-sitter-r/': Could not resolve host: github.com

  Failure 6/15: xit Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/synaptiko/tree-sitter-xit/': Could not resolve host: github.com

  Failure 7/15: swift Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/alex-pinkus/tree-sitter-swift/': Could not resolve host: github.com

  Failure 8/15: smithy Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/indoorvivants/tree-sitter-smithy/': Could not resolve host: github.com

  Failure 9/15: vhdl Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/teburd/tree-sitter-vhdl/': Could not resolve host: github.com

  Failure 10/15: eex Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/connorlay/tree-sitter-eex/': Could not resolve host: github.com

  Failure 11/15: esdl Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/greym0uth/tree-sitter-esdl/': Could not resolve host: github.com

  Failure 12/15: nim Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/aMOPel/tree-sitter-nim/': Could not resolve host: github.com

  Failure 13/15: rego Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/FallenAngel97/tree-sitter-rego/': Could not resolve host: github.com

  Failure 14/15: heex Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/phoenixframework/tree-sitter-heex/': Could not resolve host: github.com

  Failure 15/15: dbml Git command failed.
  Stdout: 
  Stderr: fatal: unable to access 'https://github.com/dynamotn/tree-sitter-dbml/': Could not resolve host: github.com


  --- stderr
  thread 'main' panicked at 'Failed to fetch tree-sitter grammars: 15 grammars failed to fetch', helix-term/build.rs:5:26
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: failed to compile `helix-term v0.6.0 (/tmp/helix/helix-term)`, intermediate artifacts can be found at `/tmp/helix/target`

This seems strange, because the listed repositories are up and accessible.
I was able to bypass this error by manually deleting the affected grammars in runtime/grammars/sources - however, this isn't exactly ideal.

Reproduction Steps

1. Clone helix source from master branch: 3f9788d
2. Navigate in the cloned directory and run: cargo install --path helix-term --locked
3. Observe the error shown above at the end of the compilation

Helix log

Platform

Linux

Terminal Emulator

xterm-256color

Installation Method

source

Helix Version

3f9788d

[the-mikedavis]

Looks like DNS resolution failed during the build. If you retry I bet it will succeed.

[766F6964]

You are infact correct. I was very confused because some of them were reachable and others weren't.
It seems my issue was that I had NetworkManager and systemd-resolved, both trying to do DNS resolving, causing problems.