unreliability
and slowness, especially when doing large batches of builds.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
tions/reference/workflow-syntax-for-github-actions#example-preventing-a-specific-failing-matrix-job-from-failing-a-workflow-run>
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
o/docs/reference/using-api/deprecation-guide/#v1-22
> <https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-22>
>
> Regards
> Alex
>
--
Dinko Korunic Senior System Engineer / R&D
https://hr.linkedin.com/in/dkorunic https://twitter.com/dkorunic
it appears it
> fails to checkout from the remote repository.
>
> Thanks Olaf
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
ot been able to find the docker image for haproxy. 2.5.8
> today. Will this be posted today?
>
> Keep up the good work.
> Thanks all
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
ecide to do Debian or Ubuntu first depending on existing Docker Hub
statistics for the popularity of haproxytech images.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
/haproxy-docker-ubuntu-quic
Let me know if you spot any issues and/or have any problems with these.
As other our haproxytech Docker images, these will auto-rebuild on:
- dataplaneapi releases
- HAProxy CE releases
including also:
- QUICTLS/OpenSSL releases
Kind regards,
D.
--
Dinko Korunic
On 19.03.2023., at 19:54, Dinko Korunic wrote:
> Images are available at the usual Docker Hub repositories:
> - https://hub.docker.com/repository/docker/haproxytech/haproxy-debian-quic
> - https://hub.docker.com/repository/docker/haproxytech/haproxy-ubuntu-quic
Ah, my apologies, these s
-alpine
https://github.com/haproxytech/haproxy-docker-ubuntu/pkgs/container/haproxy-docker-ubuntu
https://github.com/haproxytech/haproxy-docker-debian/pkgs/container/haproxy-docker-debian
Kind regards,
D.
> On 19.03.2023., at 19:54, Dinko Korunic wrote:
>
> Dear community,
>
>
reinstalling a full-featured
> desktop operating system, which seems awkward and counter productive at
> best.
>
> I don't know if that's automatically done based on broken dependencies
> or if it is caused by a preliminary upgrade of the whole system, but I
> th
it is not an issue and we can install socat. but under some
> circumstances socat refuses to install without brew update
>
> чт, 9 июл. 2020 г. в 12:42, Dinko Korunic <mailto:dinko.koru...@gmail.com>>:
> I would suggest using HOMEBREW_NO_AUTO_UPDATE environment variable to avoid
My apologies if I have missed to mention anything, I am not up to date with
current DNS changes as I used to be.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
haven’t had Kube-DNS anywhere and i think that CoreDNS is supposed to
be way to go from Kube-DNS. Hope this helps.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
. Ilya will need to send it to you unless you happen to
> have it somewhere in your email archives.
>
> it is supposed to be the next step :)
>
> I do not have access neither to Coverity token, nor to github.
> Dinko can grab a token from Coverity and pass to Willy.
>
>
>
> Best regards
> Tim Düsterhus
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
r haproxytech (https://hub.docker.com/u/haproxytech) HAProxy CE
images as well, they will get rebuilt on official base image (Debian, Ubuntu,
Alpine, etc.) being rebuilt.
This includes regular HAProxy CE images, Ingress Controller images, etc.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
Perhaps that would be a better starting point?
>
> https://hub.docker.com/r/haproxytech/haproxy-alpine
Hi Lukas,
I am maintaining haproxytech Docker images and I can easily make that (slz
being used) happen, if that’s what community would like to see.
Kind regards,
D.
--
Dinko Korunic
os (performance)
outweigh the cons (increased target size), I’ll take care of it for haproxytech
images and these changes would be also propagated to Ingress Controller image
as well.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
new haproxytech/haproxy* Docker images have SLZ enabled and
statically linked in the haproxy binary.
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
kagers to test and adjust their build process if needed.
>
Willy,
I think this is great from the packagers’ point of view, as it will make build
scripts (for Docker, embedded devices and what not) easier to maintain and one
important dependancy less to worry about.
D.
--
Dinko Korunic
ic analysis because of
> noise. Anyway, it finds bugs, why not to use it?
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
all the access required for doing so right now.
Kind regards,
D.
> On 17 Jul 2019, at 13:18, Илья Шипицин wrote:
>
> Hello, yep, contributor/member would be nice. Also, I can setup automated
> travis-ci scans
>
> On Wed, Jul 17, 2019, 3:27 PM Dinko Korunic <mailto:di
://github.com/haproxy/haproxy
> <https://github.com/haproxy/haproxy>) ?
>
> ср, 17 июл. 2019 г. в 16:36, Dinko Korunic <mailto:dinko.koru...@gmail.com>>:
> Dear Илья,
>
> I’ve increased your access level to Contributor/Member. I terms of Travis-CI
> s
custom Coverity Scan function
models yet?
Kind regards,
D.
> On 1 Aug 2019, at 11:59, Илья Шипицин wrote:
>
> also, I've no idea what to specify in COVERITY_SCAN_NOTIFICATION_EMAIL (which
> is mandatory)
>
> чт, 1 авг. 2019 г. в 12:32, Dinko Korunic <mail
s>
> >
> >
> > 2) setup COVERITY_SCAN_TOKEN = P6rHpv1618gwKWkVs7FfKQ
> >
> > 3) setup daily schedule
>
> All done now (with Dinko's new token). Thanks very much for the
> screenshot, it did help me.
>
> Let's see how it goes now. It says it's
nce".
> also, there's a good correlation, after "now fixed, good catch" coverity
> usually dismiss some bug.
>
> should we revisit those findings ?
>
>
>
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
st might be that at all the crashes I checked there were 2
> haproxy instances running. One of them has-sf , so the
> other is in "finishing mode".
>
>
Sander, can you try with “nosplice”?
https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#nosplice
same log target twice. I've
reported this and the explanation was that it's known and intended behavior.
Kind regards,
D.
--
Dinko Korunic PGP:0xEA160D0B
R&D Department Manager at Reflected
Hi,
The following really trivial patch fixes compilation issues on OSX (El
Capitan at least).
Kind regards,
D.
0001-BUG-MINOR-fix-osx-compilation-errors.patch
Description: Binary data
regards,
D.
-- Dinko Korunic ** Standard disclaimer applies **
On 11 September 2016 at 08:06:11, Willy Tarreau
(w...@1wt.eu(mailto:w...@1wt.eu)) wrote:
> Hi Dinko,
>
> On Fri, Sep 09, 2016 at 12:52:55AM -0700, Dinko Korunic wrote:
> > The following really trivial patch fixes com
public repositories are now as you said, 4
vCPU / 16 GB RAM:
https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners
Kind regards,
D.
--
Dinko Korunic ** Standard disclaimer applies **
Sent from OSF1 osf1v4b V4.0 564 alpha
30 matches
Mail list logo
