Postfix implementation

I am trying to add this to docker-mailserver which uses postfix.
See https://github.com/trusteddomainproject/OpenARC/issues/123 for the previous discussion.
I have a first attempt. See here: https://github.com/tomav/docker-mailserver/issues/1346#issuecomment-570834266
However, it seems like OpenArc is not doing anything and/or never being triggered. Any ideas what I am missing?

lukas skrev den 2020-01-05 02:17:

I am trying to add this to docker-mailserver [1] which uses postfix.
See #123 [2] for the previous discussion.
I have a first attempt. See here: tomav/docker-mailserver#1346
(comment) [3]
However, it seems like OpenArc is not doing anything and/or never
being triggered. Any ideas what I am missing?

run dmarc after arc, so dmarc can validate arc, for this to work use
opendmarc from github, i tryed build openarc from github but it
segfaults, very helpfull :(
non_smtp_milters does not make sense to call openarc milter when its
origin sender and dkim signed
cut long story openarc are made only for maillists that breaks dkim

run dmarc after arc, so dmarc can validate arc, for this to work use
opendmarc from github

You mean like this:
milter_protocol = 6
milter_default_action = accept
dkim_milter = inet:localhost:8891
dmarc_milter = inet:localhost:8893
arc_milter = inet:localhost:8894
smtpd_milters = $dkim_milter,$arc_milter,$dmarc_milter
non_smtpd_milters = $dkim_milter

i tryed build openarc from github but it segfaults, very helpfull :(

Works for me on arch linux as well as in a Debian 9 docker image

cut long story openarc are made only for maillists that breaks dkim

What do you mean by that?
I am forwarding emails from my mailserver to gmail, so I need ARC to resign the chain and make Gmail not rejecting mails from senders with strict DMARC policies.
See: https://github.com/tomav/docker-mailserver/issues/1346

Alright. It seems like it is working. Checking on a message forwarded to google, I can see this:
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578189874; cv=none; b=[.......]
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578189874; c=relaxed/simple; bh=[...]; h=Received-SPF:MIME-Version:Message-ID:Date:From:To:Subject:
	 Content-Type:Content-Transfer-Encoding; b=[.......]
ARC-Authentication-Results: i=1; mx0.domain.com; arc=none

lukas skrev den 2020-01-05 02:50:

smtpd_milters = $dkim_milter,$arc_milter,$dmarc_milter
non_smtpd_milters = $dkim_milter

yes

i tryed build openarc from github but it segfaults, very helpfull :(
Works for me on arch linux as well as in a Debian 9 docker image

then its not raw source from github, so i must find real tarballs
please link to the debian sources if it works

cut long story openarc are made only for maillists that breaks dkim
What do you mean by that?

if none breaked dkim then openarc is completely unnedded

I am forwarding emails from my mailserver to gmail,

forwarding does not break dkim, but maillists does

so I need ARC to
resign the chain and make Gmail

so you see gmail reject dkim signed mails, if you dont arc sealing it ?

not rejecting mails from senders with
strict DMARC policies.

strict is irelevant if dkim is not breaked

then its not raw source from github, so i must find real tarballs
please link to the debian sources if it works

I do not understand. I am building from master branch. I don't know what you mean by debian sources.

forwarding does not break dkim, but maillists does

There is a lot of people experiencing something different (including me). Just follow the links I posted.

And when you check the headers as seen on gmail, do you see the ARC chain
continued with i=2 and the AAR listing cv=pass for your i=1 set?
--Kurt
On Sat, Jan 4, 2020, 18:21 lukas<EMAIL_ADDRESS>wrote:

Alright. It seems like it is working. Checking on a message forwarded to
google, I can see this:
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578189874; cv=none; b=[.......]
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578189874; c=relaxed/simple; bh=[...]; h=Received-SPF:MIME-Version:Message-ID:Date:From:To:Subject:
Content-Type:Content-Transfer-Encoding; b=[.......]
ARC-Authentication-Results: i=1; mx0.domain.com; arc=none
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SLO7Q7L3PQ4R7RE6NLQ4E74DA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDEW4Y#issuecomment-570837875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SMZ462WC5BD3GWPQKDQ4E74DANCNFSM4KCY24YA
.

Hi Kurt
Nope... I do not see any i=2 :( Also, I see arc=fail (DNS record missing)
So I suppose, it is not working.
But it seems like it is doing something. I mean, I can clearly see the difference between using OpenArc and not using it.
Is that a configuration issue or a bug?

The arc=fail with a missing DNS record pretty well explains the problem.
Did you publish the public key for your ARC signing?
On Sat, Jan 4, 2020, 18:54 lukas<EMAIL_ADDRESS>wrote:

Hi Kurt
Nope... I do not see any i=2 :( Also, I see arc=fail (DNS record missing)
So I suppose, it is not working.
But it seems like it is doing something. I mean, I can clearly see the
difference between using OpenArc and not using it.
Is that a configuration issue or a bug?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SKKG45L25NMJDFWT23Q4FDV5A5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDFNZQ#issuecomment-570840806,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SLNRRLZ4UZQAPRI4SDQ4FDV5ANCNFSM4KCY24YA
.

Nope, I don't think so. To be honest I have only little idea what I am doing here... Where can/should I publish it?
And which documentation did I not read? :)

You need to publish the public key for ARC just like you do for DKIM - and
in the similar path with the selector that you are using for the sealing
On Sat, Jan 4, 2020, 19:04 lukas<EMAIL_ADDRESS>wrote:

Nope, I don't think so. To be honest I have only little idea what I am
doing here... Where can/should I publish it?
And which documentation did I not read? :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SOF5YIGTI6AZSFNFVTQ4FE4NA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDF5KY#issuecomment-570842795,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SIB7F3R44TJUNMB4PDQ4FE4NANCNFSM4KCY24YA
.

Like this?
v=ARC1; h=sha256; k=rsa; p=[....]

And what is the domain record? Does that have to do with the selector?
For DKIM I have:
mail._domainkey.domain.com

And where is the docs? Sorry, I am really lost.

In the header example you cited above, the selector is 201808 (s=). You
would publish the ARC sealing key at 201808._domainkey.. The ARC
selector can, but does not need to be, different from the DKIM selector.
--Kurt
On Sat, Jan 4, 2020, 19:18 lukas<EMAIL_ADDRESS>wrote:

Like this?
v=ARC1; h=sha256; k=rsa; p=[....]
And what is the domain record? Does that have to do with the selector?
For DKIM I have:
mail._domainkey.domain.com
And where is the docs? Sorry, I am really lost.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SMUZ4MFNJNW3EACD5LQ4FGRJA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDGSOY#issuecomment-570845499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SJZMCFYYRS6TFWGRULQ4FGRJANCNFSM4KCY24YA
.

Does that mean if I use the same selector for ARC and DKIM as well as the same keys, I can use only one TXT record for both? Or do I need to replace  v=DKIM1 with v=ARC1?

You should be able to use just one record. You can check to see what Google
publishes as a reference (I'm working on dinner so I don't have a real
keyboard right now).
On Sat, Jan 4, 2020, 19:45 lukas<EMAIL_ADDRESS>wrote:

Does that mean if I use the same selector for ARC and DKIM as well as the
same keys, I can use only one TXT record for both? Or do I need to replace
v=DKIM1 with v=ARC1?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SPGQATEDP2HPP4YUX3Q4FJVDA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDHUSA#issuecomment-570849864,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SMCT63KBDDLLPEGEATQ4FJVDANCNFSM4KCY24YA
.

I read in another thread, that I can only use one key for one server. Since I have multiple domains running, I am using the keys of the primary domain. Reusing the record will not work then. (DKIM uses one key each domain)
I checked googles record:
arc-20160816._domainkey.google.com. 8 IN TXT	"k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA1Lztpxs7yUxQEsbDFhjMc9kZVZu5P/COYEUIX4B39IL4SXAbv4viIlT9E6F6iZmTh1go7+9WQLywwgwjXMJx/Dz0RgMoPeyp5NRy4l320DPYibNqVMWa5" "iQ2WiImQC0en1O9uhLLvzaSZJ03fvGmCo9jMo0GwKzLNe14xMgn/px2L5N/3IKlKX4bqUAJTUt8L993ZlWzvgMnSFSt8B+euSKSrtAiopdy4r1yO4eN5goBASrGW0eLQc1lYouNvCrcTQpos4/GEAqiGzpqueJLmBfOO4clNvVvpPkvQs2BHw9I9LmIjaMxTNGxkGBRaP3utDiKXXqu1K+LRzl0HCNSdQIDAQAB"

And set mine accordingly:
201808._domainkey.lukius.de. 86400 IN	TXT	"k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoY59f+sniYUd720BOSiCPcdYIij4/gH+QJSyQ2b3WjynjDy5+TriljHfDI9Fo3bngJFbzWDXyX" "wq142WWrFybs8XBZNcOZf+wADqYcqCE76jluhyt/R4QItsNmb62Y0cy+AdHNnxVe8jfS5sFngYaO78PQsBpj8dGs2L1g0ys2e7D0PMcrYEvh8RAa530wPMS0r+aKLbT" "quC8qWcUtZvoRrWl4BOSlJZPIDRqAQXT9PtBFMYL6mwM/KoqUC9RCQD79SLqsvO31L06OuGUwNZBqYtGak2xhapbWuyU2bLmdofDJQa47Y9O5bwwTU5utpk6Ss23llN" "lPrQNICj9pfoWwIDAQAB"

Now I am getting a arc=fail (dns record malformed). Something must still be missing.
Bon appetit! :)

Alright. I think I got it now. @kurta what do you think? This is a forwarded message to gmail. Does this look like OpenARC proper signed the chain and everything is good?
Does i=2 mean that the chain is 2 steps long?
``
0 = sender
1 = my email server
2 = gmail

ARC-Seal: i=2; a=rsa-sha256; t=1578238460; cv=pass;
d=google.com; s=arc-20160816;
b=Ect8OKiv/DclvqS8CdYEA0dzeqe0IrxsxDGhy+aIqxtDTVhFsQaHHbENfEqC3hxxOz
AXwtTv51Ag43dBE9bg2vNCbhOGb4+3JnOFtPg9vXhF7FpwRbxlGXkPTwvAX7z8u4gzV/
tc/T5ydmk4HqDhXOj4vq1V7icApTUrQf+7eJD1t1yVCds78VxxX7VIkGm6ieQ1jJ94sF
n2DMIqtWAD3TRYzucbJA5GxhsNxWTzimaWtLBg+dOY97T39y8ZNriMknbWOLalwaYefo
UZUKEczxrXb3gGzy2UZscS1qOsS0jraBAGT/iVvvMNI8odTiPWCIMl5uyfMHVzrEQelx
Bj0w==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=content-transfer-encoding:subject:to:from:date:message-id
:mime-version:arc-filter;
bh=pwCRxelulesFS4CeB7c7JkXr7yW4Mx6hmFEr6sYnDiQ=;
b=FwltbwdAOAVvQeJIUscD/6bV5rjxxqmDWuiWjJkWA4W+illmyBjU+cwAHppgQxu4ME
Jq1mu/hJIjbl/nT60kC9cIuWIyOx/fPBSW4knfO/uz6WskBhdV87x6lCVKTxbCARdo8G
IfxS+9IbTdyW21O6dolPX3i5UA/sTwRSM0TM2FKLP1/afh6LFcTgxqGhbf5nZ29lhPXj
B+vIy9uCqjTsklTOQ3U3D9D9ZkEXR/s3TWFic9imHlV2i0MBBfocaMH0R3qmMjiuxfIO
m0y7tsh0TAPqHogDanI6R8hGkXTTV5V8faJGdh9g4oua8F9FHa3NtysbyMitdU+dfrrS
C48g==
ARC-Authentication-Results: i=2; mx.google.com;
arc=pass (i=1);
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>Return-Path<EMAIL_ADDRESS>Received: from mx0.domain.com (mx0.domain.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id i14si51706513wrr.238.2<IP_ADDRESS>.34.19
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Sun, 05 Jan 2020 07:34:20 -0800 (PST)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
arc=pass (i=1);
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>X-Virus-Scanned: Yes
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=<IP_ADDRESS>; helo=ismyemailworking.com<EMAIL_ADDRESS>receiver=
Authentication-Results: mx0.domain.com; dmarc=none (p=none dis=none) header.from=ismyemailworking.com
ARC-Filter: OpenARC Filter v0.1.0 mx0.domain.com D17BA60733
Authentication-Results: mx0.domain.com; arc=none
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578238458; cv=none; b=J0U8fGHFuxqnrdq276+3KjUcN6/WrNqIZHULDN4UhK2gw77KnV/RQnzbIkjne7d6VKoAalK08Zw+extVf/BXtKzBdACxgvZV0O7V3/k8EtM43d65jVv/4qAX7mwtXYxkiBEG4MHE9bhDdYfFuoBhUtf+MEESDQQQEMoEift1TbASYECvRI4DBSMl9KVRjHrpIznzc7ZrZbcPhvo1mIiBGezK/wXqTb5ZWpTMrcgS6l3Jlj75+8X7eB0yWNS1naLgUrZamrZtpi73qPry/Rckdqt/YOXfCrx/ZeYMB8LErjE9JzqT56jsqjjXuLnVy3C5fceRxc+YqHTD+0hc7o84sQ==
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578238458; c=relaxed/simple; bh=pwCRxelulesFS4CeB7c7JkXr7yW4Mx6hmFEr6sYnDiQ=; h=Received-SPF:MIME-Version:Message-ID:Date:From:To:Subject:
Content-Type:Content-Transfer-Encoding; b=Mll/jlcyKqf8SvRnBvX9WhaTR7Z5KtOiDPJHoLnIhRZsn21kJM9U2hunwGHFWHEz7cPCF4vFcnnff9z4Kys6D7LI540K0vG6idutiHMna6201Pu2E+aoaICeVZ/17AUOr7bFYklA3hjeDGmahog9YDq0ZmfWK4bl9Jnw3Q2XB6d+iTHTbrYEBkbzYUzwMJgGOhkwy68dJQ9vYMH2Ibss0wvcaZiRaxpiw9ie3/6kk1jO3tFf2p/8TaowXDTKfw1tzqVn4x7ght7zCm9A2JlCje5f/UAk3BZNkFJlOY3DfeX6+ByOfN+N40xG5j5y81pl4wZddKYwh5yC6ZHp//RSmQ==
ARC-Authentication-Results: i=1; mx0.domain.com; arc=none
Received: from IsMyEmailWorking.com (ismyemailworking.com [<IP_ADDRESS>]) by mx0.domain.com (Postfix) with ESMTP id D17BA60733 for<EMAIL_ADDRESS>Sun,
5 Jan 2020 15:34:17 +0000 (UTC)

Yes, the ARC chain looks good. I'm surprised that there are no DKIM
signatures on the message but that's not critical.
--Kurt
On Sun, Jan 5, 2020, 07:44 lukas<EMAIL_ADDRESS>wrote:

Alright. I think I got it now. @kurta https://github.com/kurta what do
you think? This is a forwarded message to gmail. Does this look like
OpenARC proper signed the chain and everything is good?
Does i=2 mean that the chain is 2 steps long?
``
0 = sender
1 = my email server
2 = gmail
ARC-Seal: i=2; a=rsa-sha256; t=1578238460; cv=pass;
d=google.com; s=arc-20160816;
b=Ect8OKiv/DclvqS8CdYEA0dzeqe0IrxsxDGhy+aIqxtDTVhFsQaHHbENfEqC3hxxOz
AXwtTv51Ag43dBE9bg2vNCbhOGb4+3JnOFtPg9vXhF7FpwRbxlGXkPTwvAX7z8u4gzV/
tc/T5ydmk4HqDhXOj4vq1V7icApTUrQf+7eJD1t1yVCds78VxxX7VIkGm6ieQ1jJ94sF
n2DMIqtWAD3TRYzucbJA5GxhsNxWTzimaWtLBg+dOY97T39y8ZNriMknbWOLalwaYefo
UZUKEczxrXb3gGzy2UZscS1qOsS0jraBAGT/iVvvMNI8odTiPWCIMl5uyfMHVzrEQelx
Bj0w==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816;
h=content-transfer-encoding:subject:to:from📅message-id
:mime-version:arc-filter;
bh=pwCRxelulesFS4CeB7c7JkXr7yW4Mx6hmFEr6sYnDiQ=;
b=FwltbwdAOAVvQeJIUscD/6bV5rjxxqmDWuiWjJkWA4W+illmyBjU+cwAHppgQxu4ME
Jq1mu/hJIjbl/nT60kC9cIuWIyOx/fPBSW4knfO/uz6WskBhdV87x6lCVKTxbCARdo8G
IfxS+9IbTdyW21O6dolPX3i5UA/sTwRSM0TM2FKLP1/afh6LFcTgxqGhbf5nZ29lhPXj
B+vIy9uCqjTsklTOQ3U3D9D9ZkEXR/s3TWFic9imHlV2i0MBBfocaMH0R3qmMjiuxfIO
m0y7tsh0TAPqHogDanI6R8hGkXTTV5V8faJGdh9g4oua8F9FHa3NtysbyMitdU+dfrrS
C48g==
ARC-Authentication-Results: i=2; mx.google.com;
arc=pass (i=1);
spf=pass (google.com: domain of srs0=scn3=22=ismyemailworking.com=
<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender)
<EMAIL_ADDRESS>Return-Path<EMAIL_ADDRESS>Received: from mx0.domain.com (mx0.domain.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id i14si51706513wrr.238.2<IP_ADDRESS>.34.19
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Sun, 05 Jan 2020 07:34:20 -0800 (PST)
Received-SPF: pass (google.com: domain of srs0=scn3=22=
<EMAIL_ADDRESS>designates <IP_ADDRESS> as
permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
arc=pass (i=1);
spf=pass (google.com: domain of srs0=scn3=22=ismyemailworking.com=
<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender)
<EMAIL_ADDRESS>X-Virus-Scanned: Yes
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=<IP_ADDRESS>;
helo=ismyemailworking.com<EMAIL_ADDRESS>receiver=
Authentication-Results: mx0.domain.com; dmarc=none (p=none dis=none)
header.from=ismyemailworking.com
ARC-Filter: OpenARC Filter v0.1.0 mx0.domain.com D17BA60733
Authentication-Results: mx0.domain.com; arc=none
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578238458;
cv=none;
b=J0U8fGHFuxqnrdq276+3KjUcN6/WrNqIZHULDN4UhK2gw77KnV/RQnzbIkjne7d6VKoAalK08Zw+extVf/BXtKzBdACxgvZV0O7V3/k8EtM43d65jVv/4qAX7mwtXYxkiBEG4MHE9bhDdYfFuoBhUtf+MEESDQQQEMoEift1TbASYECvRI4DBSMl9KVRjHrpIznzc7ZrZbcPhvo1mIiBGezK/wXqTb5ZWpTMrcgS6l3Jlj75+8X7eB0yWNS1naLgUrZamrZtpi73qPry/Rckdqt/YOXfCrx/ZeYMB8LErjE9JzqT56jsqjjXuLnVy3C5fceRxc+YqHTD+0hc7o84sQ==
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808;
t=1578238458; c=relaxed/simple;
bh=pwCRxelulesFS4CeB7c7JkXr7yW4Mx6hmFEr6sYnDiQ=;
h=Received-SPF:MIME-Version:Message-ID:Date:From:To:Subject:
Content-Type:Content-Transfer-Encoding;
b=Mll/jlcyKqf8SvRnBvX9WhaTR7Z5KtOiDPJHoLnIhRZsn21kJM9U2hunwGHFWHEz7cPCF4vFcnnff9z4Kys6D7LI540K0vG6idutiHMna6201Pu2E+aoaICeVZ/17AUOr7bFYklA3hjeDGmahog9YDq0ZmfWK4bl9Jnw3Q2XB6d+iTHTbrYEBkbzYUzwMJgGOhkwy68dJQ9vYMH2Ibss0wvcaZiRaxpiw9ie3/6kk1jO3tFf2p/8TaowXDTKfw1tzqVn4x7ght7zCm9A2JlCje5f/UAk3BZNkFJlOY3DfeX6+ByOfN+N40xG5j5y81pl4wZddKYwh5yC6ZHp//RSmQ==
ARC-Authentication-Results: i=1; mx0.domain.com; arc=none
Received: from IsMyEmailWorking.com (ismyemailworking.com
[<IP_ADDRESS>]) by mx0.domain.com (Postfix) with ESMTP id D17BA60733
for<EMAIL_ADDRESS>Sun,
5 Jan 2020 15:34:17 +0000 (UTC)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SNP5N75ZFZUH27W6JLQ4H55TA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIDZRRI#issuecomment-570923205,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SNPZDL5FD2DFA3H5F3Q4H55TANCNFSM4KCY24YA
.

I think the issue with the missing DKIM is that ismymailworking.com does not use DKIM for whatever reason. Here is a header from a github-mail forwarded to my GMail:
Delivered-To<EMAIL_ADDRESS>Received: by 2002:a67:ce12:0:0:0:0:0 with SMTP id s18csp20652289vsl;
        Sun, 5 Jan 2020 08:44:54 -0800 (PST)
X-Google-Smtp-Source: APXvYqyxvf4jB0mBR6igvjdHLd1ZfZK+LTIalWYiDEujK/a/uEggQYXSt1y7zqMdMrTM+/qD8bYo
X-Received: by 2002:a5d:5704:: with SMTP id a4mr97989661wrv.198.1578242694748;
        Sun, 05 Jan 2020 08:44:54 -0800 (PST)
ARC-Seal: i=2; a=rsa-sha256; t=1578242694; cv=pass;
        d=google.com; s=arc-20160816;
        b=w80imn2lasBKiX1jJbV4VIAoOPPLIJtezgcQKkIb6YPyKiWlGfGEJJJ1+yX4rx4kUS
         hpK/PKI8EHZzGQnSIB073Ho4PXeZf0w1VxJ2IIMdJdN9Xps/XKP3gkEVNmlllC0Ph/9D
         NQ14Rt05nO3eCETGiBfnO8kSCherteBEk8rODnFIBLy82nZR72nANQkixUIcBuhMeyeS
         UUl+vZnWsT+M5ppAa3B4noi2Amr92WXVp+NPvk8RRqP2r9vFvY9ReqRwN0SPpVwbeITo
         btDcgrtxd8XYDfZqfb/nUV9oEzj+dmHq8cYExx85ggN2D20GEHXW7ZAxOWQyJj2d7Ya6
         FTYA==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-unsubscribe:list-post:list-archive:list-id:precedence
         :content-transfer-encoding:mime-version:subject:references
         :in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
         :arc-filter;
        bh=2b7U3dMs52xPA8n8LErBrTLrsTnfHHdnGRtlbTpSPXo=;
        b=WJAa97GdiLGB7PHBvGTmySnEHFmAgjm4AaPHvMegHjQxEtvWAQ14AVJRqpIqHAk6E9
         32rusXgWk9ogJ/hoqCw83FucIUIMUmWHxZsfz9ynbwDY44+BcKnB65Y1gXNlYUA5gU07
         TqB5WTfyVkuP1cTNLkYvBdnX2j/azcZqWlrvua4oZdnuJHISlAvtvnKBO0wA8ONzuZsK
         wH+7kK2Uo+6diZSmMDC4/rRld90Veh3u9WrRMZ9AqmBohS5DuEUYPEPeDAWXQFpUQG0x
         CeYNtqB5vILTI0U0mN+zH4e/HLQvX18pff4MmIaIkT8CcyQzHxk9FQBLLmuOi78sTpId
         /p3A==
ARC-Authentication-Results: i=2; mx.google.com;
       dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=MGBfrKg6;
       arc=pass (i=1 dkim=pass dkdomain=github.com);
       spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Return-Path<EMAIL_ADDRESS>Received: from mx0.domain.com (mx0.domain.com. [<IP_ADDRESS>])
        by mx.google.com with ESMTPS id q18si16300906wmg.171.2<IP_ADDRESS>.44.54
        for<EMAIL_ADDRESS>        (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
        Sun, 05 Jan 2020 08:44:54 -0800 (PST)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
       dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=MGBfrKg6;
       arc=pass (i=1 dkim=pass dkdomain=github.com);
       spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
X-Virus-Scanned: Yes
X-Spam-Flag: NO
X-Spam-Score: 0.152
X-Spam-Level:
X-Spam-Status: No, score=0.152 tagged_above=-999 required=6.2 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SURBL_BLOCKED=1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=<IP_ADDRESS>; helo=out-20.smtp.github.com<EMAIL_ADDRESS>receiver=<UNKNOWN>
Authentication-Results: mx0.domain.com; dmarc=pass (p=none dis=none) header.from=github.com
ARC-Filter: OpenARC Filter v0.1.0 mx0.domain.com 5F88560736
Authentication-Results: mx0.domain.com; arc=none
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578242692; cv=none; b=Gxz/UoQ/cVYyPpEXRkDqIqJYa174Qts8kUmKjizrNZ6rl/ng9F263wHQwu2DIlqOyrP5mgPhTcpXxDVEOhQ52SRFfh79Iw527gWxP+KdBSHxjC3CfBUrpBvkR4S7DT2zORGxaucbpYYhoS2W83G9q8N2rxoOQix/jbtTNL1nBV/Kc3zmzFBGku/QOgFFI7IvAnygbmBmER/HIN57RRw8WdXsGFVbBiD9JIGMqE92TP7wPqBFRuBiKFp9h3ZywQkAOG8CPYn641koFtIJw2k1yNoxyEBaC86m+WGlmKLspwLF+njekkRSQT1RqCpaHd4W85NiGA2vu/h65pYmn84oaA==
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578242692; c=relaxed/simple; bh=OeHAFYgpfq7hdCzWfH7qcEpoznna+XievF6VcPWm9nk=; h=Received-SPF:Received:DKIM-Signature:Date:From:Reply-To:To:Cc:
	 Message-ID:In-Reply-To:References:Subject:Mime-Version:
	 Content-Type:Content-Transfer-Encoding:Precedence:X-GitHub-Sender:
	 X-GitHub-Recipient:X-GitHub-Reason:List-ID:List-Archive:List-Post:
	 List-Unsubscribe:X-Auto-Response-Suppress:
	 X-GitHub-Recipient-Address; b=DNYPK11+PTPjy9gAEDA6Ohv/ZuIShlLyKuiwyXLk/xT/ud4rbluYWXYj5xCVUh4A2YyakVg9lFsLvi4uwlTEaQmnl+juufvHKHQIfj3NQzH0JLOsiQiy2LDNBfHuTpYIiobyG0OrfilOstwnXwMgp5jy9M//ZfW6aYQ7mweIROzUay+tYmaV0BzV9OaPzrRP5rq66/exRudpXVmpLboiwKQ+6hJOiYNPkHeTD3sqy25yqAfEbEUT3aaikVTK+84I9nvgTix7o98dtTeat7D0rmV0fm2vzIuDhjd0H9cBSpLu4Gc/WJKhSq5uPWOKOUXj6w0njlij1h09IBkCLURZXw==
ARC-Authentication-Results: i=1; mx0.domain.com; dkim=pass (1024-bit key; unprotected) header.d=github.com<EMAIL_ADDRESS>header.b=MGBfrKg6; dkim-atps=neutral; arc=none
Authentication-Results: mx0.domain.com; dkim=pass (1024-bit key; unprotected) header.d=github.com<EMAIL_ADDRESS>header.b="MGBfrKg6"; dkim-atps=neutral
Received: from out-20.smtp.github.com (out-20.smtp.github.com [<IP_ADDRESS>]) by mx0.domain.com (Postfix) with ESMTPS id 5F88560736 for<EMAIL_ADDRESS>Sun,
  5 Jan 2020 16:44:52 +0000 (UTC)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [<IP_ADDRESS>]) by smtp.github.com (Postfix) with ESMTP id 240778C006D for<EMAIL_ADDRESS>Sun,
  5 Jan 2020 08:44:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1578242685; bh=2b7U3dMs52xPA8n8LErBrTLrsTnfHHdnGRtlbTpSPXo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
	 List-Archive:List-Post:List-Unsubscribe:From; b=MGBfrKg6xqJYkiUEeWu4xGmQoT9B8FF3VBqieeezmORCcz/Z0fdpmqOSD5J/p/DgZ
	 2WTcJOi8/2IYtHElmKfyGwrjNCUPdLX+5R0AnNbquLvPeE1f/HNCzdPKoaGYuS5g1V
	 9POlREWMk/2amPNL02bFOQEGG+qd79QJJdo5B8rw=
Date: Sun, 05 Jan 2020 08:44:45 -0800
From: kurta<EMAIL_ADDRESS>Reply-To: "trusteddomainproject/OpenARC"<EMAIL_ADDRESS>To: "trusteddomainproject/OpenARC"<EMAIL_ADDRESS>Cc: lukas<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [trusteddomainproject/OpenARC] Postfix implementation (#124)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e12127d14d92_23e43ff2adacd96c527667"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kurta
X-GitHub-Recipient: mindrunner
X-GitHub-Reason: author
List-ID: trusteddomainproject/OpenARC <OpenARC.trusteddomainproject.github.com>
List-Archive: https://github.com/trusteddomainproject/OpenARC
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS><https://github.com/notifications/unsubscribe/AAKZDJWRBNIM2LGPQWHY77TQ4IE73ANCNFSM4KCY24YA>
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>

But your forwarder can add its own DKIM signature. I see that it is doing
SRS to address the SPF forwarding breakage.
On Sun, Jan 5, 2020, 12:43 lukas<EMAIL_ADDRESS>wrote:

I think the issue with the missing DKIM is that ismymailworking.com does
not use DKIM for whatever reason. Here is a header from a github-mail
forwarded to my GMail:
Delivered-To<EMAIL_ADDRESS>Received: by 2002:a67:ce12:0:0:0:0:0 with SMTP id s18csp20652289vsl;
Sun, 5 Jan 2020 08:44:54 -0800 (PST)
X-Google-Smtp-Source: APXvYqyxvf4jB0mBR6igvjdHLd1ZfZK+LTIalWYiDEujK/a/uEggQYXSt1y7zqMdMrTM+/qD8bYo
X-Received: by 2002:a5d:5704:: with SMTP id a4mr97989661wrv.198.1578242694748;
Sun, 05 Jan 2020 08:44:54 -0800 (PST)
ARC-Seal: i=2; a=rsa-sha256; t=1578242694; cv=pass;
d=google.com; s=arc-20160816;
b=w80imn2lasBKiX1jJbV4VIAoOPPLIJtezgcQKkIb6YPyKiWlGfGEJJJ1+yX4rx4kUS
hpK/PKI8EHZzGQnSIB073Ho4PXeZf0w1VxJ2IIMdJdN9Xps/XKP3gkEVNmlllC0Ph/9D
NQ14Rt05nO3eCETGiBfnO8kSCherteBEk8rODnFIBLy82nZR72nANQkixUIcBuhMeyeS
UUl+vZnWsT+M5ppAa3B4noi2Amr92WXVp+NPvk8RRqP2r9vFvY9ReqRwN0SPpVwbeITo
btDcgrtxd8XYDfZqfb/nUV9oEzj+dmHq8cYExx85ggN2D20GEHXW7ZAxOWQyJj2d7Ya6
FTYA==
ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:arc-filter;
bh=2b7U3dMs52xPA8n8LErBrTLrsTnfHHdnGRtlbTpSPXo=;
b=WJAa97GdiLGB7PHBvGTmySnEHFmAgjm4AaPHvMegHjQxEtvWAQ14AVJRqpIqHAk6E9
32rusXgWk9ogJ/hoqCw83FucIUIMUmWHxZsfz9ynbwDY44+BcKnB65Y1gXNlYUA5gU07
TqB5WTfyVkuP1cTNLkYvBdnX2j/azcZqWlrvua4oZdnuJHISlAvtvnKBO0wA8ONzuZsK
wH+7kK2Uo+6diZSmMDC4/rRld90Veh3u9WrRMZ9AqmBohS5DuEUYPEPeDAWXQFpUQG0x
CeYNtqB5vILTI0U0mN+zH4e/HLQvX18pff4MmIaIkT8CcyQzHxk9FQBLLmuOi78sTpId
/p3A==
ARC-Authentication-Results: i=2; mx.google.com;
dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=MGBfrKg6;
arc=pass (i=1 dkim=pass dkdomain=github.com);
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Return-Path<EMAIL_ADDRESS>Received: from mx0.domain.com (mx0.domain.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id q18si16300906wmg.171.2<IP_ADDRESS>.44.54
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256);
Sun, 05 Jan 2020 08:44:54 -0800 (PST)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=MGBfrKg6;
arc=pass (i=1 dkim=pass dkdomain=github.com);
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
X-Virus-Scanned: Yes
X-Spam-Flag: NO
X-Spam-Score: 0.152
X-Spam-Level:
X-Spam-Status: No, score=0.152 tagged_above=-999 required=6.2 tests=[DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, SURBL_BLOCKED=1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=<IP_ADDRESS>; helo=out-20.smtp.github.com<EMAIL_ADDRESS>receiver=
Authentication-Results: mx0.domain.com; dmarc=pass (p=none dis=none) header.from=github.com
ARC-Filter: OpenARC Filter v0.1.0 mx0.domain.com 5F88560736
Authentication-Results: mx0.domain.com; arc=none
ARC-Seal: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578242692; cv=none; b=Gxz/UoQ/cVYyPpEXRkDqIqJYa174Qts8kUmKjizrNZ6rl/ng9F263wHQwu2DIlqOyrP5mgPhTcpXxDVEOhQ52SRFfh79Iw527gWxP+KdBSHxjC3CfBUrpBvkR4S7DT2zORGxaucbpYYhoS2W83G9q8N2rxoOQix/jbtTNL1nBV/Kc3zmzFBGku/QOgFFI7IvAnygbmBmER/HIN57RRw8WdXsGFVbBiD9JIGMqE92TP7wPqBFRuBiKFp9h3ZywQkAOG8CPYn641koFtIJw2k1yNoxyEBaC86m+WGlmKLspwLF+njekkRSQT1RqCpaHd4W85NiGA2vu/h65pYmn84oaA==
ARC-Message-Signature: i=1; a=rsa-sha256; d=domain.com; s=201808; t=1578242692; c=relaxed/simple; bh=OeHAFYgpfq7hdCzWfH7qcEpoznna+XievF6VcPWm9nk=; h=Received-SPF:Received:DKIM-Signature:Date:From:Reply-To:To:Cc:
Message-ID:In-Reply-To:References:Subject:Mime-Version:
Content-Type:Content-Transfer-Encoding:Precedence:X-GitHub-Sender:
X-GitHub-Recipient:X-GitHub-Reason:List-ID:List-Archive:List-Post:
List-Unsubscribe:X-Auto-Response-Suppress:
X-GitHub-Recipient-Address; b=DNYPK11+PTPjy9gAEDA6Ohv/ZuIShlLyKuiwyXLk/xT/ud4rbluYWXYj5xCVUh4A2YyakVg9lFsLvi4uwlTEaQmnl+juufvHKHQIfj3NQzH0JLOsiQiy2LDNBfHuTpYIiobyG0OrfilOstwnXwMgp5jy9M//ZfW6aYQ7mweIROzUay+tYmaV0BzV9OaPzrRP5rq66/exRudpXVmpLboiwKQ+6hJOiYNPkHeTD3sqy25yqAfEbEUT3aaikVTK+84I9nvgTix7o98dtTeat7D0rmV0fm2vzIuDhjd0H9cBSpLu4Gc/WJKhSq5uPWOKOUXj6w0njlij1h09IBkCLURZXw==
ARC-Authentication-Results: i=1; mx0.domain.com; dkim=pass (1024-bit key; unprotected) header.d=github.com<EMAIL_ADDRESS>header.b=MGBfrKg6; dkim-atps=neutral; arc=none
Authentication-Results: mx0.domain.com; dkim=pass (1024-bit key; unprotected) header.d=github.com<EMAIL_ADDRESS>header.b="MGBfrKg6"; dkim-atps=neutral
Received: from out-20.smtp.github.com (out-20.smtp.github.com [<IP_ADDRESS>]) by mx0.domain.com (Postfix) with ESMTPS id 5F88560736 for<EMAIL_ADDRESS>Sun,
5 Jan 2020 16:44:52 +0000 (UTC)
Received: from github-lowworker-2ef7ba1.ac4-iad.github.net (github-lowworker-2ef7ba1.ac4-iad.github.net [<IP_ADDRESS>]) by smtp.github.com (Postfix) with ESMTP id 240778C006D for<EMAIL_ADDRESS>Sun,
5 Jan 2020 08:44:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1578242685; bh=2b7U3dMs52xPA8n8LErBrTLrsTnfHHdnGRtlbTpSPXo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From; b=MGBfrKg6xqJYkiUEeWu4xGmQoT9B8FF3VBqieeezmORCcz/Z0fdpmqOSD5J/p/DgZ
2WTcJOi8/2IYtHElmKfyGwrjNCUPdLX+5R0AnNbquLvPeE1f/HNCzdPKoaGYuS5g1V
9POlREWMk/2amPNL02bFOQEGG+qd79QJJdo5B8rw=
Date: Sun, 05 Jan 2020 08:44:45 -0800
From: kurta<EMAIL_ADDRESS>Reply-To: "trusteddomainproject/OpenARC"<EMAIL_ADDRESS>To: "trusteddomainproject/OpenARC"<EMAIL_ADDRESS>Cc: lukas<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [trusteddomainproject/OpenARC] Postfix implementation (#124)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e12127d14d92_23e43ff2adacd96c527667"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kurta
X-GitHub-Recipient: mindrunner
X-GitHub-Reason: author
List-ID: trusteddomainproject/OpenARC <OpenARC.trusteddomainproject.github.com>
List-Archive: https://github.com/trusteddomainproject/OpenARC
List-Post https://github.com/trusteddomainproject/OpenARCList-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AAKZDJWRBNIM2LGPQWHY77TQ4IE73ANCNFSM4KCY24YA
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/trusteddomainproject/OpenARC/issues/124?email_source=notifications&email_token=AAGU3SJQMXBR6CDCQQOUJCDQ4JBATA5CNFSM4KCY24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEID7CUA#issuecomment-570945872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGU3SOQEDWE7KQ734R4UQDQ4JBATANCNFSM4KCY24YA
.

@mindrunner I am trying to do the same thing, forward email to google. As it seems you have it working, can you give us some more details on how you did it? Thanks!

But your forwarder can add its own DKIM signature. I see that it is doing
SRS to address the SPF forwarding breakage.

I assumed it is doing that and the setting for this is in postifx's main.cf
# Milters used by DKIM
milter_protocol = 6
milter_default_action = accept
dkim_milter = inet:localhost:8891
dmarc_milter = inet:localhost:8893
arc_milter = inet:localhost:8894
smtpd_milters = $dkim_milter,$arc_milter,$dmarc_milter
non_smtpd_milters = $dkim_milter

Do you see any issue with this setup? Is my mailserver not adding it's signature? Sorry, I am still not super confident in reading mail headers.

I see that it is doing
SRS to address the SPF forwarding breakage.

Yes, SRS is activated! :)

I am trying to do the same thing, forward email to google. As it seems you have it working, can you give us some more details on how you did it? Thanks!

@gkohri Sure, happy to assist. However, maybe you could ask more precisely what you need.
See my PR to docker-mailserver for an entry point:
https://github.com/tomav/docker-mailserver/pull/1363/files

When I forward an email to google, this is what I see at the top of the chain:
Received-SPF: softfail (google.com: domain of transitioning<EMAIL_ADDRESS>does not designate <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=selector1 header.b=YPRIkYTB;
arc=fail (missing mandatory fields);
spf=softfail (google.com: domain of transitioning<EMAIL_ADDRESS>does not designate <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=hotmail.com
So, yes, the software is producing a ARC chain, but google seems not to like it.

Please tell us more about your whole setup. Also please post full Email headers from Google! :)

Solved it. Perhaps it was my bad. I thought that with ARC we no longer needed SRS, but we do.

On 2020-01-13 02:48, Greg Kohring wrote:

Solved it. Perhaps it was my bad. I thought that with ARC we no longer
needed SRS, but we do.

ARC requires trust between the two parties. An ARC signature can be
faked.


Sagonzal/exceptions

Split AuthenticationException into AuthenticationClientException and AuthenticationServiceException
Expose http headers in AuthenticationServiceException- #59
Expose suberror code in AuthenticationServiceException (invalid_grant and interaction_required classification) - #61
Remove ClaimsChallengeException.

developers should instead check if AuthenticationServiceException contains claims (aligned with .NET)

Open question:
Should we rename:

AuthenticationException -> MsalException
AuthenticationServiceException -> MsalServiceException
AuthenticationClientException -> MsalClientException

@SomkaPe @henrik-me any opinions on the naming of the exceptions?

@bgavrilMS Thanks for all of the detailed feedback. I have addressed all of the main issues you have raised, and have aligned this implementation with the one in .NET. I have a couple of questions which I will follow up with offline.

one naming question which should be thought of before closing

Not sure which exceptions. IMO, I like calling it InteractionRequired and not UIInteractionRequired, though this may be misleading as some of them we should really show them the system browser... otherwise using names that are used in other libraries makes the most sense to me for the exception naming (seems like you are generally following that pattern)

In reply to: 507772688 [](ancestors = 507772688)


Support for adding env and secret in VM definition just like pod

Feature Request: To maintain parity with containers there should be support of defining environment variables inline so that a VM can be used in different environments without re baking.
`
env:
- name: SERVICE_PORT
value: "80"
- name: SERVICE_IP
value: "<IP_ADDRESS>"
`

http://kubevirt.io/api-reference/main/definitions.html#_v1_downwardapivolumesource is supported in kubevirt.
However, due to technical limitations we can not set env variables inisde the guest.
A benefit of containers.


Profile page

Can you make the collapsable menus open by default and change the student ID number to the username? I like it so far though :)


added entry under example app

Vaex dataframe + dash integration
For adding tutorials, packages, or apps

What did you add to the README.md file?

Have you ensured your contribution adheres to the pull request guidelines of awesome? In particular:

Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

For first time contributors...
Do you want to be added to the contributors list on the README.md file?

[x] Yes
[] No

What name would you like?

vaexio
What website would you like your name linked to?
https://github.com/vaexio

Hey @rishi1111 sorry about the delay in response. I'm currently getting a 502 on the app. Could you let me know when it's fixed?

It's online again 🎉

Nice @maartenbreddels will merge now.


Tooltip in Seed Vault requires 'Show Tooltip in Inventory' to be active in order to work.

Currently using version 1.7.3 of the plugin.
The tooltip for in the Seed Vault will only show if I also have the 'Show Tooltip in Inventory' activated.
It does not work with this option disabled.
With Inventory option OFF (no tooltip):

With Inventory option ON (tooltip showing):

Hey thanks for reporting this! Thankfully should be a quick fix. Next release will fix it :)


Changing version comparator

In version 2 it is possible to change the version comparator via Version::setComparator(). This method was removed in version 3. I would highly appreciate if it comes back. Is that possible?

I thought that custom comparison strategies would be so rare, which is why I decided to remove that ugly static method, but still when a user wants to roll custom one, they could still do the comparison like so: $customComparator->compare($version1, $version2).
But I do get your point, you would prefer to perform comparison through Version class API. Can you show me some example where you would find it very useful?

I have the number of commits since the last git tag in the build part. So I additionally compare the build part if the previous parts are equal. For me it is very useful to just call Version::setComparator() once in the bootstrap file and to use the Version class API then. It also ensures that the use of the custom comparator cannot be forgotten (neither by me nor by others).

Ok, can you make a PR for Version::setComparator() functionality, and then I'll consider it for 3.2.0?

FYI I'll give it a few more days before releasing 3.2.0, but I've updated Composer branch alias to 3.2.x so you can already pull it into your project (https://getcomposer.org/doc/articles/aliases.md#branch-alias).

Thanks.

An update at packagist.org would be nice :)

Done, thanks for a reminder!


'-' in comments causes error

When I locate my cursor on '--------' in comments, it causes the following errors.
Error running ghc-mod command -ghc-mod crashed on command info
ghc-mod crashed on command info

Thanks, I just published a fix to the marketplace (v0.2.5)

Thanks hoover!!!


Viewer component baseLayer behavior is inconsistent with Cesium

On Cesium's Viewer doc, it expects baseLayer to be:
ImageryLayer | false or undefined.
In Resium's Viewer.ts, it is forcing baseLayer to be undefined when it is set to false.
This is causing the map to reach out https://api.cesium.com/v1/assets/2/endpoint to when you want to turn off baseLayerPicker and baseLayer in favor of the ImageryLayer component as Cesium falls back to the Ion behavior if baseLayer is not explicitly false.

<Viewer
                id="LocationFromMap"
                ref={refViewer}
                full
                baseLayerPicker={false}
                timeline={false}
                homeButton={false}
                geocoder={false}
                fullscreenButton={false}
                vrButton={false}
                navigationHelpButton
                animation={false}
                selectionIndicator={false}
                baseLayer={false}
            >
           <ImageryLayer
                        imageryProvider={new UrlTemplateImageryProvider({
                           url: `${buildModuleUrl('Assets/Textures/NaturalEarthII')}/{z}/{x}/{reverseY}.jpg`,
                           tilingScheme: new GeographicTilingScheme(),
                           maximumLevel: 2,
                        });}
           />
    </Viewer>
    ```

The viewer code above (approximately) gives the following console errors due to baseLayer being forced to be undefined if it's `false`:

![consoleErrors](https://github.com/reearth/resium/assets/147518481/83691dfc-083f-4a06-8735-8bc680dbf86a)

If it's allowed to be false (not undefined) these don't happen. A token may also be appended to the first request if `Cesium.Ion.defaultAccessToken` is not set to undefined.

Happy to see I'm not the only person experiencing this. I've been chasing this same error for the last couple days while trying to get Resium to work in an offline (aka no internet connection) environment. This issue doesn't prevent any functionality but does pollute the web console with Ion InvalidCredentials errors.


Norminate @Arhell  to be a reviewer member of KubeVela Org

@Arhell has made consistent contributions on kubevela.io, his contribution is already qualified to be a reviewer member.
I think he'll be glad to continue his contribution as a reviewer member! \cc @Arhell
Anyone who agree with me, please help vote on this issue. Thanks.

ping @Arhell Would you like to become a reviewer member of KubeVela?

ping @Arhell Would you like to become a reviewer member of KubeVela?

I don't mind, but I mainly deal with the front-end, so I will rather only deal with the site.

Yes, it's fine to review only the website.

LGTM

Maybe you could care about the VelaUX project and improve it. LGTM
Since there're two Maintainers who vote for approval, according to our community rules, congratulations! @Arhell

@Arhell Please commit a PR to add your name to the owner's list.

LGTM, thanks for the contribution!🎉


Fix Issue detecting the output device

fixes #172
Apparently returning an empty array to MediaKeyTap makes it listen to all keys. Something that might need to be fixed in MediaKeyTap? @the0neyouseek

Hi JonVR. Will you be reviewing my PR? I need to call self.mediaKeyTap?.stop(), if (!atLeastOne) for this very reason.

Hi @opbarnes I will look into it whenever I get time, however I still need to review some other PR's first (as they came in earlier) and also wanted to do a bit of a refactor of some functions as they are becoming a bit too big.


scmProvider for gitlab should export a Normalized version of the organization value

In Gitlab it is possible to use sub-folders for organizations, like /orgA/teamB/projectC.
In that cas you would git clone<EMAIL_ADDRESS>When using An AppSet searching for all matching repos under the orgA, the returned organization contains / like orgA/teamB.
Here's a sample Appset:
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  annotations:
  labels:
  name: org-a
  namespace: argocd
spec:
  generators:
  - matrix:
      generators:
      - clusters:
          selector:
            matchLabels:
              argocd.argoproj.io/secret-type: cluster
              environment: qa
          values:
            environment: qa
      - scmProvider:
          cloneProtocol: https
          filters:
          - branchMatch: deployment
            pathsExist:
            - deployments/argocd/qa.yaml
          gitlab:
            allBranches: false
            api: https://gitlab.server.net/
            group: "orga"
            includeSubgroups: true
            tokenRef:
              key: token
              secretName: my-gitlab-token
  template:
    metadata:
      name: '{{ organization }}-{{ repository }}-{{ nameNormalized }}'
    spec:
      destination:
        namespace: orga
        server: '{{server}}'
...

Here the template name will be orgaA/teamB-projectC-cluster_name, which is not a valid name.
Appset Controler does log an error:
applicationset-controller
time="2023-07-27T20:15:35Z"
level=error
msg="failed to unchanged Application"
action=unchanged
app=orgaA/teamB-projectC-cluster_name
appSet=orga
error="Application.argoproj.io \"orgaA/teamB-projectC-cluster_name\" is invalid:
  metadata.name: Invalid
  value: \"orgaA/teamB-projectC-cluster_name\":
      a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')"

I'm trying to dig in the code, but help will be much appreciated.
For example, the cluster name provided by the clusters generator does provide a normalized version of the name as nameNormalized

yeah I moved the PR :)


fix(ci): operator release fails with "no rule to make target 'build-chart'"

What this PR does / why we need it:

https://github.com/replicatedhq/embedded-cluster/actions/runs/10605611609/job/29394826595
Which issue(s) this PR fixes:

Does this PR require a test?

Does this PR require a release note?

Does this PR require documentation?

Merging as this only affects the release process.


Idea: add a public render method to Usage Drivers

Improvement Description
A few of the existing drivers out there are starting to congeal around having a unified render method, which translates a hydrated Scope to relevant interface-specific invocations. By making this part of the public API we can start to rely on this method (as in, we expect drivers to implement the render method).
Current Behavior
No Usage.render method.
Proposed Behavior
Usage.render would return a generator that allows the caller to iterate over relevant interface-specific outputs/invocations.

Would drivers have a mechanism to indicate that they aren't renderable? I think there are other kinds of Usages out there.

Yeah, good question - I think it would be a bit like _assert_has_line_matching_ - its an optional method, but for drivers that have a need for rendering it would provide some consistency.


Make API spec definition dynamic based on network in grest-poll.sh

Is your feature request related to a problem? Please describe.
When setting up grest on a network other than mainnet, the polling API spec definition will point to mainnet.
Describe the solution you'd like
When installing a network other than mainnet, grest-poll.sh should point to that network's API spec.
Describe alternatives you've considered
Keep manually editing the definition on new installs.

Added fix via setup-grest.sh (only for default, not user variable section) instead of grest-poll sh to:

avoid scraping on each poll (as you'd poll frequently, especially on monitoring instances)
Avoid third iteration of NWMAGIC (currently in env and setup-grest.sh)


Send email notifications on raised exceptions

Perhaps using a gem like airbrake

@remomueller: continuous integration is sufficient
Also, we have plenty of people reporting issues that spring up!


Place order (market and limit) give zero price and infinite volume

Hello I'm adding support for the lykke exchange (www.lykke.com) and when I make a trade I get a price of 0 and a volume of Infinite:
{ price: '0.00',   size: 'Infinity',   fee: null,   orig_size: 'Infinity',   remaining_size: 'Infinity',   orig_price: '0.00',   order_type: 'maker',   cancel_after: 'day',   product_id: 'EOS-BTC',   post_only: true }
Even though I have a balance and quotes. Any idea what is going wrong?
2018-05-13 19:00:00  0.00185000 EOS-BTC   +0.00%        4     - 46.15    -1.2210   0.3815     sell  0.00000000 EOS  0.20753246 BTC   +0.00%  +18.43%
2018-05-14 15:32:26  0.00169900 EOS-BTC   -8.17%        2    -- 44.67    -1.6557   0.3836           0.00000000 EOS  0.20753246 BTC   +0.00%  +28.95%

order size is calculated by diving your balance/deposit, which for many people recently has been incorrectly returning as 0 or null

Order size is calculated using buy/sell_pct, on a non-positive balance the bot will error out with insufficient funds will preparing a order.
If the balance doesn't get reported at all take a look at balance.js, as @illya13 did fix something? in #1573 only a couple of days ago this might also apply to engine.js
I have yet to see the error myself on any of my running bots though.


Fix/6

Fixes issue #6

Coverage remained the same at 100.0% when pulling 505d9faa0ff12181df7a4bb00f35d069fa9a8fbf on arronhunt:fix/6 into 3e0b7fbe434c5c07aacfe280a9b55d405c95c738 on adesege:development.

This PR fixes the use of
const expressApiVersioning = require('express-api-versioning').default;
did you get it to work without the default key?


the negroni repo moved references/imports updated

The negroni repo moved from github.com/codegangsta/negroni to
github.com/urfave/negroni  The README file and import paths are updated
accordingly.

Thank you!


images not loading on emulator

Hi,
I have started using the latest version (5.0.0). It works perfectly in browser when using ionic serve, but when using ionic cordova emulate ios the images wont load and the spinner keeps spinning.
I am using this plugin in the following way:
<img-loader src="/path/to/file" useImg></img-loader>

Just to throw in a few of my observations if it helps. It seems this works fine in the browser, but on an actual Android device (Pixel 2XL) the images sometimes load but mostly just don't, and stay completely blank (I don't have a fallback image configured, fallback is disabled.)

Reverting to 4.2.1 restores normal functionality.

@ihadeed have you looked into what @lincolnthree has mentioned?

+1
with angular 5.0.0 not working. image loading fail with error 404. event url is correct and working

Should be fixed in the latest release, please re-open with steps to reproduce if you're still experiencing this issue.


Question About Parameters

This is a question and not a bug report. :)  Your project works excellently and has been for many years for me.  I sent a PayPal donation to support the cause. 🙏
My question is about parameters.  I see that you support @0 as input parameters for filtering.  I was wondering if that translates to -- or can translate to -- parameterized in SQL when it gets compiled as a query to send to the database?
Thank you for any insight you can provide and thank you again for your efforts.

Thank you for that @mahdiyar021 but that looks different from what I am asking.  Mine is a general question that I have been too busy to investigate so I wanted to ask here to save me some time.  I guess we see where that got me. 😅

For further reference/context, I was running into an issue with Syncfusion DataOperations which does not (or did not, when I reported it) parameterize their queries.  They have since addressed this for a future release:
https://www.syncfusion.com/forums/186351/dataoperations-performfiltering-does-not-parameterize-values
At one point they were not going to address this, and my idea at the time was to use System.Linq.Dynamic.Core instead, but was unclear if the parameters made their way to SQL, too.  Now that Syncfusion has fixed this on their end this is no longer a priority/concern for me.
(It would be nice to know if parameters are still sent to SQL as designed, however :D )

Correct, you need to use the config:
var config = new ParsingConfig
{
    UseParameterizedNamesInDynamicQuery = true
};

var result784 = context.Products.Where(config, "NullableInt = @0", 1).ToDynamicArray<ProductDynamic>();

This generates (e.g. Sqlite) this SQL:
SELECT "p"."Key", "p"."NullableInt", "p"."Dict_Name"
      FROM "Products" AS "p"
      WHERE "p"."NullableInt" = @__Value_0

See ConsoleApp_net6.0_EF6_Sqlite for more details.


refactor: move mempool result to mempool types

Stack:

#161
#160
#159 ⬅

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 51.00%. Comparing base (9ad5ef6) to head (5105739).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #159      +/-   ##
==========================================
+ Coverage   50.86%   51.00%   +0.14%
==========================================
  Files          19       19
  Lines         694      694
  Branches      694      694
==========================================
+ Hits          353      354       +1
  Misses        322      322
+ Partials       19       18       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


UI notification different when kill app

i custom view notification by file xml, it only show when app opening. when close app, notification show from payload and it different with view my costom, i want to show view by xml when close app, thanks

@vohoangtuit without any code, screenshots, etc it's hard to know where to begin.  I would suggest looking at some of the other FCM related issues like #4 or #89


fix: use sdk-go v1.42.4-lens

Removes amino.Seal call in codec init. Not sure if this will work, but worth a shot.

Support for Injective was added in b8291470df53c79075a156a175b16785f5a4ec14 so closing out this PR


Natural Gas Updates

Closes #399, #400
Changes proposed in this Pull Request

In this PR I have:

Integrated methane tracking. Gas production facilities are now modelled as stores + links rather than generators.
Applied natural gas import/export constraints, tied to modelled weather year
Updated relevant emission accounting constraint equations for ch4 tracking

Checklist

[ ] I tested my contribution locally and it seems to work fine.
[ ] Code and workflow changes are sufficiently documented.
[ ] Changed dependencies are added to envs/environment.yaml.
[ ] Changes in configuration options are added in all of config.default.yaml.
[ ] Changes in configuration options are also documented in doc/configtables/*.csv.

To be done before merging:

[ ] Correct international natural gas import/export constraints
[ ] Add config option for allowing range of imports/exports (ie. extend limits by x%)
[ ] Update natural gas plots

@ktehranchi; can you please confirm neither of the changes in this commit are breaking changes for you?

The log path change reverts the change from this commit. I was getting a NotADirectory error if left as is. Maybe this is a snakemake version thing though?
The add_co2_emissions() I dont think is needed at the end? The CCS techs are captured in the attach_newCarrier_generators function, I believe. The parsing of the - causes quite a few issues for sector names, as many use -. Removing the catch all  add_co2_emissions() at the end bypasses the sector issues, though.


Multi Desktop Feature Enhancement

Description of the new feature / enhancement
Adding Multi Desktop enhancement into the PowerToys collection will help multi taskers a lot. Current version doesn't have any shortcuts other than linear switching with ctrl + win + L/R
It'd be great we can switch to specefic desktop with hot key & main part, after switching desktop name will be shown in the center or somewhere for one or two seconds so that we know which window we jumped to while Ctrl Win Arrows
Here is the additional app which is already been made. But I think Microsoft should have not abandoned its own pro feature halfway.
https://peachapp.net/
Scenario when this would be used?
I work as a Project Manager who has 10 repos open simultaneously on every desktop along with other supporting windows. and Skype pinned for All Desktop windows. Right now it's too confusing to switch windows as I cannot be sure which one I switched to, it's too time consuming & effort taking to go from the first desktop to the last one while passing through all desktops in between. As per my personal requirement, Flashing the Desktop name for a second is more useful than additional hotkeys
Supporting information
Reference App:
https://peachapp.net/

There are several other issues related to virtual desktops which read similar to what you are proposing here. Could your review these and close or refine this issue afterward?
#19, #24, #32, #3737

closing as similar already added way back in time


Nlog async file target no longer writes after moderate use

We're seeing an issue where the file target, with async wrapper no longer writes after moderate use.  We're using other targets at the same time, which continue to write, namely the database target.  If we restart the application that is using nlog, the text file writes again.
thanks

We are seeing the same behavior with NLog 3.2.0

Could you provide a sample project for this?

Unfortunately its proprietary.  I could try to throw something together from scratch

That would be great if possible. I can't reproduce it, but it is a serious
bug what you describe.

Does anyone know if this bug is introduced in 3.2.0?

@attrib75 because we can't reproduce we need a sample project or unit tests. Otherwise I will need to close this issue.

I'll try to find time to reproduce the issue with a test app and submit it.  Looking at it more closely, I think we are configuring it wrong, or its not behaving as expected?  If you configure an ArchiveEvery day setting, together with an ArchiveAboveSize setting,  then each day, when that day's log messages hit the ArchiveAboveSize limit, its done logging for that day.  The next day, it will generate a new log file and log until it hits the ArchiveAboveSize limit, etc.
Is this the intended behavior?

    layout="${longdate}|${callsite:methodName=true} ${message} ${newline} ${windows-identity:userName=true:domain=true} ${newline}${exception:format=ToString} "/>
</target>

thanks!

@Xharze do you know this?

I don't think that archive options should stop logging. So it's a bug.

I didn't know this, if it's the case it is a serious bug

@attrib75
I renamed the issue. Did I subscribed it well?

Yes, but this is the intended result right? If so, its not an issue, I just didn't understand how to configure it

Thanks

Hi @attrib75
Is it possible to test this more with : archive every minute and a lower archiveabovesize? Can you get it reproduced?
We can then create a unit test and fix this

@attrib75 is it possible to test it for me?

I have found the issue. We cannot create multiple archive files with the same name (archiveNumbering="Date").
It's unclear what to do. Don't archive? Append to the same archive file?
The solution is to choose for archiveNumbering="DateAndSequence"
So proposal: wontfix.

@attrib75 please you input :)

Hi yes that makes sense.   I would agree to append a sequence to the archive above setting. Thank you for looking into this!

Thanks for the feedback!

Warning notes added at: https://github.com/NLog/NLog/wiki/File-target


Updating version to 2.0.0

Major Version update for PoA.
Use following package.json for PoA runs:
{
  "private": true,
  "scripts": {
    "test": "make test"
  },
  "devDependencies": {
    "@percy/cli": "1.27.0-alpha.0",
    "@percy/webdriver-utils": "1.27.0-alpha.0"
  }
}

lets update package.json as well, since this will go in master now

@itsjwala I also wanted to update the package.json, if its fine I will update it as it is pinning the particular CLI alpha version and will be merged to master that is why I was little concerned.

@Amit3200 not an issue, this codebase is used only for development purpose.
example repo should contain stable release.

Closing this as for consistent PR and release


Change to a more general detection of uncommon representations

Coverage remained the same at 65.422% when pulling 17232dd48c956d7a72a987911f63c5534cfcaf55 on makyen:Makyen-more-general-word-text into 50615b053bf4daead9bf386c73333f8143fcb82e on Charcoal-SE:master.


Cards are left-aligned

Expected Behavior
On a fresh install, all cards are centre-aligned.
Actual Behavior
Cards are left-aligned.
Observations
Following error is thrown in the console:
Uncaught (in promise) TypeError: Cannot read property 'length' of null
    at HTMLElement.setStyle (card-mod.js:1)
    at async HTMLElement._setTemplate (card-mod.js:1)

Steps to Reproduce the Problem
(on a new Home Assistant OS install)

Installed card-mod via HACS
Installed 'Lovelace Soft UI light theme' via HACS
Set theme to 'Lovelace Soft UI light theme'
View any dashboard or create a new dashboard

Specifications

Version: v0.59
Platform: Home Assistant OS 2020.12.2
Subsystems:

card-mod: v2.0.3

Debugging/Resolution attempts

Reinstalled theme, card-mod
Restarted multiple times
Viewed in Chrome/Edge

Example Screenshot

Try reinstalling from main.

Tried reinstalling the theme from main, still having the same issue even after a restart.

Tried reinstalling the theme from main, still having the same issue even after a restart.

Huh. No issues for me, could be related to the fact that you're at 2010.12.2 but I'm at 2021.1.0b0.

Huh. No issues for me, could be related to the fact that you're at 2010.12.2 but I'm at 2021.1.0b0.

Ah, typo in the original, meant to say version 2020.12.2 (current stable). Updated to 2021.1.0b0, same issue unfortunately.

Ah, typo in the original, meant to say version 2020.12.2 (current stable). Updated to 2021.1.0b0, same issue unfortunately.

See any issues in the browser console?

See any issues in the browser console?

Only that noted in the observations above, I've included a screenshot for reference.

Only that noted in the observations above, I've included a screenshot for reference.

I have the same problem here，I also use HACS installation. I think the problem is here：
#columns {     flex-direction: column !important;     margin: 0 auto;     max-width: 500px; }
Without this code, the style is normal

I have the same problem here，I also use HACS installation. I think the problem is here：
#columns {     flex-direction: column !important;     margin: 0 auto;     max-width: 500px; }
Without this code, the style is normal

@baby7 Mind making a PR? Just change theme.yaml, run theme_maker.py, and create a PR for both repos.

@baby7 Mind making a PR? Just change theme.yaml, run theme_maker.py, and create a PR for both repos.

I'll look at this tonight (AEDT) if a PR isn't in.

Each style file has this code, I will try to PR, but I don't know where this code was used before.

Each style file has this code, I will try to PR, but I don't know where this code was used before.

Edit theme.yaml and use the generator Python file.

Edit theme.yaml and use the generator Python file.

OK

OK

I submitted PR, but one of them didn't seem to pass the inspection

I submitted PR, but one of them didn't seem to pass the inspection

@KTibow I see you've updated HACS(Dark Soft UI Theme),the updated style works fine.

@KTibow I see you've updated HACS(Dark Soft UI Theme),the updated style works fine.

Yeah I'm lazy. I'll get around to it.

Yeah I'm lazy. I'll get around to it.


Setup ci system

[ ] ci snapshot build
[ ] milestone release
[ ] ga release

Looks like on windows if maven cache is enabled we get:
Error: ENOENT: no such file or directory, realpath 'D:\a\spring-rewrite-commons\spring-rewrite-commons\spring-rewrite-commons-functional-tests\private-artifact-repository-tests\testcode\maven-projects\private-repository\reposilite-data\repositories\snapshots\com\example\dependency\dependency-project\1.0-SNAPSHOT'


The Seata Server dump stack will appear no permission.

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description

The seata server dump stack d:/xx.log, this operation will appear without permission on Linux.
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :
OS :
Others:

the append path can be use current user home dir concat log name. and logger the path.


Should the number of total student points be allowed to go below 0?

If not, should we check it in front end or backend?
For now, it is allowed:

Discussed today (25.09.2024).
Server should respond with status code 400 and explanation why such case is disallowed.
This scenario should still be checked on frontend side.


ConvertTo-Bicep outputs decompile warning message multiple times

Describe the bug
When using ConvertTo-Bicep to decompile multiple ARM Templates at the same time the decompilation warning message generated by bicep decompile is generated multiple times.
To Reproduce
Add multiple ARM templates to a folder and run ConvertTo-Bicep.
PS C:\> ConvertTo-Bicep -Path C:\ARMTemplates
WARNING: Decompilation is a best-effort process, as there is no guaranteed mapping from ARM JSON to Bicep.
You may need to fix warnings and errors in the generated bicep file(s), or decompilation may fail entirely if an accurate conversion is not possible.
If you would like to report any issues or inaccurate conversions, please see https://github.com/Azure/bicep/issues.
WARNING: Decompilation is a best-effort process, as there is no guaranteed mapping from ARM JSON to Bicep.
You may need to fix warnings and errors in the generated bicep file(s), or decompilation may fail entirely if an accurate conversion is not possible.
If you would like to report any issues or inaccurate conversions, please see https://github.com/Azure/bicep/issues.
C:\ARMTemplates\nsg.bicep(6,10) : Error BCP017: Expected a resource identifier at this location.
WARNING: Decompilation is a best-effort process, as there is no guaranteed mapping from ARM JSON to Bicep.
You may need to fix warnings and errors in the generated bicep file(s), or decompilation may fail entirely if an accurate conversion is not possible.
If you would like to report any issues or inaccurate conversions, please see https://github.com/Azure/bicep/issues.
WARNING: Decompilation is a best-effort process, as there is no guaranteed mapping from ARM JSON to Bicep.
You may need to fix warnings and errors in the generated bicep file(s), or decompilation may fail entirely if an accurate conversion is not possible.
If you would like to report any issues or inaccurate conversions, please see https://github.com/Azure/bicep/issues.

Expected behavior
The warning should only be printed once followed by the error logs from bicep decompile
Additional context
Add any other context about the problem here.

No longer an issue after #21 was implemented.


Hex dependency resolution failed

Trying to add phoenix_haml into my phoenix project as mentioned on readme, but i get error message. sadly i have no an idea what it's trying to tell me.
added this in my mix.esx:

{:phoenix_haml, "~> 0.0.5"}

and this one into config/config.ex

config :phoenix, :template_engines,
haml: PhoenixHaml.Engine

after executing mix deps.get following message comes:

Running dependency resolution
Looking up alternatives for conflicting requirements on phoenix
Activated version: 0.13.1
From phoenix_haml v0.0.5: ~> 0.4.0
From mix.exs: ~> 0.13.1
** (Mix) Hex dependency resolution failed, relax the version requirements or unlock dependencies

when i add phoenix_haml via github in mix.esx:

{:phoenix_haml, github: "chrismccord/phoenix_haml"}

then it throws same message but with different versions:

Running dependency resolution
Looking up alternatives for conflicting requirements on phoenix
Activated version: 0.13.1
From deps/phoenix_haml/mix.exs: ~> 0.12.0
From mix.exs: ~> 0.13.1
** (Mix) Hex dependency resolution failed, relax the version requirements or unlock dependencies

What Im doing wrong?

I need to bump the phoenix dep , but you can try
{:phoenix_haml, github: "chrismccord/phoenix_haml", override: true}

thank your Chris but same message

➜  blog  mix deps.get

Updating phoenix_haml (git://github.com/chrismccord/phoenix_haml.git)
Running dependency resolution
Looking up alternatives for conflicting requirements on phoenix
Activated version: 0.13.1
From deps/phoenix_haml/mix.exs: ~> 0.12.0
From mix.exs: ~> 0.13.1
** (Mix) Hex dependency resolution failed, relax the version requirements or unlock dependencies

Ive also tried to add calliope in my mix.exs but with no results.
can you explain why this message comes?
here are all of my deps:

defp deps do
[{:phoenix, "~> 0.13.1"},
{:phoenix_ecto, "~> 0.4"},
{:postgrex, ">= 0.0.0"},
{:phoenix_html, "~> 1.0"},
{:phoenix_live_reload, "~> 0.4", only: :dev},
{:cowboy, "~> 1.0"},
{:phoenix_haml, github: "chrismccord/phoenix_haml", override: true},
{:comeonin, "~> 0.10"}]
end

It's being caused by me locking phoenix at 0.12. I need to release a new version that supports >= 0.13

ok.
if i will fork it then edit this file
https://github.com/chrismccord/phoenix_haml/blob/master/mix.exs
and if i will change third line

defp deps do
[
{:phoenix, "~> 0.12.0"},
{:cowboy, "~> 1.0.0", only: [:dev, :test]},
{:calliope, "~> 0.3.0"}
]
end

to

defp deps do
[
{:phoenix, "~> 0.13.1"},
{:cowboy, "~> 1.0.0", only: [:dev, :test]},
{:calliope, "~> 0.3.0"}
]
end

it will work right?

i have fixed by forking this repo and made it friendly with 0.13.1 version of phoenix
if you get similar error fix so:
change "chrismccord" to "programisti"
{:phoenix_haml, github: "programisti/phoenix_haml"}

Can you send a PR?

sorry but dont know what PR abbreviation means.
only PR i know is marketing stuff.

hehe "Pull request". When you visit this projects page it should present you with an option to "compare and pull request" from your fork.

i hope you are looking for this:
https://github.com/chrismccord/phoenix_haml/pull/13

fixed.
so you dont need to change author name as i said before.


there is an error, maybe the same of 2 weeks ago

Can you check? this extension is saving lives ahah
keep up with the good work!

Are you having problems with password protected recordings? If so, it's a known issue and I'm working on it.

Yes, but it seems that on Firefox it is working normally: i should try using it. I'll try also the debugging tool.
Thanks anyway :D


Everything is in Arabic...

Everything is in arabic... no english!

what do you mean everything in arabic? documentation?


Monitor Group bulk add

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
Looking for a feature in the settings similar to "Tags" but for monitor groups. This way you can bulk add multiple into a group instead of one at a time upon creation.
✔ Solution
Be able to go in to settings and select Monitor Group. From here you can create a new monitor group and/or bulk add monitors to that group or an existing group.
❓ Alternatives
No response
📝 Additional Context
No response

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1457 or https://github.com/louislam/uptime-kuma/issues/1323
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^


[Site Request] Please provide a bottle/formula for homebrew (macOS)

[X] I'm reporting a site feature request
[X] I've verified that I'm running yt-dlp version 2021.08.10
[X] I've searched the bugtracker for similar site feature requests including closed ones

Description
As a macOS-user, I would love to see yt-dlp being provided as a homebrew bottle / Formula. This would make updating my apps more convenient. youtube-dl and youtube-dlc (and even haruhi-dl!) hava a bottle, but are outdated with speed issues at the moment and I'm pretty sure yt-dlp would gain some more users if a homebrew bottle would be provided.

Isn't this a homebrew side problem?(similar to scoop and choco)

To be honest, I don't know.

Bottles are created using the Brew Test Bot, usually when people submit pull requests to Homebrew

I don't have a mac - making it not possible for me to make a bottle and test it. Even if I did, I will need to manually keep updating it. Similar to #330 and #368, I am not interested in maintaining packages that I need to keep manually updating. Any third party is free to make a bottle and put in the effort to keep it up to date

FWIW once formula is created, it's often updated by PRs from community

I'll try making a formula

FYI, I have just merged the formula, it can be installed as brew install yt-dlp now. 🎉

@chenrui333 Will it be auto-updated? @nao20010128nao had also just made a PR #827 to maintain our own taps. I am wondering if it is needed now

it can be automated pretty easily with something like this

Thank you! https://formulae.brew.sh/formula/yt-dlp#default


Persisted store shows zero triples

I'm probably just misunderstanding RDFLib (e.g., identifiers) or my data is funky, but when I try to open a persisted store with identifiers and the like, but when I try to open a previously-persisted store, following the example in the oxrdflib API tutorial, I get zero triples.
For example, the following works:
g = Graph(store='Oxigraph')
g.open(dir)
g.parse(ttl_path)
print(len(g))
g.close()

and has no errors to suggest it failed to persist, but if I comment out the parse call, the length is zero.
create=True doesn't seem to make a difference, and adding an identifier to the Graph call produces a different error when it comes time to parse: No scheme found in an absolute IRI.
I'm using the stable version of RDFLib (6.3.2) and am trying to use this with YAGO 4.5, with the smaller schema and taxonomy files showing this issue, not just the huge facts one which motivated using a more-efficient store.

@ dymil  Thank you for trying Oxigraph! Yes, identifiers in RDFlib is a mess.

and adding an identifier to the Graph call produces a different error when it comes time to parse: No scheme found in an absolute IRI.

This is probably because you are not using a valid URL (aka IRI) as identifier. Something like http://example.com/ should work.
For example
g = Graph(store='Oxigraph', identifier="http://example.com")
g.open(dir)
g.parse(ttl_path)
print(len(g))
g.close()

Great!

Should the code in the README under "If you want to get the store data persisted on disk" have an identifier in the Graph() call?

Yes, definitely.

Also, do you know if there's some way to avoid re-parsing everything?

Yes, you just need to figure out which auto-generated identifier was used during loading.
Something like g.query("SELECT ?graph WHERE { GRAPH ?graph { ?s ?p ?o }} LIMIT 1") should give you the used graph name. If it's a blank node you should use Graph(store='Oxigraph', identifier=BNode("my_Id")) afterward to make it work.

Worked again, thanks so much!


Cache limit test

Testing for #902

Codecov Report

Merging #917 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #917   +/-   ##
=======================================
  Coverage   53.99%   53.99%
=======================================
  Files          41       41
  Lines        7538     7538
=======================================
  Hits         4070     4070
  Misses       2950     2950
  Partials      518      518

Impacted Files
Coverage Δ

xorm.go
64.61% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e3550c7...fd53cfd. Read the comment docs.


Manifest not detected in Quarkus-Omnifaces extension

I've configured the PWAResourceHandler on my Quarkus + Myfaces Application but the manifest.json can't be detected.
I debug the code and see the manifest generating the file. But the manifest is not recognized.

Quarkus: 2.16.3.Final
Quarkus-Omnifaces: 3.14.3
Someone can help ?

I see the issue.   Might need to fix both Quarkus OmniFaces AND OmniFaces to make it work.

@felipelx07 can you try just adding @Named to your Manifest like this..
@Named
@ApplicationScoped
public class ManifestJson extends WebAppManifest {

Does that now work for you?

Its work mate! Thank you

I am going to work a better fix but that should keep you working for now.

@all-contributors add @felipelx07 for bug


Web API Link is not Working

Hi, Abshishek!
Thanks for amazing work. I was just trying and found the API has got some issues (or I am using it incorrectly, don't know). The screen shots are attached for your perusal, have a look at them, thanks!
The commands to run the API (Am I using these environment variables correctly?):

The link result:

And also could you please update the diffuzers.ipynb file as well?
Thanks again!

is this in google colab?

is this in google colab?

Yes, trying in Colab.

okay. to run the api in colab, you need to use localtunnel (or ngrok).
using localtunnel, in colab, you can do:
!npm install localtunnel
!diffuzers api &>/dev/null&
!npx localtunnel --port 10000

localtunnel will return you a link which you can use.
ill add an example for both app and api using ngrok and localtunnel.
btw, if i may ask, why do you want to run the api in colab? since, api is designed mostly for serving a custom frontend. is it for testing purposes?

its a bit compressed now. all the features are still there. just load the model and then see what happens :D everything available previously, is still there. if you are still missing something that was there previously, please let me know.

its a bit compressed now. all the features are still there. just load the model and then see what happens :D everything available previously, is still there. if you are still missing something that was there previously, please let me know.

OOh, I get it now. The features are now by default attached with the model. I think, last time we were selecting an option and then load a model.
Your efforts are much appreciated , keep doing amazing work.
Thanks a lot!


[poppler] Fix build error with triplet x64-windows-cpp17

Describe the pull request

What does your PR fix? Fixes #

Fix build error with triplet x64-windows-cpp17
x64-windows-cpp17.cmake
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)
set(VCPKG_CXX_FLAGS "/std:c++17")
set(VCPKG_C_FLAGS "/std:c17")

Does this related to https://github.com/microsoft/vcpkg/pull/15468 regressions?

Does this related to https://github.com/microsoft/vcpkg/pull/15468 regressions?

Does the official support cxx17 in the latest version? If not, please open an issue to upstream for official approval.

It supports, but poppler in C++14 can't be used in C++ 17 application.
boost-exception in vcpkg doesn't support C++ 17 now.

Does the official support cxx17 in the latest version? If not, please open an issue to upstream for official approval.

It supports, but poppler in C++14 can't be used in C++ 17 application.
boost-exception in vcpkg doesn't support C++ 17 now.

I'm unable to reproduce this issue locally after adding boost-container as a dependency of poppler:
Installing package poppler[core]:x64-windows-cpp17... done

Specifically, using the triplet you've posted, I'm able to successfully build boost-exception and boost-container. Have you pulled the most recent vcpkg master and reproduced this from a clean instance? (You can rename installed/ to quickly "uninstall" everything for testing)

I'm unable to reproduce this issue locally after adding boost-container as a dependency of poppler:
Installing package poppler[core]:x64-windows-cpp17... done

Specifically, using the triplet you've posted, I'm able to successfully build boost-exception and boost-container. Have you pulled the most recent vcpkg master and reproduced this from a clean instance? (You can rename installed/ to quickly "uninstall" everything for testing and rename it back when you're done)

After updates for vcpkg and its repo, and delete vcpkg/installed, vcpkg install poppler:x64-windows-cpp17 succeeds.
As a diff, delete vcpkg/installed/x64-windows-cpp17 instead of vcpkg/installed, the problem I've stated can not be solved.


polish strategy optimization

Codecov Report

Merging #37 (c7d1dad) into main (d443314) will decrease coverage by 11.07%.
The diff coverage is 32.18%.

@@              Coverage Diff              @@
##               main      #37       +/-   ##
=============================================
- Coverage     96.09%   85.01%   -11.08%
- Complexity      505      517       +12
=============================================
  Files           141      157       +16
  Lines          1331     1542      +211
  Branches         74       79        +5
=============================================
+ Hits           1279     1311       +32
- Misses           39      214      +175
- Partials         13       17        +4

Impacted Files
Coverage Δ

...rader/candle/api/application/StrategyInteractor.kt
100.00% <ø> (ø)

...rader/candle/api/domain/service/StrategyService.kt
80.00% <ø> (ø)

...structure/repository/BBandsParamsRepositoryImpl.kt
100.00% <ø> (ø)

...frastructure/repository/EmaParamsRepositoryImpl.kt
100.00% <ø> (ø)

...rastructure/repository/MacdParamsRepositoryImpl.kt
100.00% <ø> (ø)

...frastructure/repository/RsiParamsRepositoryImpl.kt
100.00% <ø> (ø)

...ture/repository/entity/StrategyParamsPrimaryKey.kt
100.00% <ø> (ø)

...common/domain/model/candle/CandleListExtensions.kt
100.00% <ø> (ø)

...rader/common/domain/model/market/CommissionRate.kt
88.88% <0.00%> (-11.12%)
:arrow_down:

...der/common/domain/model/strategy/BackTestResult.kt
0.00% <0.00%> (ø)

... and 29 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d443314...c7d1dad. Read the comment docs.


Spoilered text are not working on Android

I'm using the prebuilt library for Android downloaded recently from the official site. When I send the TdApi.GetChatHistory request to get the messages in a chat, in the result list every message content type is MessageUnsupported if the message is a text message and it contains any spoilered text.
Interestingly in C# (tdlib 1.8.9 + TdSharp) it works fine and returns the content correctly.
What do you suggest?

You are using an outdated TDLib version.
Here is an example on how to build TDLib in Android: https://github.com/tdlib/td/tree/master/example/android#tdlib-android-example

Thanks, I could build the new version and now it works fine.
@levlam so can you please remove or extend the text on the website, because it is not clear that it is a deprecated 3 years old build. It appears in 2 places:

on the bottom of the main page: https://core.telegram.org/tdlib/
and in the instructions generator: https://tdlib.github.io/td/build.html?language=Java

It will be removed after TDLib 1.9.0.


[bug]: Fee policies not broadcasting, odd behavior

I recently fired up a second LND node which is demonstrating odd fee policy behavior. I opened several channels three days ago, and have attempted to change the fee policy via lncli and thunderhub. Fee policy changes are made successfully, verified via lncli. However, over the past three days, the node has not broadcasted the fee policy changes, as reported by all LN network browsers, as well as my original node which has a channel with my second node. Oddly enough, the second node appears to be receiving gossip normally, as I can adjust channel fees from my original node, which are quickly reflected in the channel policies on the second node.
I've reviewed the lnd logs and see no errors. It appears to be updating the network graph / update as expected.
I've made fee rate changes many times over the past couple of days and attempted restarts of lnd; none of which seem to effect the issue.
Your environment
LND 15.3
Ubuntu
Bitcoind

any other relevant environment details

Steps to reproduce
As above
Expected behaviour
Fee policy changes should be accurately updating by peers
Actual behaviour
Second node seems to be receiving fee rate updates appropriately but may not be broadcasting its own policiies?

I've made fee rate changes many times over the past couple of days and attempted restarts of lnd; none of which seem to effect the issue.

Your fee updates could have been rate limited, if you sent out too frequently. I suggest to pause updating fees a bit (two days or so) and then test again.

Your fee updates could have been rate limited, if you sent out too frequently. I suggest to pause updating fees a bit (two days or so) and then test again.

I'd suggest this is not applicable as the original fee change from the opening policy in lnd.conf was allowed ~24 hours to propagate without success. Subsequent changes have been allowed minimum 6-24 hours before making another attempt.

It looks like a rate limiting thing but:

Does this behavior happen with all the channels, or only with one of them?
How many peers does your node have?
Did any of your changes propagate?
When was the last time that you updated your fees?

Does this behavior happen with all the channels, or only with one of them?

All channels. Only one rate change was propagated from the node. Currently the node has a channel with my original node, and two others. After channel opening I was able to change fees once on the channel with my original node. However, no changes have since been broadcast for that channel. The other two channels have never appropriately updated fee policy changes.

How many peers does your node have?

Currently 7. Three are peers with channels.

Did any of your changes propagate?

As above, only one.

When was the last time that you updated your fees?

I've attempted again this morning; on average every 24 hours. This morning I switched to tor only, assuming my hydrib/VPN setup could be causing an issue, however, it does not seem to have affected the issue. I'd imagine my hybrid/VPN setup is not to blame as I've been able to successfully route payments via these channels, and the node is appropriately seeing fee policy changes from its peers with which it has active channels

Yes, I also doubt is related to your hydrib/VPN setup.
You coud try:

Asking some other operator in the network (better if he is connected to your primary node) what fees does he see.
Updating the fee from your primary node, does that fee get propagated?
Updating the fee from you secondary node with another channel, do LN Browsers reflect that fee?

I appreciate the ideas!
https://amboss.space/edge/759586x1943x2
This is one of the channels that has not updated fees... It still thinks I'm charging 3000ppm, which is specified on channel open via lnd.conf. The fees seem consistent among several LN browsers...
YES! Oddly enough, when I change fees from my primary node, it is seen by the secondary node. Here is the channel between the two: https://amboss.space/edge/759589x2173x1 ; As you can see, I was able to change fees ONCE on this channel with the secondary node, from 3000 > 1000 ppm; no others have been broadcast. Worth clarifying; the other two channels that the secondary node has with Moon and Boltz havent broadcast a single rate change.
LN browsers have not reflected the fee changes, as you can see from links provided

Oddly enough they finally updated... Only took 3 days. Any other ideas why I could have run into the delay?

My vote goes for rate limiting. Hard to say if it was something else without further investigation. I will close the issue, let us know if it happens again :+1:

I am running into similar issues on testnet. Very hard to get policy updates propagated to explorers. Also with two independent nodes connected to the same external node (opennode in my case, I believe also running lnd), the update doesn't reach the other node.
I understand rate limiting, but if only lnd nodes are involved, isn't that supposed to be only for a minute?

I am running into similar issues on testnet. Very hard to get policy updates propagated to explorers. Also with two independent nodes connected to the same external node (opennode in my case, I believe also running lnd), the update doesn't reach the other node.
I understand rate limiting, but if only lnd nodes are involved, isn't that supposed to be only for a minute?

It is definitely not rate limiting... It took 3 days to change from the original fee policy set on channel opening.

I have a feeling that there is a bug somewhere in the gossip code. In a different context, I did some investigation previously: https://github.com/lightningnetwork/lnd/issues/6531#issuecomment-1125986653

Can confirm that after applying https://github.com/bottlepay/lnd/commit/41564ff4588b62bc517b85f9adad05f8124a5817, my updates propagate to mempool.space promptly.

@joostjager how many peers does your node have? Have you modified any of the default gossip config params?
AFAICT, all your diff above does it always send the gossip messages to peers that are your active syncers. Otherwise, we'll treat them only as source of new inbound updates and use the other peers to send out outbound updates.

At the moment it has 3 peers in ACTIVE_SYNC, but I remember that I tried adding more peers when I couldn't get my updates propagated.
I've seen the same problem in the controlled environment mentioned above. It's also reproducible there. Just need to update the docker lnd rev to a branch that doesn't include the patch.

@Roasbeef the analysis in the link above (horizon not set), does that make any sense?

@mcsnubbs

I'd imagine my hybrid/VPN setup is not to blame as I've been able to successfully route payments via these channels

Just wanted to add that I also started experiencing this issue shortly after switching to hybrid mode using tunnelsats


Android: Basic support configuration changes

What does the pull request do?
This add basic support for configuration changes, enough to prevent recreating the main activities when such changes occur, such as rotating the device. Only orientation change and resizing are handled.
Also, removes the view from logical tree when the activity is destroyed due to an unhandled configuration change, or by the os due to resource constraints. When the activity is recreated, the view is restored from the viewmodel. There is a rendering bug that occurs after recreating the activity, when the screen is black, and updates to the scene will only make it show the background with outlines of some controls, This requires further investigation.
What is the current behavior?
Currently, rotating the device will cause the activity to be recreated, which causes the bug noted above.
What is the updated/expected behavior with this PR?
Rotating the device will only update the size of the main view
How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Fixed issues

To support viewmodel and proper lifecycle management, the main activity now derives from AppCompatActivity. This made the ResourceDesigner.cs file to grow quite large.

You can test this PR using the following package version. 0.10.999-cibuild0018205-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Note that xamarin sdk will be replaced soon #6922

Ok, that would make it much easier to build on linux.

You can test this PR using the following package version. 0.10.999-cibuild0018216-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Note that xamarin sdk will be replaced soon #6922

What's the status on that PR and it's dependency? Will they be merged soon?

@emmauss #6922 PR is blocked by #7347, which is blocked by #5831. We plan to have all of these changes for next major release.
But I think this PR can be merged before that, I will need to adjust my 6922 PR after.

@emmauss #6922 PR is blocked by #7347, which is blocked by #5831. We plan to have all of these changes for next major release. But I think this PR can be merged before that, I will need to adjust my 6922 PR after. Although I am not really experienced with Xamarin SDK, and if you want, you can rebase this PR on top of 6922. If you have free time for it.

I'll rebase over your PR as the Xamarin SDK has a few thing that makes working with it harder, compared to the dotnet sdk. Also, the dotnet sdk added support for android on linux on the preview

rebased over #6922 .

You can test this PR using the following package version. 0.10.999-cibuild0018760-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

PR ready for review

You can test this PR using the following package version. 0.10.999-cibuild0018781-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]