[10:33:38] elukey: ryankemper: gehel: fyi i have deployed the java fact now. the bit your most likley intrested in is facter -p java.version.major (or $facts['java']['version']['major] i puppet) [10:33:56] cool! thanks! [10:35:43] jbond42: you rock as always, thanks! [10:36:13] thanks and no probs :) [10:39:09] (just noticed that I got excited by puppet and java versions, this is probably the result of some bad career choices) [10:39:25] lol [10:43:43] elukey: indeed! [10:44:07] elukey: :D [10:44:41] https://bash.toolforge.org/quip/tjq1jXUBgTbpqNOmZ-m4 [10:44:45] <_joe_> elukey: well rejoice - it could be java and helm [10:48:21] moritzm: is there a sane way to figure out what the default `dh_auto_build` target does when using `dh_golang`? i need to override it, but that only makes sense if i know what i'm overriding [10:49:08] <_joe_> we've lost her. "sane way" and "dh_golang" in the same sentence... [10:50:39] _joe_: 🙀 [10:53:16] kormat: for some reason it's not listed in the dh_golang manpage, but the inline comments at the top of /usr/share/perl5/Debian/Debhelper/Buildsystem/golang.pm should list all the steps [10:53:30] sorry for ruining what could've been a fine day with Perl :-) [10:54:39] looks like the same content as in https://manpages.debian.org/testing/dh-golang/Debian::Debhelper::Buildsystem::golang.3pm.en.html [10:54:48] which.. doesn't [10:55:48] things like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821454#27 imply that it's `dh_auto_build -O--buildsystem=golang` [10:56:22] yeah, the steps listed unter "IMPLEMENTATION" map to the respective dh_auto_foo debhelper steps [11:10:19] <_joe_> jbond42: Error: Facter: error while resolving custom fact "java": undefined method `split' for nil:NilClass [11:10:41] _joe_: which machine? [11:10:54] <_joe_> jbond42: deploy2001 [11:11:00] thanks checking [11:11:03] <_joe_> probably no java installed [11:11:11] <_joe_> puppet is still running [11:11:14] yes i suspect the confine is dinfed badly [11:11:28] <_joe_> yeah same on a random appserver [11:12:11] ack thanks [11:17:29] I'm about to reinitialise the postgres replicas in eqiad maps. tilerator is already disabled in eqiad so it should have no user-facing impact. However, this is maps, and so "should" may not correspond with common understandings of the term [11:20:38] hnowlan: https://tools.ietf.org/html/rfc6919 might come handy in those cases ;) [11:27:02] is there a way to access the current git commit from inside `gbp buildpackage --git-pbuilder`? [11:32:37] kormat: you mean the shell you get dropped in when it fails? [11:33:41] no [11:34:04] you mean during the build? [11:34:04] i currently have this in debian/rules: [11:34:06] ``` [11:34:09] override_dh_auto_build: [11:34:09] dh_auto_build -- -ldflags "-X main.AppVersion=$$(cat RELEASE_VERSION) -X main.GitCommit=$$(git rev-parse HEAD)" [11:34:09] ``` [11:34:21] which produces `git: command not found` [11:34:31] AFAIK you just get the archive within the building process, not the repo [11:34:39] but not 100% sure [11:35:40] i was hoping that gbp might pass in the commit id in an env var or something, but i'm not finding a way to do this [11:36:03] you need the SHA1? [11:36:08] *just the [11:36:29] yes [11:38:23] not sure, you need the $EXPERT [11:38:44] _joe_: fyi the java fact should be fixed now [11:38:55] moritzm: hi :) [11:39:21] moritzm: is there a way to have gbp buildpackage pass in the current git commit sha1 to the build env? [11:43:45] not sure, it has many features, but substandard docs. you can probably fix the issue above by simply adding "git" to Build-Depends, though? then it's available for rev-parse in the build environment/chroot? [11:44:05] ah. so the `.git` dir will be present inside? ok, i'll give that a go [11:44:48] no, I meamt the "git: command not found" [11:45:44] moritzm: well, having the git command available inside pbuilder is of limited use if `.git` isn't available :) [11:45:57] `fatal: not a git repository (or any of the parent directories): .git` [11:51:35] alright, i give up. gbp-buildpackage + git-pbuilder + pbuilder + dpkg-buildpackage is an impenetrable mess. [11:52:39] you could try passing --git-export-dir=DIRECTORY to get a checkout which should be available in the build environment [11:53:11] or simply ditch the [11:53:45] or simply ditch the X main.GitCommit hack it doesn't seem particularly useful in the first place? is that for displaying some version info or so? [11:53:58] that's what i'm going with [11:54:11] yes, it's used in the output of `orchestrator -version`, and in the startup log message [11:54:34] it turns out that it's vital that main.AppVersion is set correctly [11:54:44] (T267113) [11:54:44] T267113: Orchestrator binary needs version embedded - https://phabricator.wikimedia.org/T267113 [11:55:03] -X main.GitCommit=bespokeWMFbuild then :-) [11:55:10] hah ;) [11:55:21] kormat: take a look at https://gerrit.wikimedia.org/r/plugins/gitiles/operations/debs/chartmuseum/+/refs/heads/master/debian/rules [11:55:46] and lie about main.GitCommit I would say :) [11:56:31] ah, as a replacement for `cat RELEASE_VERSION`. that's cute. [15:28:23] heysorry lost during the daywe got SEV2 for been troubleshooting for last 2 days :(yes, we plan to move after we apply (me and Liuba) applied for citizenship.I can apply in December and get my passport for travel in 1 month, hence I can travel from Januaryslava_novak15:21:12Liuba can apply in Ferbruary or March - and probably get her [15:28:24] passport back in 1 month - hence we can pack and start to move :) we will still rent a flat in Dublin as spend some time here - since we need to get citizenship for Reginaslava_novak15:22:17so we plan to rent in Dublin and Odessa until we get passport for Regina (be tax resident in Ireland) and completely move after Regina got her passportideally, [15:28:24] we would like to work-from-anywhere after Liuba got her ukranian passport back in April (or May).slava_novak15:25:48I would like to start next year - Feb or March with the new job. (I consider to give notice >1-2 month to Sean) - so he can safely find someone.since I told him that by Jun of 2021 - I will be gone from Amazon. [15:28:27] omg [15:30:26] sorry wrong window [15:31:10] no problem :) [15:31:14] slava_novak: I'll read it here, no need to repost ;) [17:28:43] lovely: https://github.com/puppetlabs/puppetlabs_spec_helper/blob/v1.2.2/lib/puppetlabs_spec_helper/puppet_spec_helper.rb#L18-L33 [17:29:46] rotfl [17:30:18] ahaha [17:37:52] maps update - maps replicas in eqiad are currently resyncing from the postgresql master. there are new nodes in codfw that have not joined the clusters yet and won't until we finish eqiad and remedy the issues with maps2002 in codfw. maps2002 is in a bad state and needs to have its data resynced, but I dare not do that until we have finished eqiad. [17:38:21] I'm PTO tomorrow but I will stick my head in to make sure that things are stable - if there are any major issues feel free to ring/text me. [18:06:37] Anyone have more experience than I do of tilerator? it appears to be having issues in codfw and metrics have stopped rendering for it [18:18:18] tilerator in codfw is having issues at the moment, some workers are occasionally running out of memory but still serving successfully - it won't have user facing impact apart from us serving older map tiles which isn't a huge deal. if more issues come up please let wdoran know [18:21:04] <_joe_> hnowlan: I searched for documentation on tilerator and the first result is https://steamcdn-a.akamaihd.net/steam/apps/945680/header.jpg?t=1601884141 [18:22:13] I clicked...hoping for docs...was not disappointed [18:23:03] https://staging.reactiongifs.us/wp-content/uploads/2016/04/nothing_to_see_here_naked_gun.gif [18:24:31] afaik the docs for tilerator redirect to karthotherian on wikitech, which needs fixing. the github ones are pretty good though https://github.com/kartotherian/kartotherian/blob/master/packages/tilerator/README.md unfortunately doesn't give much info for this problem right now though [18:37:52] <_joe_> I was about to say, the docs that exist usually don't give you much in terms of debugging [18:38:10] <_joe_> and ooms in javascript usually need to use the node debugger [19:00:17] would someone be kind enough to remind me of the right way™ to request/create a Gerrit repository? [19:00:30] I remember being told that creating it yourself is not recommended (https://wikitech.wikimedia.org/wiki/Gerrit#Creating_new_repositories) [19:01:04] I promise to note it down this time! [19:02:38] sukhe: https://www.mediawiki.org/wiki/Gerrit/New_repositories#Step_2:_Request_a_Git_repository [19:03:28] jynus: thank you! [19:03:53] this was right above the wikitech link but I wasn't sure if I should follow it [19:05:02] I do it, normally they attended my requests very quickly [19:06:07] ok thanks, will give it a shot