infra issueshttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues2022-02-19T14:16:28Zhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10746mail IPv62022-02-19T14:16:28ZJ0WImail IPv6Forking from #6377:
IPv6 for `mail.alpinelinux.org`Forking from #6377:
IPv6 for `mail.alpinelinux.org`https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10744dev IPv62022-02-19T14:16:35ZJ0WIdev IPv6Forking from #6377:
IPv6 for `dev.alpinelinux.org`Forking from #6377:
IPv6 for `dev.alpinelinux.org`https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10741Live build log updates2022-01-07T18:13:39ZSören TempelLive build log updatesThis is a follow up to a short discussion I had yesterday with @kdaudt on `#alpine-infra`.
Presently, it seems that build logs are uploaded to [build.alpinelinux.org](https://build.alpinelinux.org) in a separate step after the build has...This is a follow up to a short discussion I had yesterday with @kdaudt on `#alpine-infra`.
Presently, it seems that build logs are uploaded to [build.alpinelinux.org](https://build.alpinelinux.org) in a separate step after the build has completed. As such, they are not available during the build which often makes it difficult to determine if there is a problem with the currently ongoing build (e.g. if the build is stuck which happens quite often on riscv64 for example).
IMHO it would be nice to have live buildlogs for all architectures to ease detection of hanging builds etc. Maybe this could be achieved by having the builders write logs to a NFS which could then also be mounted on the webserver powering [build.alpinelinux.org](https://build.alpinelinux.org) thereby having these files updated continuously?https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10736Migrate pkgs.a.o to pmOS python implementation2021-12-17T11:04:25ZCarlo LandmeterMigrate pkgs.a.o to pmOS python implementationThe current pkgs.a.o has been implemented with lua-turbo which unfortunately has not much upstream life.
In combination with luajit, this has been giving us troubles and needing to switch back to regular lua.
The discussion has risen on...The current pkgs.a.o has been implemented with lua-turbo which unfortunately has not much upstream life.
In combination with luajit, this has been giving us troubles and needing to switch back to regular lua.
The discussion has risen on IRC to switch to the python [alternative](http://pkgs.postmarketos.org/packages) created by PmOS.
The sources can be found [here](https://gitlab.com/postmarketOS/apkbrowser).
although most features have been ported over, there is one feature that has been left out, Fedora [Anitya](https://release-monitoring.org/) release monitoring.
This feature has previously been added by @jirutka. @jirutka, are you interested in adding a similar feature to the python implementation?
As previously discussed on IRC, we would like to move this forward even if that means if this feature is missing.
/cc @alpine/infraCarlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10714Backport bot2021-05-26T22:16:22ZJ0WIBackport botWould be great to have a bot (similar to [this](https://github.com/rullzer/backportbot)) to create backport MRs from GitLab comments.Would be great to have a bot (similar to [this](https://github.com/rullzer/backportbot)) to create backport MRs from GitLab comments.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10713CI: Only run builds for specified archs2022-01-23T07:30:42Zomniomni+alpine@hack.orgCI: Only run builds for specified archsTwo reasons. Its unnessecary to spend cycles on spinning up and down unneded workers and also to show "success" for archs you can't (and/or didn't) build for.Two reasons. Its unnessecary to spend cycles on spinning up and down unneded workers and also to show "success" for archs you can't (and/or didn't) build for.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10712Migrate https://github.com/alpinelinux/docker-alpine to GitLab2021-11-12T17:31:42ZTBKMigrate https://github.com/alpinelinux/docker-alpine to GitLabAfter migration please update the project description with a link to gitlab and use the archive feature to block new issues/PR from being created.After migration please update the project description with a link to gitlab and use the archive feature to block new issues/PR from being created.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10710add interwiki link for arch linux2021-01-19T18:49:25ZAlex Xu (Hello71)add interwiki link for arch linux90% of alpine wiki just duplicates arch wiki but out-of-date. let's just link to them where appropriate.90% of alpine wiki just duplicates arch wiki but out-of-date. let's just link to them where appropriate.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10699migrate away from lists.a.o SourceHut implementation2020-08-05T08:56:01ZCarlo Landmetermigrate away from lists.a.o SourceHut implementationlists.a.o is no longer maintained according to the current maintainer.
/cc @kdaudtlists.a.o is no longer maintained according to the current maintainer.
/cc @kdaudtCarlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10690Contributors should be able to remove S-requested-changes label2020-05-17T13:33:58ZKonstantin KulikovContributors should be able to remove S-requested-changes labelDevs ask contributors to make changes in MR and add S-requested-changes label.
They push updates, but the label stays and MR sometimes gets forgotten.
Contributors should be able to remove that label themselves, instead of pinging devs ...Devs ask contributors to make changes in MR and add S-requested-changes label.
They push updates, but the label stays and MR sometimes gets forgotten.
Contributors should be able to remove that label themselves, instead of pinging devs directly.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10688Signature files missing for most netboot images2021-07-28T07:23:02ZChristian KohlschütterSignature files missing for most netboot imagesMost Alpine netboot images cannot be verified by alpine-ipxe because the corresponding .sig files (e.g., vmlinuz-vanilla.sig) are missing for most versions.
There are signatures available for _some_ versions (see https://boot.alpinelinu...Most Alpine netboot images cannot be verified by alpine-ipxe because the corresponding .sig files (e.g., vmlinuz-vanilla.sig) are missing for most versions.
There are signatures available for _some_ versions (see https://boot.alpinelinux.org/sig/), so the code signing verification in https://boot.alpinelinux.org/boot.ipxe may or may not work, depending on what version you try.
I understand that it's sometimes recommended to re-sign these images ourselves, and to use a custom-compiled version of iPXE with the corresponding root certificate, however this may not always be feasible or desired.
As a first step, I suggest to automatically include these .sig files upon releasing a version and deploy them to all mirror servers (e.g., http://dl-cdn.alpinelinux.org/) and the netboot tarballs on the website. This may also allow other uses of verification, outside the iPXE use case.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10682Aports pipeline check against release-monitoring.org2022-08-18T16:20:12ZTBKAports pipeline check against release-monitoring.orgWould it be possible to add to the CI pipeline a validation step checking if the aport is monitored by Anitya (https://release-monitoring.org/) ?
https://release-monitoring.org/static/docs/api.html
The goal is to get better coverage wh...Would it be possible to add to the CI pipeline a validation step checking if the aport is monitored by Anitya (https://release-monitoring.org/) ?
https://release-monitoring.org/static/docs/api.html
The goal is to get better coverage which hopefully will resulting in faster upgrades by the maintainer.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10680Cleanup of github repositories2020-04-19T12:26:53ZCarlo LandmeterCleanup of github repositorieswith #10675 underway we should think about cleaning up github.com/alpinelinux.
Currently it can be confusing for users which tools are used primarily for our development.
I think it would be best if we use the same policy as we have disc...with #10675 underway we should think about cleaning up github.com/alpinelinux.
Currently it can be confusing for users which tools are used primarily for our development.
I think it would be best if we use the same policy as we have discussed regarding git.a.o.
We choose to only sync/mirror our base tools like aport/abuild/apk-tools and similar.
The rest of the projects we can remove or set as discontinued whichever is prefered.
Currently the majority of the github projects are synced by jirutka's `git-mirror-syncd` sync tool.
I guess it makes sense to start syncing from GitLab ones we moved projects from git.a.o to GitLab.
I made the projects a task list so they can be selected which should be moved and or deleted/archived.
## Github projects
* [ ] aports
* [ ] alpine-mksite
* [ ] docker-alpine
* [ ] apk-tools
* [ ] alpine-docker-gitlab
* [ ] aports-turbo
* [ ] abuild
* [ ] build-server-status
* [ ] alpine-chroot-install
* [ ] awall
* [ ] ca-certificates
* [ ] alpine-secdb
* [ ] docker-abuild
* [ ] mkinitfs
* [ ] alpine-make-rootfs
* [ ] alpine-make-vm-image
* [ ] alpine-conf
* [ ] turbo-paste
* [ ] alpine-drone-ci
* [ ] lua-aports
* [ ] alpine-mirror-status
* [ ] alpine-iso
* [ ] alpine-netboot
* [ ] alpine-backup
* [ ] alpine-wiki
* [ ] alpine-baselayout
* [ ] alpine_bootstrap
* [ ] linux-stable-grsec
## Github mirrored projects by git-mirror-syncd
* aports
* abuild
* apk-tools
* alpine-backup
* alpine-baselayout
* alpine-conf
* alpine-drone-ci
* alpine-iso
* alpine-mirror-status
* alpine-mksite
* alpine-netboot
* awall
* ca-certificates
* docker-abuild
* linux-stable-grsec
* lua-aports
* mkinitfsCarlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10677Add a static site for capative portals2020-03-21T11:10:23ZRasmus Thomsenoss@cogitri.devAdd a static site for capative portalsIt'd be nice if we hosted a TXT file somewhere with some recognisable string (e.g. "OK" or SUCCESS") like [Fedora does](https://fedoraproject.org/static/hotspot.txt). This site can be used with software like NetworkManager to check wheth...It'd be nice if we hosted a TXT file somewhere with some recognisable string (e.g. "OK" or SUCCESS") like [Fedora does](https://fedoraproject.org/static/hotspot.txt). This site can be used with software like NetworkManager to check whether a connection requires login (like most public WiFis do). This address is queried upon connecting to a network (to check if an immediate login is required) and then every so often (to check if the network requires you to log in again after some amount of time has passed) and is basically just a check if the site can be reached and outputs the desired result or if the user is redirected to some login page.
There have been some privacy concerns about this since the hoster of the website could collect the IPs that query the website, e.g. to count users. As such it'd make sense if we host this site since we're a trusted party already - users already query our servers to update repos etc.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10676CI detection of circular dependencies2022-01-22T02:38:18ZAriadne Conillariadne@ariadne.spaceCI detection of circular dependenciesI have had to break a few circular dependencies recently. It would be nice if the CI scripts could detect these circular dependencies so they don't make it in to begin with...I have had to break a few circular dependencies recently. It would be nice if the CI scripts could detect these circular dependencies so they don't make it in to begin with...https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10671GitLab upgrade and testing procedure2020-04-02T19:41:08ZCarlo LandmeterGitLab upgrade and testing procedureWe should test run our GitLab upgrades with a test framework/procedure to test basic features.
Currently we run a new VPS on Linode from the periodic backups made by Linode.
After it boots we need to adjust some settings to make the doc...We should test run our GitLab upgrades with a test framework/procedure to test basic features.
Currently we run a new VPS on Linode from the periodic backups made by Linode.
After it boots we need to adjust some settings to make the docker containers run.
@kdaudt can you add those notes in this ticket?
For test procedure we can run:
https://docs.gitlab.com/ee/administration/raketasks/check.html
We can also run some docker container on the same docker network with would have a script/tools to run basic tests like:
* Access webui (https)
* Access API
* Create/delete project
* Push/Pull repositories
* ...Carlo LandmeterCarlo Landmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10669GitLabs postgres instance reports duplicate keys2020-01-06T22:51:32ZCarlo LandmeterGitLabs postgres instance reports duplicate keys```
postgres_1 | 2019-12-14 05:50:21.362 UTC [869] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-14 05:50:21.362 UTC [869] DETAIL: Key (namespace_id)=(1941) alread...```
postgres_1 | 2019-12-14 05:50:21.362 UTC [869] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-14 05:50:21.362 UTC [869] DETAIL: Key (namespace_id)=(1941) already exists.
postgres_1 | 2019-12-14 05:50:21.362 UTC [869] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-14 15:50:18.933 UTC [1916] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-14 15:50:18.933 UTC [1916] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2019-12-14 15:50:18.933 UTC [1916] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 00:19:59.432 UTC [2816] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 00:19:59.432 UTC [2816] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-15 00:19:59.432 UTC [2816] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 00:19:59.780 UTC [2816] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 00:19:59.780 UTC [2816] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-15 00:19:59.780 UTC [2816] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 18:14:18.472 UTC [4669] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 18:14:18.472 UTC [4669] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-15 18:14:18.472 UTC [4669] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 21:00:32.850 UTC [4959] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 21:00:32.850 UTC [4959] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-15 21:00:32.850 UTC [4959] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 21:28:47.885 UTC [4932] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 21:28:47.885 UTC [4932] DETAIL: Key (namespace_id)=(1654) already exists.
postgres_1 | 2019-12-15 21:28:47.885 UTC [4932] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-15 23:50:23.674 UTC [5236] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-15 23:50:23.674 UTC [5236] DETAIL: Key (namespace_id)=(1654) already exists.
postgres_1 | 2019-12-15 23:50:23.674 UTC [5236] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 04:50:26.742 UTC [5745] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 04:50:26.742 UTC [5745] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-16 04:50:26.742 UTC [5745] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 08:50:32.829 UTC [6186] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 08:50:32.829 UTC [6186] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-16 08:50:32.829 UTC [6186] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 08:50:32.892 UTC [6187] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 08:50:32.892 UTC [6187] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-16 08:50:32.892 UTC [6187] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 09:50:26.646 UTC [6285] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 09:50:26.646 UTC [6285] DETAIL: Key (namespace_id)=(1654) already exists.
postgres_1 | 2019-12-16 09:50:26.646 UTC [6285] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 12:50:30.812 UTC [6600] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 12:50:30.812 UTC [6600] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-16 12:50:30.812 UTC [6600] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 17:25:06.921 UTC [7115] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 17:25:06.921 UTC [7115] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-16 17:25:06.921 UTC [7115] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-16 20:09:36.920 UTC [7423] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-16 20:09:36.920 UTC [7423] DETAIL: Key (namespace_id)=(972) already exists.
postgres_1 | 2019-12-16 20:09:36.920 UTC [7423] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-17 07:50:18.165 UTC [8639] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-17 07:50:18.165 UTC [8639] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-17 07:50:18.165 UTC [8639] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-17 12:50:17.576 UTC [9189] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-17 12:50:17.576 UTC [9189] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-17 12:50:17.576 UTC [9189] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-18 02:50:08.814 UTC [10668] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-18 02:50:08.814 UTC [10668] DETAIL: Key (namespace_id)=(2103) already exists.
postgres_1 | 2019-12-18 02:50:08.814 UTC [10668] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-18 15:19:22.626 UTC [11986] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-18 15:19:22.626 UTC [11986] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-18 15:19:22.626 UTC [11986] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-19 08:59:41.315 UTC [13879] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-19 08:59:41.315 UTC [13879] DETAIL: Key (namespace_id)=(2082) already exists.
postgres_1 | 2019-12-19 08:59:41.315 UTC [13879] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-19 15:58:21.772 UTC [14669] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-19 15:58:21.772 UTC [14669] DETAIL: Key (namespace_id)=(460) already exists.
postgres_1 | 2019-12-19 15:58:21.772 UTC [14669] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-19 17:33:23.383 UTC [14837] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-19 17:33:23.383 UTC [14837] DETAIL: Key (namespace_id)=(460) already exists.
postgres_1 | 2019-12-19 17:33:23.383 UTC [14837] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-19 19:15:13.443 UTC [14984] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-19 19:15:13.443 UTC [14984] DETAIL: Key (namespace_id)=(314) already exists.
postgres_1 | 2019-12-19 19:15:13.443 UTC [14984] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-19 20:17:19.220 UTC [15133] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-19 20:17:19.220 UTC [15133] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-19 20:17:19.220 UTC [15133] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-20 13:19:52.929 UTC [16952] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-20 13:19:52.929 UTC [16952] DETAIL: Key (namespace_id)=(209) already exists.
postgres_1 | 2019-12-20 13:19:52.929 UTC [16952] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-20 13:50:29.841 UTC [17014] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-20 13:50:29.841 UTC [17014] DETAIL: Key (namespace_id)=(2129) already exists.
postgres_1 | 2019-12-20 13:50:29.841 UTC [17014] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-20 15:22:08.018 UTC [17186] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-20 15:22:08.018 UTC [17186] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2019-12-20 15:22:08.018 UTC [17186] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-20 18:50:12.816 UTC [17555] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-20 18:50:12.816 UTC [17555] DETAIL: Key (namespace_id)=(460) already exists.
postgres_1 | 2019-12-20 18:50:12.816 UTC [17555] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-20 20:31:15.109 UTC [17791] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-20 20:31:15.109 UTC [17791] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-20 20:31:15.109 UTC [17791] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-21 11:21:36.722 UTC [19272] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-21 11:21:36.722 UTC [19272] DETAIL: Key (namespace_id)=(314) already exists.
postgres_1 | 2019-12-21 11:21:36.722 UTC [19272] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-21 12:52:55.821 UTC [19458] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-21 12:52:55.821 UTC [19458] DETAIL: Key (namespace_id)=(314) already exists.
postgres_1 | 2019-12-21 12:52:55.821 UTC [19458] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-21 19:50:12.460 UTC [20267] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-21 19:50:12.460 UTC [20267] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-21 19:50:12.460 UTC [20267] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-21 21:50:21.007 UTC [20446] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-21 21:50:21.007 UTC [20446] DETAIL: Key (namespace_id)=(169) already exists.
postgres_1 | 2019-12-21 21:50:21.007 UTC [20446] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-21 23:50:06.221 UTC [20658] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-21 23:50:06.221 UTC [20658] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-21 23:50:06.221 UTC [20658] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-22 00:19:55.864 UTC [20730] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-22 00:19:55.864 UTC [20730] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-22 00:19:55.864 UTC [20730] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-22 13:18:01.263 UTC [22158] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-22 13:18:01.263 UTC [22158] DETAIL: Key (namespace_id)=(1672) already exists.
postgres_1 | 2019-12-22 13:18:01.263 UTC [22158] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-22 18:46:45.687 UTC [22784] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-22 18:46:45.687 UTC [22784] DETAIL: Key (namespace_id)=(169) already exists.
postgres_1 | 2019-12-22 18:46:45.687 UTC [22784] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 01:18:22.441 UTC [23521] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 01:18:22.441 UTC [23521] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-23 01:18:22.441 UTC [23521] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 02:33:01.938 UTC [23612] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 02:33:01.938 UTC [23612] DETAIL: Key (namespace_id)=(1717) already exists.
postgres_1 | 2019-12-23 02:33:01.938 UTC [23612] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 04:50:06.946 UTC [23914] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 04:50:06.946 UTC [23914] DETAIL: Key (namespace_id)=(460) already exists.
postgres_1 | 2019-12-23 04:50:06.946 UTC [23914] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 12:23:35.095 UTC [24762] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 12:23:35.095 UTC [24762] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-23 12:23:35.095 UTC [24762] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 12:44:26.221 UTC [24804] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 12:44:26.221 UTC [24804] DETAIL: Key (namespace_id)=(1672) already exists.
postgres_1 | 2019-12-23 12:44:26.221 UTC [24804] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 13:56:28.636 UTC [24931] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 13:56:28.636 UTC [24931] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-23 13:56:28.636 UTC [24931] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 17:20:11.483 UTC [25265] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 17:20:11.483 UTC [25265] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2019-12-23 17:20:11.483 UTC [25265] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-23 17:32:40.047 UTC [25312] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-23 17:32:40.047 UTC [25312] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-23 17:32:40.047 UTC [25312] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-24 08:50:04.500 UTC [26969] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-24 08:50:04.500 UTC [26969] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-24 08:50:04.500 UTC [26969] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-24 20:50:28.554 UTC [28347] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-24 20:50:28.554 UTC [28347] DETAIL: Key (namespace_id)=(209) already exists.
postgres_1 | 2019-12-24 20:50:28.554 UTC [28347] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-25 06:23:59.355 UTC [29342] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-25 06:23:59.355 UTC [29342] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-25 06:23:59.355 UTC [29342] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-25 06:51:59.251 UTC [29439] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-25 06:51:59.251 UTC [29439] DETAIL: Key (namespace_id)=(460) already exists.
postgres_1 | 2019-12-25 06:51:59.251 UTC [29439] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-25 16:21:44.025 UTC [30551] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-25 16:21:44.025 UTC [30551] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-25 16:21:44.025 UTC [30551] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-25 21:50:32.578 UTC [31167] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-25 21:50:32.578 UTC [31167] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-25 21:50:32.578 UTC [31167] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 04:50:34.086 UTC [31967] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 04:50:34.086 UTC [31967] DETAIL: Key (namespace_id)=(972) already exists.
postgres_1 | 2019-12-26 04:50:34.086 UTC [31967] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 05:40:00.132 UTC [32048] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 05:40:00.132 UTC [32048] DETAIL: Key (namespace_id)=(169) already exists.
postgres_1 | 2019-12-26 05:40:00.132 UTC [32048] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 07:50:21.810 UTC [32293] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 07:50:21.810 UTC [32293] DETAIL: Key (namespace_id)=(682) already exists.
postgres_1 | 2019-12-26 07:50:21.810 UTC [32293] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 10:50:05.166 UTC [32643] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 10:50:05.166 UTC [32643] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-26 10:50:05.166 UTC [32643] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 14:23:00.273 UTC [576] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 14:23:00.273 UTC [576] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-26 14:23:00.273 UTC [576] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 15:53:13.773 UTC [705] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 15:53:13.773 UTC [705] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-26 15:53:13.773 UTC [705] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 16:50:33.091 UTC [842] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 16:50:33.091 UTC [842] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-26 16:50:33.091 UTC [842] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-26 19:22:32.452 UTC [1129] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-26 19:22:32.452 UTC [1129] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-26 19:22:32.452 UTC [1129] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-27 01:20:17.604 UTC [1769] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-27 01:20:17.604 UTC [1769] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-27 01:20:17.604 UTC [1769] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-27 01:20:18.893 UTC [1779] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-27 01:20:18.893 UTC [1779] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-27 01:20:18.893 UTC [1779] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-27 03:50:22.370 UTC [2053] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-27 03:50:22.370 UTC [2053] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-27 03:50:22.370 UTC [2053] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-27 05:50:12.523 UTC [2258] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-27 05:50:12.523 UTC [2258] DETAIL: Key (namespace_id)=(169) already exists.
postgres_1 | 2019-12-27 05:50:12.523 UTC [2258] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-27 20:05:26.041 UTC [3790] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-27 20:05:26.041 UTC [3790] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-27 20:05:26.041 UTC [3790] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-28 15:50:05.165 UTC [5906] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-28 15:50:05.165 UTC [5906] DETAIL: Key (namespace_id)=(430) already exists.
postgres_1 | 2019-12-28 15:50:05.165 UTC [5906] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-28 22:50:10.134 UTC [6703] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-28 22:50:10.134 UTC [6703] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-28 22:50:10.134 UTC [6703] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 00:20:23.564 UTC [6871] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 00:20:23.564 UTC [6871] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-29 00:20:23.564 UTC [6871] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 02:19:58.071 UTC [7089] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 02:19:58.071 UTC [7089] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-29 02:19:58.071 UTC [7089] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 03:50:05.810 UTC [7239] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 03:50:05.810 UTC [7239] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-29 03:50:05.810 UTC [7239] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 05:20:29.081 UTC [7431] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 05:20:29.081 UTC [7431] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2019-12-29 05:20:29.081 UTC [7431] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 20:45:52.036 UTC [9160] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 20:45:52.036 UTC [9160] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-29 20:45:52.036 UTC [9160] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 22:25:25.957 UTC [9338] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 22:25:25.957 UTC [9338] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-29 22:25:25.957 UTC [9338] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-29 23:58:53.301 UTC [9513] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-29 23:58:53.301 UTC [9513] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2019-12-29 23:58:53.301 UTC [9513] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-30 12:39:54.501 UTC [10917] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-30 12:39:54.501 UTC [10917] DETAIL: Key (namespace_id)=(169) already exists.
postgres_1 | 2019-12-30 12:39:54.501 UTC [10917] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-31 12:50:28.826 UTC [13632] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-31 12:50:28.826 UTC [13632] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2019-12-31 12:50:28.826 UTC [13632] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-31 18:36:11.514 UTC [14268] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-31 18:36:11.514 UTC [14268] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2019-12-31 18:36:11.514 UTC [14268] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2019-12-31 19:50:06.872 UTC [14429] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2019-12-31 19:50:06.872 UTC [14429] DETAIL: Key (namespace_id)=(1301) already exists.
postgres_1 | 2019-12-31 19:50:06.872 UTC [14429] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-02 01:50:06.036 UTC [17703] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-02 01:50:06.036 UTC [17703] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2020-01-02 01:50:06.036 UTC [17703] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-02 04:43:22.700 UTC [17991] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-02 04:43:22.700 UTC [17991] DETAIL: Key (namespace_id)=(2171) already exists.
postgres_1 | 2020-01-02 04:43:22.700 UTC [17991] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-02 11:07:49.127 UTC [18748] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-02 11:07:49.127 UTC [18748] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2020-01-02 11:07:49.127 UTC [18748] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-02 17:49:39.431 UTC [19539] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-02 17:49:39.431 UTC [19539] DETAIL: Key (namespace_id)=(1282) already exists.
postgres_1 | 2020-01-02 17:49:39.431 UTC [19539] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-02 21:20:28.963 UTC [19927] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-02 21:20:28.963 UTC [19927] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2020-01-02 21:20:28.963 UTC [19927] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 01:50:24.104 UTC [20460] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 01:50:24.104 UTC [20460] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2020-01-03 01:50:24.104 UTC [20460] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 03:22:45.812 UTC [20625] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 03:22:45.812 UTC [20625] DETAIL: Key (namespace_id)=(1941) already exists.
postgres_1 | 2020-01-03 03:22:45.812 UTC [20625] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 11:43:26.441 UTC [21520] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 11:43:26.441 UTC [21520] DETAIL: Key (namespace_id)=(209) already exists.
postgres_1 | 2020-01-03 11:43:26.441 UTC [21520] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 12:18:24.181 UTC [21666] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 12:18:24.181 UTC [21666] DETAIL: Key (namespace_id)=(980) already exists.
postgres_1 | 2020-01-03 12:18:24.181 UTC [21666] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 17:11:28.817 UTC [22202] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 17:11:28.817 UTC [22202] DETAIL: Key (namespace_id)=(1717) already exists.
postgres_1 | 2020-01-03 17:11:28.817 UTC [22202] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 17:24:30.778 UTC [22202] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 17:24:30.778 UTC [22202] DETAIL: Key (namespace_id)=(209) already exists.
postgres_1 | 2020-01-03 17:24:30.778 UTC [22202] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 18:41:50.591 UTC [22416] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 18:41:50.591 UTC [22416] DETAIL: Key (namespace_id)=(1717) already exists.
postgres_1 | 2020-01-03 18:41:50.591 UTC [22416] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 20:13:52.098 UTC [22576] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 20:13:52.098 UTC [22576] DETAIL: Key (namespace_id)=(1717) already exists.
postgres_1 | 2020-01-03 20:13:52.098 UTC [22576] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 21:35:05.772 UTC [22718] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 21:35:05.772 UTC [22718] DETAIL: Key (namespace_id)=(1654) already exists.
postgres_1 | 2020-01-03 21:35:05.772 UTC [22718] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 21:50:34.558 UTC [22745] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 21:50:34.558 UTC [22745] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2020-01-03 21:50:34.558 UTC [22745] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-03 22:06:58.381 UTC [22722] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-03 22:06:58.381 UTC [22722] DETAIL: Key (namespace_id)=(1424) already exists.
postgres_1 | 2020-01-03 22:06:58.381 UTC [22722] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 05:50:09.301 UTC [23571] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 05:50:09.301 UTC [23571] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2020-01-04 05:50:09.301 UTC [23571] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 08:52:45.445 UTC [23907] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 08:52:45.445 UTC [23907] DETAIL: Key (namespace_id)=(1590) already exists.
postgres_1 | 2020-01-04 08:52:45.445 UTC [23907] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 13:50:18.562 UTC [24423] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 13:50:18.562 UTC [24423] DETAIL: Key (namespace_id)=(1941) already exists.
postgres_1 | 2020-01-04 13:50:18.562 UTC [24423] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 17:48:27.964 UTC [24830] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 17:48:27.964 UTC [24830] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2020-01-04 17:48:27.964 UTC [24830] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 20:37:17.741 UTC [25220] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 20:37:17.741 UTC [25220] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2020-01-04 20:37:17.741 UTC [25220] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 22:13:59.541 UTC [25392] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 22:13:59.541 UTC [25392] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2020-01-04 22:13:59.541 UTC [25392] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-04 23:50:01.253 UTC [25587] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-04 23:50:01.253 UTC [25587] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2020-01-04 23:50:01.253 UTC [25587] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-05 16:17:45.517 UTC [27403] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-05 16:17:45.517 UTC [27403] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2020-01-05 16:17:45.517 UTC [27403] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-05 20:50:38.037 UTC [27922] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-05 20:50:38.037 UTC [27922] DETAIL: Key (namespace_id)=(1606) already exists.
postgres_1 | 2020-01-05 20:50:38.037 UTC [27922] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-05 23:50:09.699 UTC [28210] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-05 23:50:09.699 UTC [28210] DETAIL: Key (namespace_id)=(1128) already exists.
postgres_1 | 2020-01-05 23:50:09.699 UTC [28210] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-06 09:26:13.119 UTC [29332] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-06 09:26:13.119 UTC [29332] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2020-01-06 09:26:13.119 UTC [29332] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-06 11:27:13.585 UTC [29586] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-06 11:27:13.585 UTC [29586] DETAIL: Key (namespace_id)=(1941) already exists.
postgres_1 | 2020-01-06 11:27:13.585 UTC [29586] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-06 15:17:13.865 UTC [30041] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-06 15:17:13.865 UTC [30041] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2020-01-06 15:17:13.865 UTC [30041] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
postgres_1 | 2020-01-06 15:17:13.986 UTC [30041] ERROR: duplicate key value violates unique constraint "namespace_aggregation_schedules_pkey"
postgres_1 | 2020-01-06 15:17:13.986 UTC [30041] DETAIL: Key (namespace_id)=(2) already exists.
postgres_1 | 2020-01-06 15:17:13.986 UTC [30041] STATEMENT: INSERT INTO "namespace_aggregation_schedules" ("namespace_id") VALUES ($1) RETURNING "namespace_id"
```https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10667aports anitya (release-monitoring) checks stopped working2020-01-06T13:06:55ZJakub Jirutkaaports anitya (release-monitoring) checks stopped workingIt seems that it doesn’t work for almost two months already.
@clandmeterIt seems that it doesn’t work for almost two months already.
@clandmeterhttps://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10665The builder logs should include the current environment2020-01-22T20:51:45ZSören TempelThe builder logs should include the current environment@kdaudt and I spent way too much time [debugging a bmake build failure](https://git.alpinelinux.org/aports/commit/?id=ff5117155c530c327ec13a639499dc19e5536ee6) which could be reproduced only on the `x86*` builders because these builders ...@kdaudt and I spent way too much time [debugging a bmake build failure](https://git.alpinelinux.org/aports/commit/?id=ff5117155c530c327ec13a639499dc19e5536ee6) which could be reproduced only on the `x86*` builders because these builders add the flag `-l24` to the `MAKEFLAGS` environment variable in `/etc/abuild.conf`. I believe we would have found this issue way faster if the build log produced by `build.alpinelinux.org` contained the output of `env(1)`.
This could be added to abuild itself. Though I think the output is not that useful in the general case, i.e. I know which environment variable I set on my development machine, it is primarily useful on the builders imho.https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10664parse the RSS feed of security updates to the main web page event those git c...2019-12-19T15:37:25ZPICCORO Lenz McKAYparse the RSS feed of security updates to the main web page event those git commits!as discuss here: https://lists.alpinelinux.org/~alpine/users/%3C2013507513.1487922.1576682692429%40mail.yahoo.com%3E#%3CCALci+FTUP_6SStZkqtNxkDyFHVU1uSOKHnx-r=rVuReErqgJGg@mail.gmail.com%3E
as i can see it, git commits are parsed to mai...as discuss here: https://lists.alpinelinux.org/~alpine/users/%3C2013507513.1487922.1576682692429%40mail.yahoo.com%3E#%3CCALci+FTUP_6SStZkqtNxkDyFHVU1uSOKHnx-r=rVuReErqgJGg@mail.gmail.com%3E
as i can see it, git commits are parsed to main page.. **so also the security issues RSS feed can also be parsed! i think *those are more important rather than the commits..* **
![image](/uploads/52766f3bd47fbd73a85e34459294f3e5/image.png)