From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "J.P." Newsgroups: gmane.emacs.bugs,gmane.emacs.erc.general Subject: bug#60936: 30.0.50; ERC >5.5: Add erc-fill style based on visual-line-mode Date: Wed, 16 Aug 2023 07:28:26 -0700 Message-ID: <87msyrcb91.fsf@neverwas.me> References: <87tu0nao77.fsf@neverwas.me> <87edkcmflq.fsf__21602.8587006562$1691592938$gmane$org@neverwas.me> <87jzu4upl9.fsf@gmx.de> <87v8dgh0af.fsf@neverwas.me> <87sf8kuvxr.fsf@gmx.de> <87leecuuqu.fsf@gmx.de> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32055"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: 60936@debbugs.gnu.org, emacs-erc@gnu.org To: Michael Albinus Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Aug 16 16:29:35 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1qWHWh-000889-CH for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 16 Aug 2023 16:29:35 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qWHWU-0003Ya-UR; Wed, 16 Aug 2023 10:29:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qWHWC-0003P3-7y for bug-gnu-emacs@gnu.org; Wed, 16 Aug 2023 10:29:08 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qWHWA-0004Ws-L4 for bug-gnu-emacs@gnu.org; Wed, 16 Aug 2023 10:29:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qWHWA-0004KJ-HE for bug-gnu-emacs@gnu.org; Wed, 16 Aug 2023 10:29:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "J.P." Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 16 Aug 2023 14:29:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 60936 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 60936-submit@debbugs.gnu.org id=B60936.169219611916587 (code B ref 60936); Wed, 16 Aug 2023 14:29:02 +0000 Original-Received: (at 60936) by debbugs.gnu.org; 16 Aug 2023 14:28:39 +0000 Original-Received: from localhost ([127.0.0.1]:41790 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qWHVm-0004JT-Lv for submit@debbugs.gnu.org; Wed, 16 Aug 2023 10:28:39 -0400 Original-Received: from mail-108-mta86.mxroute.com ([136.175.108.86]:34383) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qWHVj-0004JH-7U for 60936@debbugs.gnu.org; Wed, 16 Aug 2023 10:28:36 -0400 Original-Received: from mail-111-mta2.mxroute.com ([136.175.111.2] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta86.mxroute.com (ZoneMTA) with ESMTPSA id 189febf7cf5000d7b6.001 for <60936@debbugs.gnu.org> (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Wed, 16 Aug 2023 14:28:29 +0000 X-Zone-Loop: a8ea7983d49d7a49c4db9972e68483e404d334ab02d8 X-Originating-IP: [136.175.111.2] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=neverwas.me ; s=x; h=Content-Type:MIME-Version:Message-ID:Date:References:In-Reply-To: Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=38dGZHBHSag3G3UmMI99vN/mzyzBvINNk5o5DKN59L0=; b=FKjGoGQNthb3wARwn8fEZTZO4E cVJbW2tdTVV137xXIrz0lNPCJQa5wROPPjdVNtTrJc0pOUZrAN8fPMinmE/5NEoyRgU2cp6rE8+Pn +9e176QpfSPx4Blr1nA6d+fgUZHdrhXClCXh315Qdf8KvADsPrDd2gmaABMTk1xsiNabJc/vMPMlB SeBBdUJluh/cyvex6pRvk6F0DXMvBeaMMENDIGi4RX7zXAk7edGHsBrFUbmzD5g51oSrP46SMqYLV mtKFlSezQ9KpFis6zlqG/I8hyx2+nMzOPm/K1rJOTjVVIklYsl3Vpero0j/OYztL6D8ceE/C/YD/q IJchsoJQ==; In-Reply-To: <87leecuuqu.fsf@gmx.de> (Michael Albinus's message of "Tue, 15 Aug 2023 18:37:45 +0200") X-Authenticated-Id: masked@neverwas.me X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:267593 gmane.emacs.erc.general:2233 Archived-At: Michael Albinus writes: > Michael Albinus writes: > >> I've enabled the /metrics endpoint on emba. This requires a restart of >> gitlab, which I haven't done. Should happen next time, when gitlab >> patches are installed (which is not my responsibility). > > Hmm. I've just read . It tells us > > Measure reliability and stability with metrics (removed) > > This feature was deprecated in GitLab 14.7 and removed in 16.0. > > So it might work ATM (we're using GitLab CE 13.12.15), but it might > disappear in the future. Hi Michael. This deprecation notice appears to be about GitLab's metrics feature, which they describe as a managed Prometheus instance and integrated dashboard solution for their enterprise product. Apparently, they're replacing that with a full observability offering. In case you're curious, they also say [1]: This deprecation does not include: - Deprecating alerts for Prometheus - Capabilities that GitLab comes with that allow operators of GitLab to retrieve metrics from those instances [2] It's the second bullet I was referring to initially, which allows external Prometheus instances to poll the /-/metrics endpoint if exposed. But to be of any use, those instances would need their IP addresses whitelisted. Additionally, we'd need a "node exporter" [3] process running on the same host to provide intel on system-resource consumption. In the end, this is probably too involved to be worth anyone's while. So, I guess you can probably just revert whatever change you made to the configuration. Thanks anyway and please pardon the distraction. [1] https://gitlab.com/gitlab-org/gitlab/-/issues/346541 [2] https://docs.gitlab.com/ee/administration/monitoring/prometheus/gitlab_metrics.html [3] https://prometheus.io/docs/guides/node-exporter/