Some linters don't get enabled automatically

[xephos1one]

My repo contains multiple .yml files yamllint should be automatically enabled when initializing trunk and while doing so yamllint gets queried:

Initializing 24% [==========================================================>                                                                                                                                                                                                ]  4/17  6.0s 

 ↳ Querying latest versions                                                                                                                                                                                                                                                                
   ↳ bandit ⠋                                                                                                                                                                                                                                                                              
   ↳ checkov ⠋                                                                                                                                                                                                                                                                             
   ↳ ruff ⠋                                                                                                                                                                                                                                                                                
   ↳ yamllint ⠋

but in the end it doesn't enable it:

Initializing 100% [=======================================================================================================================================================================================================================================================>]  17/17  11.6s 
Formatting Configs 100% [==================================================================================================================================================================================================================================================>]  12/12  0.7s 
                                                                                                                                                                                                                                                                                           
✔ 9 linters were enabled (.trunk/trunk.yaml)

  dotenv-linter 3.3.0 (1 dotenv file)
  git-diff-check (55 files)
  hadolint 2.12.1-beta (1 docker file) (created .hadolint.yaml)
  markdownlint 0.44.0 (1 markdown file) (created .markdownlint.yaml)
  osv-scanner 2.0.1 (1 lockfile file)
  oxipng 9.1.4 (1 png file)
  prettier 3.5.3 (1 markdown, 35 yaml files)
  taplo 0.9.3 (4 toml files)
  trufflehog 3.88.25 (55 files)

Enabling it manually also fails with a not very helpful error message:

$ trunk check enable yamllint
✖ Trunk Internal Error: Please report this issue at https://slack.trunk.io (reference id: f01c5258b2754cc449002b678acfb147)

I don't use Slack so I reported it here.

Using the VS Code extension with Ubuntu 22.04.5 LTS in WSL2.
In this environment I use a proxy server to connect to the internet, in case this might be important.

[TylerJang27]

Hi! Thanks for reporting this issue. The logs indicate a timeout trying to connect to the pypi server, so I suspect your proxy server is a factor here.

Here's a couple things I'd appreciate you trying:

1. If you manually add yamllint@1.37.0 to your enabled list in .trunk/trunk.yaml, can you run trunk check --filter=yamllint <path>
2. Configure your proxy so that you can curl https://pypi.org/pypi/yamllint/json. If that works but Trunk continues to error in the same way, we can attempt to diagnose the mismatch with your proxy configuration

[xephos1one]

Thanks for the answer and the recommendations.

I can curl https://pypi.org/pypi/yamllint/json already.

Adding yamllint@1.37.0 to enabled linters in .trunk/trunk.yaml did the trick.
The first call of trunk check --filter=yamllint <path> did install yamllint and linting is now working as expected.

But why does the automatic install fail then?
Looks like to be the same with bandit, checkov and ruff, manually adding them installs and activates them.
Is there any logging I could enable to see what's goin?

[xephos1one]

Any update on this issue or another thing I could try or activate some logging?

[TylerJang27]

Hi, sorry I missed your follow-up. If you remove yamllint from your .trunk/trunk.yaml, you can then run trunk check enable yamllint --debug to get all of our logs from that command. With that being said, the error that I saw from the crash report was a timeout trying to curl that URL, so I don't have any other ideas for what could be the issue, unless we're missing some env vars that using your proxy requires

[xephos1one]

$ trunk check enable yamllint --debug
[07-11 15:17:11] [run.cc:557] Ran command: 'check enable yamllint --debug' LogLevel:debug
[07-11 15:17:11] [regex.cc:19] Parse regex function failed: Input '11.9.2' did not match regex 'flyway-(?P<semver>.*)'
[07-11 15:17:11] [download.cc:231] flyway could not parse arg 'semver' from regex function '${version}=>flyway-(?P<semver>.*)' 
[07-11 15:17:11] [client.cc:40] upstream is set to 'null'
[07-11 15:17:11] [service.cc:155] [user-agent=unknown sid=n/a] RX:virtual grpc::Status trunk::cli::lint::Service::Start(grpc::ServerContext *, const proto::v1::StartRequest *, grpc::ServerWriter<proto::v1::StartResponse> *) [DAEMON]
[07-11 15:17:11] [git_source_control.cc:517] Computing merge base between 20890d47e3ef19c1e1eef2ff5baaf304f8ae7a6d and 20890d47e3ef19c1e1eef2ff5baaf304f8ae7a6d [DAEMON]
[07-11 15:17:11] [git_source_control.cc:519] Resolved divergent commit as 20890d47e3ef19c1e1eef2ff5baaf304f8ae7a6d [DAEMON]
[07-11 15:17:11] [session_context.cc:167] Making commit info with id: 20890d47e3ef19c1e1eef2ff5baaf304f8ae7a6d [DAEMON]
[07-11 15:17:11] [service.cc:237] [user-agent=unknown sid=n/a] lint session created sid=3 with the following options:
cache_enabled: true, num_jobs: 4, session_type: 1, client_id: , scope: 1 [DAEMON]
[07-11 15:17:11] [service.cc:155] [user-agent=unknown sid=n/a] TX:virtual grpc::Status trunk::cli::lint::Service::Start(grpc::ServerContext *, const proto::v1::StartRequest *, grpc::ServerWriter<proto::v1::StartResponse> *) status=OK [DAEMON]
[07-11 15:17:11] [service.cc:647] [user-agent=unknown sid=n/a] RX:virtual grpc::Status trunk::cli::lint::Service::Enable(grpc::ServerContext *, const proto::v1::EnableRequest *, proto::v1::EnableResponse *) [DAEMON]
[07-11 15:17:12] [release.cc:138] Retrieved 1 linter-version pairs from ReleaseVersionService [DAEMON]
[07-11 15:17:17] [sentry.cc:364] Trunk Internal Error
---
trunk_cli_version: 1.24.0
title: Internal trunk error occurred. Please report this issue to us @ https://slack.trunk.io
report:
  - Timeout connecting to host [DAEMON]
[07-11 15:17:17] [service.cc:647] [user-agent=unknown sid=n/a] TX:virtual grpc::Status trunk::cli::lint::Service::Enable(grpc::ServerContext *, const proto::v1::EnableRequest *, proto::v1::EnableResponse *) status=INTERNAL err='Trunk Internal Error: Please report this issue at https://slack.trunk.io (reference id: 7e51a0bfb36c45abee32ffd56a29f416)' [DAEMON]
[07-11 15:17:17] [client.cc:19] GRPC Failed (error code INTERNAL): Trunk Internal Error: Please report this issue at https://slack.trunk.io (reference id: 7e51a0bfb36c45abee32ffd56a29f416)
[07-11 15:17:17] [service.cc:266] lint session ended sid=3 [DAEMON]
[07-11 15:17:17] [service.cc:268] [user-agent=unknown sid=3] RX:virtual grpc::Status trunk::cli::lint::Service::End(grpc::ServerContext *, const proto::v1::EndRequest *, proto::v1::EndResponse *) [DAEMON]
[07-11 15:17:17] [service.cc:268] [user-agent=unknown sid=3] TX:virtual grpc::Status trunk::cli::lint::Service::End(grpc::ServerContext *, const proto::v1::EndRequest *, proto::v1::EndResponse *) status=OK [DAEMON]
[07-11 15:17:17] [service.cc:335] [user-agent=unknown sid=n/a] RX:virtual grpc::Status trunk::cli::lint::Service::End(grpc::ServerContext *, const proto::v1::EndRequest *, proto::v1::EndResponse *) [DAEMON]
[07-11 15:17:17] [service.cc:335] [user-agent=unknown sid=n/a] TX:virtual grpc::Status trunk::cli::lint::Service::End(grpc::ServerContext *, const proto::v1::EndRequest *, proto::v1::EndResponse *) status=OK [DAEMON]
[07-11 15:17:17] [sentry.cc:354] Trunk user error full stack:
trunk_cli_version: 1.24.0
title: Something went wrong (but it doesn't appear to be our fault)
report:
  - "Trunk Internal Error: Please report this issue at https://slack.trunk.io (reference id: 7e51a0bfb36c45abee32ffd56a29f416)"
✖ Trunk Internal Error: Please report this issue at https://slack.trunk.io (reference id: 7e51a0bfb36c45abee32ffd56a29f416)

The first lines indicate some type of error already and "Timeout connecting to host [DAEMON]" is not helpful when there's no URL to connect to.
There's definitely traffic to the proxy server when executing the command but there also are tries to go to the following IPs directly with HTTPS that that will get blocked at the firewall:
35.190.25.25, 151.101.64.223, 151.101.128.223, 130.211.34.183, 52.26.210.209, 44.232.164.14 and 35.186.241.51.
Looking at the DNS requests reveals that api.mixpanel.com and pypi.org are under them while traffic to api.segment.io seems to go through the proxy

When installing a linter successfully through adding it to the trunk.yaml only the following IPs were tried directly:
35.186.241.51, 52.13.185.92 and 107.178.240.159 so pypi.org isn't in there this time

How are api.mixpanel.com, pypi.org and api.segment.io called? Which of these is necessary for the automatic install of matching linters and what differs to installing through adding them to the trunk.yaml?

[xephos1one]

@TylerJang27 Any updates on this?