FOSS public instance issueshttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues2024-03-01T18:44:19Zhttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/450Hosting request for Traffic Intelligence2024-03-01T18:44:19ZNicolas SaunierHosting request for Traffic Intelligence## Description of the projects to be hosted
- Project Name: Traffic Intelligence
- Project URL: http://132.207.98.161:3000/
- Project Maintainers: Nicolas Saunier
- Project License: MIT
Please explain here how they meet our current cri...## Description of the projects to be hosted
- Project Name: Traffic Intelligence
- Project URL: http://132.207.98.161:3000/
- Project Maintainers: Nicolas Saunier
- Project License: MIT
Please explain here how they meet our current criteria.
### Main criteria
- [X] Free / Open Source
- [X] main development repositories
- [X] you are an official maintainer of the project
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
No
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
Small
- number of maintainers and regular contributors
Intermittent contributions by graduate students
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
Self-hosted at http://132.207.98.161:3000/ and https://hg.reactionary.software/repo/traffic-intelligence/
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [X] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/434Bringing back repositories long thought lost2024-02-15T10:31:45ZStephen ChappellBringing back repositories long thought lost## Description of the projects to be hosted
- Project Name: Confabulator
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/confabulator.html
- Project Maintainers: Stephen Paul Chappell
- Pr...## Description of the projects to be hosted
- Project Name: Confabulator
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/confabulator.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Game Development
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-game-development.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Network Applications
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-network-applications.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Network Programming
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-network-programming.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Python Graphics
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-python-graphics.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC GUI Programming
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-python-gui-programming.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Python Networked Game
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-python-networked-game.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: CSC Space Battle
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/csc-space-battle.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: Mythical Machine
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/mythical-machine.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: Predict Gold
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/predict-gold.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: QtPipe
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/qtpipe.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: QuizMe
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/quizme.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
- Project Name: XP
- Project URL: https://bitbucket-archive.softwareheritage.org/projects/st/stephen-paul-chappell/xp.html
- Project Maintainers: Stephen Paul Chappell
- Project License: The Unlicense
Please explain here how they meet our current criteria.
### Main criteria
- [X] Free / Open Source
- [X] main development repositories
- [X] you are an official maintainer of the project
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems? I thought these repositories were lost several years ago.
- estimation of the user base if possible, or number of downloads,
reverse dependencies… Many of these are related to Computer Science Camp (CSC) at a college.
- number of maintainers and regular contributors. There is one maintainer.
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow? I believe they only exist at the URLs given.
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [ ] just a project in your personal namespace
I do not really care how these things are brought back to life.
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/446Requests get produces incomplete json in Heptapod CI2024-02-09T15:24:14ZPierre AugierRequests get produces incomplete json in Heptapod CII can't use [PDM](https://github.com/pdm-project/pdm) in Heptapod CI because of a strange behavior of `requests` that I cannot reproduce elsewhere. In particular, using the same Docker image locally on my PC do not lead to this bug.
Exa...I can't use [PDM](https://github.com/pdm-project/pdm) in Heptapod CI because of a strange behavior of `requests` that I cannot reproduce elsewhere. In particular, using the same Docker image locally on my PC do not lead to this bug.
Example of job for which I get that https://foss.heptapod.net/fluiddyn/fluidsim/-/jobs/2206610
I use a very simple Python script containing
```
from datetime import datetime
from requests import Session
session = Session()
print("before get:", datetime.now())
resp = session.get(
"https://pypi.org/simple/flit-core/",
headers={
"Accept": "application/vnd.pypi.simple.v1+json",
"Cache-Control": "no-cache",
},
timeout=120,
)
print("after get:", datetime.now())
print(resp)
print(resp.content[-400:])
print(resp.json()["versions"])
```
On Heptapod CI, I get:
```
before get: 2024-01-03 10:22:01.244619
after get: 2024-01-03 10:22:01.277003
<Response [200]>
b'g/packages/4c/8f/bed80c03f71cb3a2935882f391b53d2510c359191e5e0361650fa02d1365/flit_core-3.1.0.tar.gz","yanked":false},{"core-metadata":false,"data-dist-info-metadata":false,"filename":"flit_core-3.2.0-py3-none-any.whl","hashes":{"sha256":"6f25843e908dfc3e907b6b9ee71e3d185bcb5aebab8c3431e4e34c261e5ff1b5"},"requires-python":">=3.4","size":45693,"upload-time":"2021-03-21T21:20:19.175500Z","url":"http'
Traceback (most recent call last):
File "/home/appuser/.local/lib/python3.9/site-packages/requests/models.py", line 960, in json
return complexjson.loads(self.content.decode(encoding), **kwargs)
File "/usr/local/lib/python3.9/json/__init__.py", line 346, in loads
return _default_decoder.decode(s)
File "/usr/local/lib/python3.9/json/decoder.py", line 337, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/local/lib/python3.9/json/decoder.py", line 353, in raw_decode
obj, end = self.scan_once(s, idx)
json.decoder.JSONDecodeError: Unterminated string starting at: line 1 column 10236 (char 10235)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/builds/fluiddyn/fluidsim/tmp_bug_unearth.py", line 20, in <module>
print(resp.json()["versions"])
File "/home/appuser/.local/lib/python3.9/site-packages/requests/models.py", line 968, in json
raise RequestsJSONDecodeError(e.msg, e.doc, e.pos)
requests.exceptions.JSONDecodeError: Unterminated string starting at: line 1 column 10236 (char 10235)
```
The json data is incomplete, which leads to the exception.
I'm looking for ideas to understand this annoying issue...https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/438Hosting request for my StreamModule project2024-02-09T14:11:57ZEric HopperHosting request for my StreamModule project## Description of the projects to be hosted
- Project Name: The StreamModule System
- Project URL: https://github.com/Omnifarious/StrMod
- Project Maintainers: Eric Hopper
- Project License: LGPLv2+
Please explain here how they meet ou...## Description of the projects to be hosted
- Project Name: The StreamModule System
- Project URL: https://github.com/Omnifarious/StrMod
- Project Maintainers: Eric Hopper
- Project License: LGPLv2+
Please explain here how they meet our current criteria.
### Main criteria
- [X] Free / Open Source
- [X] main development repositories
- [X] you are an official maintainer of the project
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
It's officially released, but nobody packages it. It can be built as a cmake project.
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
I don't know of anybody besides me that uses it. :-(
- number of maintainers and regular contributors
One
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
It was hosted on OSDN, but OSDN has apparently died.
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [X] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [X] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/421CI jobs fail on pulling images2024-01-17T11:46:26ZYannick GuernCI jobs fail on pulling imagesHello,
I'm not sure how to post this issue.
When a job is triggered with the "owner" role, all goes well.
```
Running with gitlab-runner hpd-0.6.0 (47e7e9a450f4)
on clever-cloud-docker Hh2oMJm3
Preparing the "docker" executor 00:48
...Hello,
I'm not sure how to post this issue.
When a job is triggered with the "owner" role, all goes well.
```
Running with gitlab-runner hpd-0.6.0 (47e7e9a450f4)
on clever-cloud-docker Hh2oMJm3
Preparing the "docker" executor 00:48
Using Docker executor with image heptapod.host:443/b2ck/dependency_proxy/containers/library/python:3.10 ...
Pulling docker image registry.heptapod.net/heptapod/heptapod-runner/helper:x86_64-0.6.0 ...
Using docker image sha256:bc72d7cab39fc33205004225c7ba6acd72460e31ab4e142bd8ce778e073afdc4 for registry.heptapod.net/heptapod/heptapod-runner/helper:x86_64-0.6.0 with digest registry.heptapod.net/heptapod/heptapod-runner/helper@sha256:782a71c6ca417df71589d8bd2604d98285eda99d4faa4ebe9c8779e0b9080d9a ...
Starting service heptapod.host/b2ck/dependency_proxy/containers/library/postgres:latest ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image heptapod.host:443/b2ck/dependency_proxy/containers/library/postgres:latest ...
Using docker image sha256:ec7f99c50d3c6f6a0d528b24ba6f55baa3de3af0f1c3ab3ec5d6183369f1e213 for heptapod.host:443/b2ck/dependency_proxy/containers/library/postgres:latest with digest heptapod.host:443/b2ck/dependency_proxy/containers/library/postgres@sha256:b7662e5572febc3380fd5773fa600824f0433b82935e7e5b4c180e9541b2b3d7 ...
Waiting for services to be up and running...
```
But the same job on the same runner triggered by a "developer" role ends up as a fail.
```
Running with gitlab-runner hpd-0.6.0 (47e7e9a450f4)
on clever-cloud-docker Hh2oMJm3
Preparing the "docker" executor 00:16
Using Docker executor with image heptapod.host:443/b2ck/dependency_proxy/containers/library/python:3.10 ...
Pulling docker image registry.heptapod.net/heptapod/heptapod-runner/helper:x86_64-0.6.0 ...
Using docker image sha256:bc72d7cab39fc33205004225c7ba6acd72460e31ab4e142bd8ce778e073afdc4 for registry.heptapod.net/heptapod/heptapod-runner/helper:x86_64-0.6.0 with digest registry.heptapod.net/heptapod/heptapod-runner/helper@sha256:782a71c6ca417df71589d8bd2604d98285eda99d4faa4ebe9c8779e0b9080d9a ...
Starting service heptapod.host/b2ck/dependency_proxy/containers/library/postgres:latest ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image heptapod.host:443/b2ck/dependency_proxy/containers/library/postgres:latest ...
WARNING: Failed to pull image with policy "always": Error response from daemon: error parsing HTTP 404 response body: unexpected end of JSON input: "" (manager.go:205:0s)
ERROR: Preparation failed: failed to pull image "heptapod.host:443/b2ck/dependency_proxy/containers/library/postgres:latest" with specified policies [always]: Error response from daemon: error parsing HTTP 404 response body: unexpected end of JSON input: "" (manager.go:205:0s)
Will be retried in 3s ...
```
![image](/uploads/f42925a2ef6a84ecf10d50bdf8508b86/image.png)
![image](/uploads/3a8124655501a417df830391cef295e5/image.png)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/431Hosting request for Zandronum, a multiplayer oriented Doom port2023-12-13T18:26:25ZBenjamin BerkelsHosting request for Zandronum, a multiplayer oriented Doom port## Description of the projects to be hosted
- Project Name: Zandronum
- Project URL: https://zandronum.com/
- Project Maintainers: Benjamin Berkels <torr.samaho@quantentunnel.de>, Adam Kaminski <kaminskiadam9@gmail.com>
- Project Licens...## Description of the projects to be hosted
- Project Name: Zandronum
- Project URL: https://zandronum.com/
- Project Maintainers: Benjamin Berkels <torr.samaho@quantentunnel.de>, Adam Kaminski <kaminskiadam9@gmail.com>
- Project License: 4-clause license based on the OSI-approved and GPL-compatible Sleepycat License, with the addition of the "No Endorsement" clause from the 3-clause New BSD License.
Please explain here how they meet our current criteria.
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
We are currently using https://osdn.net/ for our development repositories, but since OSDN is not working properly anymore and it does not seem that this will be fixed, we want to move all our repositories to a new FOSS host.
- [x] you are an official maintainer of the project
I am an official maintainer and also founder of this project.
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
We will of course add the acknowledgements, if you grant our hosting request.
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
Yes, it had numerous releases in the past (see https://zandronum.com/) and is release on flathub (https://flathub.org/apps/com.zandronum.Zandronum) and in the AUR (https://aur.archlinux.org/packages/zandronum).
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
Right now, I see more than 100 active players on the public server list. I would estimate the total number of users (players) is above 1000.
- number of maintainers and regular contributors
A handful.
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
The hg repositories are currently hosted at https://osdn.net/. This also has a tracker, but we don't use that. We host a tracker at https://zandronum.com/tracker/. We are looking mainly for a place to host our hg repositories.
### Hosting type
What would you like to have?
- [x] a top-level group
A group called Zandronum, where we can host our hg repositories as groups.
- [ ] a project in an existing group
- [ ] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [x] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/181DISTILIBRE: a Tryton verticalisation project2023-12-03T14:43:01ZVERSATILcode@versatil.frDISTILIBRE: a Tryton verticalisation project## Description of the projects to be hosted
- Project Name: DISTILIBRE
- Project URL: https://distilibre.org
- Project Maintainers: VERSATIL
- Project License: GPL V3
DISTILIBRE is a verticalisation of [Tryton](https://tryton.org), for...## Description of the projects to be hosted
- Project Name: DISTILIBRE
- Project URL: https://distilibre.org
- Project Maintainers: VERSATIL
- Project License: GPL V3
DISTILIBRE is a verticalisation of [Tryton](https://tryton.org), for the craft spirit industry.
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
- [x] you are an official maintainer of the project
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
- number of maintainers and regular contributors
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [x] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/410Hosting request for The Void Programming Language2023-11-07T09:26:51ZDmitry BorodkinHosting request for The Void Programming Language## Description of the projects to be hosted
- Project Name: Voidc
- Project URL: currently https://github.com/Dmitry-Borodkin/voidc
- Project Maintainers: Dmitry Borodkin (me)
- Project License: LGPL 3.0
Please explain here how they me...## Description of the projects to be hosted
- Project Name: Voidc
- Project URL: currently https://github.com/Dmitry-Borodkin/voidc
- Project Maintainers: Dmitry Borodkin (me)
- Project License: LGPL 3.0
Please explain here how they meet our current criteria.
### Main criteria
- [x] Free / Open Source
- [x] main development repositories
- [x] you are an official maintainer of the project
- [x] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
Not yet. But in several months I suppose to make some "initial release"...
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
For couple of years - rather small. Then - who knows?
- number of maintainers and regular contributors
For the moment - just me alone.
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
At GitHub (with TortoiseHg+hggit) without any kind of additional "payload".
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [x] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/419pipline fail to start when pushing - starts when editing online2023-10-31T06:32:36ZHartmut Goebelpipline fail to start when pushing - starts when editing onlineHi.
for a quite simple project I added a [.gitlab-ci.yml](https://foss.heptapod.net/tryton-community/community/website/-/blob/xxxxx/.gitlab-ci.yml?ref_type=heads) file. This uses git as repository format.
- the pipeline starts when edit...Hi.
for a quite simple project I added a [.gitlab-ci.yml](https://foss.heptapod.net/tryton-community/community/website/-/blob/xxxxx/.gitlab-ci.yml?ref_type=heads) file. This uses git as repository format.
- the pipeline starts when editing the .gitlab-ci.yml
in gitlab (adding/removing white-space)
- the pipeline does *not* start when pushing a change
As you can see in https://foss.heptapod.net/tryton-community/community/website/-/commits/xxxxx?ref_type=heads
- the pipeline did run for 6f304862 which I edited online
- the pipeline did not run for [ebd76afd](https://foss.heptapod.net/tryton-community/community/website/-/commit/ebd76afdb285ddc762bd2db68112bdc6cf7426c4), which I pushed
Related:
- Before I edited the .gitlab-ci file online, I pushed several attempts. None of which ran, as you can see in the [commit log](https://foss.heptapod.net/tryton-community/community/website/-/commits/xxxxx?ref_type=heads)
- Also none of these pushes made the [pipeline list](https://foss.heptapod.net/tryton-community/community/website/-/pipelines) show up. Instead this page showed the "Get started with GitLab CI/CD" content.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/432Emails on push integration send email for topics2023-10-26T14:22:15ZCédric Kriercedric.krier@b2ck.comEmails on push integration send email for topicsSince few hours, our "Emails on push" integration started to send emails when user push to topic.
The integration is configured for "Default branch and protected branches".
The topic even based on the default branch should not be conside...Since few hours, our "Emails on push" integration started to send emails when user push to topic.
The integration is configured for "Default branch and protected branches".
The topic even based on the default branch should not be considered as default branch.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/423forced-push does not update merge-request2023-10-03T20:27:21ZHartmut Goebelforced-push does not update merge-requestWhen force-pushing a branch to a git-repo, the merge-request is not updated.
I pushed to [branch `WD`](https://foss.heptapod.net/tryton-community/community/website/-/commits/WD) a few minute ago, but the [related merge-request](https://...When force-pushing a branch to a git-repo, the merge-request is not updated.
I pushed to [branch `WD`](https://foss.heptapod.net/tryton-community/community/website/-/commits/WD) a few minute ago, but the [related merge-request](https://foss.heptapod.net/tryton-community/community/website/-/merge_requests/2) is not updated.
I used ssh to push.
Possible related to #419https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/424issue templates are not availalble2023-10-03T20:27:20ZHartmut Goebelissue templates are not availalbleI a git repository
I created issue templates in `.gitlab/issue_templates/`, following the examples of this very project.
https://foss.heptapod.net/tryton-community/community/heptapod/-/tree/main/.gitlab/issue_templates
Anyhow templates ...I a git repository
I created issue templates in `.gitlab/issue_templates/`, following the examples of this very project.
https://foss.heptapod.net/tryton-community/community/heptapod/-/tree/main/.gitlab/issue_templates
Anyhow templates are not available in
https://foss.heptapod.net/tryton-community/community/heptapod/-/issues/new
I pushed using ssh.
Possible related to #419 and #423https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/422OSUOSL workers fails to download artifacts2023-10-01T20:06:34ZCédric Kriercedric.krier@b2ck.comOSUOSL workers fails to download artifactsWe have may jobs that are failing like this: https://foss.heptapod.net/tryton/tryton/-/jobs/2100224 \
They all have in common to be running on OSUOSL worker.We have may jobs that are failing like this: https://foss.heptapod.net/tryton/tryton/-/jobs/2100224 \
They all have in common to be running on OSUOSL worker.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/224System upgrade for OSCI Runner2023-09-13T08:12:33ZGeorges RacinetSystem upgrade for OSCI RunnerThe OSCI Runner is running an older OS version than the rest of the swarm.
Several issues depend on its upgrade, even if just to move this cause of problems out of the way: #221, #222 and perhaps more.
~RunnersThe OSCI Runner is running an older OS version than the rest of the swarm.
Several issues depend on its upgrade, even if just to move this cause of problems out of the way: #221, #222 and perhaps more.
~RunnersGeorges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/411Notifications stopped working?2023-08-22T06:21:47ZMatti PicusNotifications stopped working?I used to get an email for new issues and commits to PyPy projects. Now I no longer get notifications. My settings have not changed, and my email is valid.I used to get an email for new issues and commits to PyPy projects. Now I no longer get notifications. My settings have not changed, and my email is valid.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/223Project for hg-fastimport2023-07-12T12:40:03ZRoy MarplesProject for hg-fastimport## Description of the projects to be hosted
- Project Name: hg-fastimport
- Project URL: https://roy.marples.name/projects/hg-fastimport, https://wiki.mercurial-scm.org/FastImportExtension
- Project Maintainers: Roy Marples
- Project Li...## Description of the projects to be hosted
- Project Name: hg-fastimport
- Project URL: https://roy.marples.name/projects/hg-fastimport, https://wiki.mercurial-scm.org/FastImportExtension
- Project Maintainers: Roy Marples
- Project License: GPL2
Please explain here how they meet our current criteria.
### Main criteria
- [X] Free / Open Source
- [X] main development repositories
- [X] you are an official maintainer of the project
- [X] agreement to acknowledge where appropriate the help provided by Octobus
and Clever Cloud by hosting on foss.heptapod.net
### Additional information
Knowing this can help in case there are constraints on resources and/or
administrators availability at the time of the request. It can also help us
suggest the right solution for the needs of the project.
- is the project officially released? In downstream distributions or
packaging systems?
Yes, in pkgsrc at least.
https://pkgsrc.se/devel/py-hg-fastimport
- estimation of the user base if possible, or number of downloads,
reverse dependencies…
No idea, but likely small.
- number of maintainers and regular contributors
1
- where is the project currently hosted? Are there issue trackers,
review systems, CI/CD to hook to or to replace somehow?
I used to self host but I can no longer do this.
I am looking for a new host, there are no trackers or CI to replace, just a place to host the code is currently needed.
### Hosting type
What would you like to have?
- [ ] a top-level group
- [ ] a project in an existing group
- [X] just a project in your personal namespace
## Post approval maintainer task list
See [README](README.md#maintainer-task-list-for-the-import-to-happen)
for explanations.
- [ ] Reviewing [Heptapod workflow](https://heptapod.net/pages/faq.html#workflow)
## Post import maintainer task list
- [ ] Add the Octobus and Clever cloud acknowledgement at the selected place.
- [ ] Communicate about the migration to help others to aware of the options
(for example on mastodon, twitter, bitbucket thread, mailing list, …)https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/225OSUOSL: experiment without the Cellar cache2023-06-30T16:42:58ZGeorges RacinetOSUOSL: experiment without the Cellar cacheWhen we started using our own Container Registry, `registry.heptapod.net`, we quickly had to work around bandwidth issues between Clever Cloud services (in this case the S3-compatible Cellar, which actually holds container layers) and OS...When we started using our own Container Registry, `registry.heptapod.net`, we quickly had to work around bandwidth issues between Clever Cloud services (in this case the S3-compatible Cellar, which actually holds container layers) and OSUOSL. It was by then around 2-3 MB/s.
At the time, the solution was to introduce a caching layer at OSUOSL. In theory, the configuration should not have tampered with uploads, but in practice it does, which makes for long debugging sessions that we cannot really afford. The consequence was the introduction of the `container-registry-push` tag, to avoid building images on runners that don't have the capability to upload them.
After some changes in our swarm of Runners, we only have two instance runners available for container builds: `osci-01-docker-x86_64` and `clever-cloud`. The OSCI runner is currently [in trouble](#224) and the Clever runner cannot be used [in some cases](#218). This is bad.
I've just took some fresh bandwidth measurements and got 17 MB/s to get a 1 GB file from Cellar to OSUOSL. This looks acceptable enough to at least experiment removing this caching layer from OSUOSL runners. In turn, this should make them also able to use shared CI caches (less efficiently than the `clever-cloud` runner, obviously).
## Task list
- [x] Detach `osuosl-01` and `osuosl-02` from the Cellar cache, tag them `container-registry-push`
- [x] Test Docker image production on instance runners
- [x] Configure S3 shared CI caches on Omnibus Heptapod dedicated runners (`osuosl-openstack-01-omnibus-heptapod` and `osuosl-openstack-02-omnibus-heptapod`, same systems actually, with different configurations)
- [x] Confirm proper cache behaviour on the Omnibus runners with the upcoming builds for Heptapod 0.36.3
- [x] Generalizehttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/218Socket connection timeout with bower.io2023-06-27T15:49:04ZCédric Kriercedric.krier@b2ck.comSocket connection timeout with bower.ioJobs running on clever-cloud runner are failing because of a socket timeout against bower.io like https://foss.heptapod.net/tryton/tryton-docker/-/jobs/1867825
Locally there are no problem to connect to bower.io so there seems to be netw...Jobs running on clever-cloud runner are failing because of a socket timeout against bower.io like https://foss.heptapod.net/tryton/tryton-docker/-/jobs/1867825
Locally there are no problem to connect to bower.io so there seems to be network issue between clever-cloud and bower.io.https://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/221Running node on CI fails2023-06-26T10:22:50ZCédric Kriercedric.krier@b2ck.comRunning node on CI failsSuch [job](https://foss.heptapod.net/tryton/tryton-docker/-/jobs/1957699) is now failing. This seems to be related to thread.\
I got recently similar issue with memcached, this was because the docker version was too old.Such [job](https://foss.heptapod.net/tryton/tryton-docker/-/jobs/1957699) is now failing. This seems to be related to thread.\
I got recently similar issue with memcached, this was because the docker version was too old.Georges RacinetGeorges Racinethttps://foss.heptapod.net/heptapod/foss.heptapod.net/-/issues/222Many CI jobs fail randomly for "shell not found"2023-06-26T09:53:36ZCédric Kriercedric.krier@b2ck.comMany CI jobs fail randomly for "shell not found"We have many CI jobs like https://foss.heptapod.net/tryton/tryton/-/jobs/1966078 that are failing randomly with this message: `shell not found` just after using the docker image.We have many CI jobs like https://foss.heptapod.net/tryton/tryton/-/jobs/1966078 that are failing randomly with this message: `shell not found` just after using the docker image.Georges RacinetGeorges Racinet