Hi,
unfortunately issues in our GitLab repo are not publicly visible due to
inability of GitLab to have them just read only for quest users. Since
we rely on them a lot for all sorts of things during development and
planning we have them tightly managed. So letting people/bots open and
comment issues would be a problem...
If you need a handle for later to ask about, it is issue `labs/bird#416`.
This is something we talked about and would like to fix in the future.
If anybody has a suggestion how to have issues public and read-only in
self-hosted GitLab, we are very much open to hearing them))
Happy routing,
David
David Petera (he/him) | BIRD Tech Support | CZ.NIC, z.s.p.o.
On 5/19/26 18:59, Justin Cattle wrote:
Acutally - just wandering, is there a publicly visible bug/issue I can
use as a reference for this ?
Cheers,
Just
On Tue, 19 May 2026 at 17:57, Justin Cattle <[email protected]> wrote:
Hi David,
Glad to have surfaced the issue in that case, and we'll live with
the warning for now.
Thanks!
Cheers,
Just
On Tue, 19 May 2026 at 15:37, David Petera via Bird-users
<[email protected]> wrote:
Hi Just,
I've briefly looked into the configuration code and it indeed
seems like current implementation demands thread group for BFD
to be named 'express'...
This is definitely an oversight and we will fix that once we
have more time on our hands.
In the meantime having the warning is probably your best option)
Thanks for spotting this and happy routing!
David
David Petera (he/him) | BIRD Tech Support | CZ.NIC, z.s.p.o.
On 5/19/26 14:21, Justin Cattle wrote:
Hi,
I've been testing migrating to bird3. I preferred to redefine
the default threading configs so that everything is explicit,
rather than implicit. But, when I defined the ¬eress" group,
I got the following warning logged:
<WARN> Symbol 'express' overrides existing keyword
Rather than create create needless log lines, I though I
would fix that by creating my own custom thread group
instead, and use that for BFD.
I created:
thread group responsive {
threads 1;
max latency 10 ms;
min time 1 ms;
max time 10 ms;
wakeup time 60 s;
}
protocol bfd {
thread group responsive;
interface "net0" {
interval 1000 ms;
multiplier 4;
};
interface "net1" {
interval 1000 ms;
multiplier 4;
};
}
However, the config validation then throws the following error:
<FATAL> Express thread group not configured and "express"
not found
Is this a bug, or something I'm doing wrong ?
Thanks!
Cheers,
Just
Notice:
This email is confidential and may contain copyright material
of members of the Ocado Group. Opinions and views expressed
in this message may not necessarily reflect the opinions and
views of the members of the Ocado Group.
If you are not the intended recipient, please notify us
immediately and delete all copies of this message. Please
note that it is your responsibility to scan this message for
viruses.
References to the "Ocado Group" are to Ocado Group plc
(registered in England and Wales with number 7098618) and its
subsidiary undertakings (as that expression is defined in the
Companies Act 2006) from time to time. The registered office
of Ocado Group plc is Buildings One & Two, Trident Place,
Mosquito Way, Hatfield, Hertfordshire, AL10 9UL.
Ocado Polska Sp. z o.o. posiada status dużego przedsiębiorcy
w rozumieniu ustawy o przeciwdziałaniu nadmiernym opóźnieniom
w transakcjach handlowych. / Ocado Polska Sp. z o.o. holds
the status of a large enterprise under the Act on
Counteracting Excessive Delays in Commercial Transactions.
Notice:
This email is confidential and may contain copyright material of
members of the Ocado Group. Opinions and views expressed in this
message may not necessarily reflect the opinions and views of the
members of the Ocado Group.
If you are not the intended recipient, please notify us immediately
and delete all copies of this message. Please note that it is your
responsibility to scan this message for viruses.
References to the "Ocado Group" are to Ocado Group plc (registered in
England and Wales with number 7098618) and its subsidiary undertakings
(as that expression is defined in the Companies Act 2006) from time to
time. The registered office of Ocado Group plc is Buildings One & Two,
Trident Place, Mosquito Way, Hatfield, Hertfordshire, AL10 9UL.
Ocado Polska Sp. z o.o. posiada status dużego przedsiębiorcy w
rozumieniu ustawy o przeciwdziałaniu nadmiernym opóźnieniom w
transakcjach handlowych. / Ocado Polska Sp. z o.o. holds the status of
a large enterprise under the Act on Counteracting Excessive Delays in
Commercial Transactions.
