Hi,

Could it be, that the Github Status Plugin is currently not working as expected? Since some time i am missing the reported build status for my flake on github.

The error message according hydra-notify is the following:

Sep 16 18:22:56 tank hydra-notify[2039]: Flake is github:shawn8901/nixos-configuration/28dbe4cc7f9b036bb7a3fc37a22b08730f48df0d?narHash=sha256-BeuUHKxtlcnweo9c2rZLRABgIv2ARBUXfySQ6MJDxQA%3D
Sep 16 18:22:56 tank hydra-notify[2039]: Can't parse flake, skipping GitHub status update

https://github.com/NixOS/hydra/blob/274027eb504c7fe090e00c16fd94f4b832981095/src/lib/Hydra/Plugin/GithubStatus.pm#L100

Which is right according the regex, tho i am not seeing what should be wrong on my end, it looks to me that the narHash that is in the url is unexpected.

My jobset definition is here: https://github.com/Shawn8901/nixos-configuration/blob/b1f6e066c77c4eb078bcf873bf6e7eeb3a91db16/.hydra/jobsets.nix#L28

And i dont see where i could cause the narHash to be included and i asume its more a internal issue here.

Hi,

Could it be, that the Github Status Plugin is currently not working as expected for flakes? Since some time i am missing the reported build status for my flake on github.

The error message according hydra-notify is the following:

Sep 16 18:22:56 tank hydra-notify[2039]: Flake is github:shawn8901/nixos-configuration/28dbe4cc7f9b036bb7a3fc37a22b08730f48df0d?narHash=sha256-BeuUHKxtlcnweo9c2rZLRABgIv2ARBUXfySQ6MJDxQA%3D
Sep 16 18:22:56 tank hydra-notify[2039]: Can't parse flake, skipping GitHub status update

https://github.com/NixOS/hydra/blob/274027eb504c7fe090e00c16fd94f4b832981095/src/lib/Hydra/Plugin/GithubStatus.pm#L100

Which is right according the regex, tho i am not seeing what should be wrong on my end, it looks to me that the narHash that is in the url is unexpected.

My jobset definition is here: https://github.com/Shawn8901/nixos-configuration/blob/b1f6e066c77c4eb078bcf873bf6e7eeb3a91db16/.hydra/jobsets.nix#L28

And i dont see where i could cause the narHash to be included and i asume its more a internal issue here.

I saw that there is https://github.com/NixOS/hydra/issues/1486 but my hydra.conf looks fine according to what is mentioned in the issue

❯ cat /var/lib/hydra/hydra.conf
evaluator_max_memory_size = 4096
evaluator_workers = 4
max_concurrent_evals = 1
restrict-eval = false
max_output_size = 5368709120
max_db_connections = 150
compress_build_logs = 1
<runcommand>
  job = *:*:merge-pr
  command = /nix/store/vfw63pq1i2r937j7aszff38msfi4d0y8-merge_pr/bin/merge_pr
</runcommand>
<hydra_notify>
  <prometheus>
    listen_address = 127.0.0.1
    port = 9199
  </prometheus>
</hydra_notify>
<githubstatus>
  jobs = .*
  useShortContext = true
</githubstatus>
Include /run/secrets/rendered/hydra-write-token.conf
Include /run/secrets/rendered/hydra-hook-token.conf

using_frontend_proxy = 1
base_uri = https://hydra.pointjig.de
notification_sender = hydra@pointjig.de
max_servers = 25

gc_roots_dir = /nix/var/nix/gcroots/hydra
use-substitutes = 1

I saw that there is https://github.com/NixOS/hydra/issues/1486 but my hydra.conf looks fine according to what is mentioned in the issue

❯ cat /var/lib/hydra/hydra.conf
evaluator_max_memory_size = 4096
evaluator_workers = 4
max_concurrent_evals = 1
restrict-eval = false
max_output_size = 5368709120
max_db_connections = 150
compress_build_logs = 1
<runcommand>
  job = *:*:merge-pr
  command = /nix/store/vfw63pq1i2r937j7aszff38msfi4d0y8-merge_pr/bin/merge_pr
</runcommand>
<hydra_notify>
  <prometheus>
    listen_address = 127.0.0.1
    port = 9199
  </prometheus>
</hydra_notify>
<githubstatus>
  jobs = .*
  useShortContext = true
</githubstatus>
Include /run/secrets/rendered/hydra-write-token.conf
Include /run/secrets/rendered/hydra-hook-token.conf

using_frontend_proxy = 1
base_uri = https://hydra.pointjig.de
notification_sender = hydra@pointjig.de
max_servers = 25

gc_roots_dir = /nix/var/nix/gcroots/hydra
use-substitutes = 1

so the config part of the issue seems unrelated and its more the 2nd part about the url.

I assume issue author did later just use the git url variant, but i dont think that this is a proper solution as the github url is quite nice to use.