| 10 Sep 2024 |
|  moved to @amadaluzia:tchncs.de changed their display name from Artur Manuel (on break) to (lambda (u) (format nil "~A is not using Matrix right now." u)) "Artur Manuel". | 17:36:48 |
| 11 Sep 2024 |
|  Sr. Estegosaurio joined the room. | 12:49:01 |
 Matt Sturgeon | Do we have a nix-community "bot" account we can use for automated tasks.
Note that it can't be an actual bot (GitHub App), because that won't trigger CI when it pushes. Instead it should be a "machine user" as described here:
User accounts are *intended" for humans, but you can create accounts to automate activity on GitHub. This type of account is called a *machine user". For example, you can create a machine user account to automate continuous integration (CI) workflows.
Managing bots and service accounts with two-factor authentication may also be relevant.
In my case, I just want to nominate a @nix-community-bot as the user that will rebase commits when using Mergify's queue. See this discussion for context.
Therefore it needs to be a regular GitHub user, with write access to nixvim (wider access would be fine, so long as only trusted nix-community admins have access to log in as the user). The user must also have logged in to Mergify's dashboard. | 14:55:47 |
| Matt Sturgeon | * Do we have a nix-community "bot" account we can use for automated tasks?
Note: it can't be an actual bot (GitHub App), because that won't trigger CI when it pushes. Instead it should be a "machine user" as described here:
User accounts are intended for humans, but you can create accounts to automate activity on GitHub. This type of account is called a machine user. For example, you can create a machine user account to automate continuous integration (CI) workflows.
Managing bots and service accounts with two-factor authentication may also be relevant.
In my case, I just want to nominate a @nix-community-bot as the user that will rebase commits when using Mergify's queue. See this discussion for context.
Therefore it needs to be a regular GitHub user, with write access to nixvim (wider access would be fine, so long as only trusted nix-community admins have access to login as the user). The user must also have logged in to Mergify's dashboard.
| 15:32:57 |
| Matt Sturgeon | If not, could we add one? | 17:27:48 |
| 12 Sep 2024 |
 zowoq | Can reuse https://github.com/nix-infra-bot, I've logged in to mergify and added it as a collaborator to nixvim. | 00:48:34 |
| zowoq | * Can reuse https://github.com/nix-infra-bot, I've logged it in to mergify and added it as a collaborator to nixvim. | 00:51:14 |
| moved to @amadaluzia:tchncs.de changed their display name from (lambda (u) (format nil "~A is not using Matrix right now." u)) "Artur Manuel" to (lambda (u) (format nil "~a ~a")) "Artur" "Manuel". | 01:49:22 |
| moved to @amadaluzia:tchncs.de changed their display name from (lambda (u) (format nil "~a ~a")) "Artur" "Manuel" to (lambda (f l) (format nil "~a ~a")) "Artur" "Manuel". | 01:56:13 |
 K900 | Does anyone have commit permissions on fenix? Can I get a merge on https://github.com/nix-community/fenix/pull/163 | 04:27:11 |
| K900 | One line change that fixes an eval warning | 04:27:20 |
 cafkafk | ohh that's what's been causing it | 04:27:54 |
| cafkafk | seems like it may just be figsoda https://github.com/orgs/nix-community/teams/fenix or org admins :s | 04:29:59 |
| Matt Sturgeon | Thanks! | 07:00:44 |
 emily | is fenix ~dead-ish? | 08:59:26 |
| emily | looks like this is the first manual change in several months | 09:00:08 |
| emily | and I've scrolled back about a year and not found a substantive change | 09:00:53 |
| emily | perhaps it's time to point people at oxalica/rust-overlay? | 09:01:30 |
| emily | uh, actually figsoda seems to have disappeared from GitHub entirely in July? | 09:01:59 |
 Mic92 | maybe finished studying? | 10:31:41 |
 eyJhb | Maybe it works good enough? | 12:38:00 |
| emily | I mean, we just had to get an org admin to merge a fix for a Nixpkgs deprecation after over a week, so it doesn't seem like an "it's done, no more changes needed" situation | 12:40:29 |
| 13 Sep 2024 |
|  Khalil Santana joined the room. | 00:08:02 |
| cafkafk | > <@emilazy:matrix.org> uh, actually figsoda seems to have disappeared from GitHub entirely in July?
¯\_(ツ)_/¯ this message is seen by figsoda's account, so seems to still be around | 05:46:07 |
| eyJhb | In reply to @emilazy:matrix.org
I mean, we just had to get an org admin to merge a fix for a Nixpkgs deprecation after over a week, so it doesn't seem like an "it's done, no more changes needed" situation Upstream changes doesn't really change that, does it? Project might be done and quite usable, but accounting for upstream changes breaking something is kind of hard. And not always you have the time to sit down and fix such things. | 06:03:58 |
| emily | sure, I'm not blaming anyone | 11:26:47 |
| emily | just wondering if there is a plan for ongoing maintenance | 11:27:07 |
| Matt Sturgeon | Its not blocking me, as everything passed on a rebuild, but I figured I should report so the infra/buildbot maintainers are aware:
I just had a buildbot build fail with "cachix: FailureResponse | 524: A timeout occurred" (only one build had the issue; the other 199 all passed). Not seen this before, so I'll monitor to see if it becomes a recurring issue.
| 11:41:51 |
| Mic92 | Matt Sturgeon: I saw error 500 in a different place too for cachix. It's something domen has to fix. | 12:25:20 |
| Mic92 | In reply to @emilazy:matrix.org
just wondering if there is a plan for ongoing maintenance It was merged. We can ask the community if someone else wants to take over maintainance. | 12:26:05 |
