2024-06-02T00:16:15 *** teepee_ is now known as teepee 2024-06-02T05:06:03 *** teepee_ is now known as teepee 2024-06-02T05:14:32 *** teepee_ is now known as teepee 2024-06-02T12:45:15 *** teepee_ is now known as teepee 2024-06-02T12:48:30 hi cboltz, please check pending changes on riesling again: 20240602124752312423 2024-06-02T12:48:53 s/ing/ing3/ 2024-06-02T12:49:13 s/pending3/pending/ 2024-06-02T12:50:13 without a /g, that's still riesling ;-) 2024-06-02T12:50:46 s/riesling/riesling3/ 2024-06-02T12:50:57 grr ^^ 2024-06-02T12:51:13 all for saving 4 characters 2024-06-02T12:51:25 ;-) 2024-06-02T13:21:38 acidsys: I wish the fix was that easy 2024-06-02T13:22:07 db:schema:dump ? 2024-06-02T13:22:27 the issue is essentially that the db migration seemingly happened outside of rails 2024-06-02T13:22:39 oh :( 2024-06-02T13:22:46 I assume somebody just created these tables by hand or something 2024-06-02T13:23:18 burn everything and start from scratch? 2024-06-02T13:23:42 I wish 2024-06-02T13:24:07 I need to figure out how rails tracks versions with postgres, because it's different 2024-06-02T13:26:04 I will work on that a bit because I'm curious myself wtf is going on 2024-06-02T13:27:27 okey, if I can be more useful than deleting files let me know 2024-06-02T13:28:25 I wonder (but not sure how risky) if db:migrate:redo could work 2024-06-02T13:31:07 ah I found it 2024-06-02T13:31:12 "select * from public.schema_migrations;" 2024-06-02T13:31:19 we are just missing a couple of versions in this 2024-06-02T13:31:41 well, public part is not necessary 2024-06-02T13:32:10 ohh cool find 2024-06-02T13:32:20 looks obvious now :P 2024-06-02T13:32:28 that it does 2024-06-02T13:32:42 I wonder if I will mess up ordering if I just shove new entries there 2024-06-02T13:35:48 https://discuss.rubyonrails.org/t/rails-7-1-insert-into-schema-migrations-version-values-sort-order-inside-db-structure-sql/84142/2 says the order should not matter 2024-06-02T13:37:19 well, I did order them correctly anyway 2024-06-02T13:37:31 I like things to be neat 2024-06-02T13:37:49 me too 2024-06-02T13:38:51 thank you! 2024-06-02T13:38:53 now riesling3 is the only minion left without a clean highstate 2024-06-02T13:40:54 tsp requires so much work to be done 2024-06-02T13:41:23 I feel 2024-06-02T13:59:45 I did the highstate on riesling3 a minute before you said it needs one ;-) (at least the timestamp of the minion log has that time) 2024-06-02T14:52:13 thank you! 2024-06-02T15:15:54 I fear there's more for cboltz: 20240602150746914842 2024-06-02T15:18:36 Jacob Michalskie: Seems the Matrix <-> Tg bridges are down 2024-06-02T15:22:32 Jacob Michalskie: It seems there is just a long delay 2024-06-02T15:22:49 might need a restart 2024-06-02T18:52:21 someone motivatd to review https://github.com/openSUSE/monitor-o-o/pull/3 ? 2024-06-02T18:55:18 acidsys: I'd be happy to review but I don't have much background information behind request. I see change in obs project (I suppose expected), monitor.opensuse.org -> alerts.infra.opensuse.org, complete change of platforms 2024-06-02T18:56:19 acidsys: It is a bit unfortunate that it is a lot of different things mixed together. Some changes would be an easy :+1: while others lack the context that would be provided in an individual commit message. 2024-06-02T18:57:10 hi both of you, thanks for checking. yes, we decommission the Icinga/Nagios setup in favor of a Prometheus stack. happy to explain further in the commit message, any particular parts I could elaborate on? 2024-06-02T18:57:25 acidsys: one thing regarding bundler. What's the target platform? Does it have bundler 2.5.X? 2024-06-02T18:57:30 the original was 2.4.X 2024-06-02T18:57:45 I recall these accidental changes costed me quite some rollbacks 2024-06-02T18:59:26 I don't know much about Bundler, it should ideally be built on jekyll.i.o.o (but currently is not), there is no bundler installed. for development I built it on Tumbleweed which required this update 2024-06-02T18:59:38 e.g. the added "'rubygem(strscan)'" and the Gemfile.lock update - is that really related to Prometheus? 2024-06-02T19:00:10 that's not related to Prometheus, I just found I cannot test my changes without these updates. I can split the Ruby parts out 2024-06-02T19:00:42 That would help readability / reviewability :-) 2024-06-02T19:01:40 rule of thumb is: if your commit message has 8 bullet points, those could be 8 commits instead. 2024-06-02T19:02:45 updated 2024-06-02T19:02:49 though it could be OK to keep the Prometheus-related changes together 2024-06-02T19:03:44 2nd commit message still mentions "Gemfile.lock" 2024-06-02T19:03:51 just noticed and removed 2024-06-02T19:04:29 and "mention additional package needed on openSUSE in README" ? 2024-06-02T19:07:09 elaborated on that 2024-06-02T19:08:15 that message now belongs to the other commit, no? 2024-06-02T19:09:31 strscan line was added in "Update Ruby stack" (latest 5cbe2661df7251b0df5e71491df01e8235facb1d) 2024-06-02T19:09:56 what I'm not so sure about is why all these platforms are getting listed (x86 would suffic for us), but I think it's not a problem either 2024-06-02T19:10:35 but it also still appears in https://github.com/openSUSE/monitor-o-o/pull/3/commits/1e4e6a95a4d0279ee6ebbbdfe4f354aa7b749a5b 2024-06-02T19:21:08 thanks, missed that, correcting soon now I fail to build it again >:( 2024-06-02T19:22:34 the changes in "_config.yml" line 4, 6, 33 could be a separate commit as it is unrelated to Prometheus. 2024-06-02T19:26:56 more of a weak preference, though. 2024-06-02T19:31:10 both done now 2024-06-02T19:32:36 and found additional packages required to build this .. apparently we need a C compiler to build our websites 2024-06-02T19:34:43 or a C-compiler for bundler to build required stuff 2024-06-02T19:35:29 What about the IRC-related changes? Could be its own commit, too. 2024-06-02T19:53:11 *** teepee_ is now known as teepee 2024-06-02T19:56:24 good idea 2024-06-02T19:57:24 done and also used the opportunity to reference the other channel