Got an error when pushing a relatively large commit to GitLab: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
There was no big difference in information between these commands¹:
git pushgit push --verbose
Posted by jpluimers on 2026/05/27
Got an error when pushing a relatively large commit to GitLab: error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
There was no big difference in information between these commands¹:
git pushgit push --verbosePosted in //e, 6502, Apple, Apple ///, Apple IIgs, Apple ][, Development, DVCS - Distributed Version Control, git, GitLab, History, Power User, Software Development, Source Code Management, Versioning | Leave a Comment »
Posted by jpluimers on 2026/05/27
After the 2022 GitLab.com backlash* to auto-delete “inactive” (for whichever metric of “inactive”) repositories of free users, I thought they would have multiple checks in place to prevent that from happening.
TL;DR: of two possible checks to prevent this, only one is in place.
This means that if by accident one of those checks stops working, all inactive repositories will be be deleted after a 7 day retention period. Which is very short, especially when you miss the email about it (for instance because of holiday or health reasons).
That bad!
Posted in Awareness, GitLab, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2026/05/21
“Explain it to me like I’m five” works!
[Wayback/Archive] Started making people walk me through their AI PRs in person. The 500-line diffs disappeared overnight : ExperiencedDevs
Via [Wayback/Archive] Post by Frans Bouma (@fransbouma.com) — Bluesky: This is just brilliant.
--jeroen
Posted in AI and ML; Artificial Intelligence & Machine Learning, Development, DVCS - Distributed Version Control, Issue/Bug tracking, LLM, Software Development, Source Code Management, Versioning | Leave a Comment »
Posted by jpluimers on 2026/05/04
Ook vandaag even een herinnering aan de NLUUG voorjaarsconferentie 2026 van (komende) donderdag 7 2026 mei in het Van der Valk Hotel Utrecht¹.
Deze keer omdat een goede vriend van me daar spreekt. Arjen Lentz heeft het over A Wizard’s Guide to Foreseeing the Unseen.
Dat klinkt misschien vaag, het concrete resultaat is dat je met analyse van CVE’s veel te weten komt over hun echte root cause. Die blijkt verrassend voorspelbaar, is fixbaar, en kennis daarover is niet alleen nuttig voor adversaries. Het kan jou namelijk helpen bij de development en selectie van wat je zelf gebruikt.
Het volledige programma staat hieronder², eerst de aankondiging van [Wayback/Archive] L⭕️rd Quux RCX CCX: “Over een week is het zover! De enige NLUUG conferentie van 2026. …” – Mastodon
Posted in Blue team, Development, DVCS - Distributed Version Control, git, Infosec (Information Security), Power User, Red team, Security, Software Development, Source Code Management, Systems Architecture | 1 Comment »
Posted by jpluimers on 2026/04/30

Last 90 days uptime on 20260427 of the GitHub Platform: 87.25%
Because of two alternative GitHub status pages, a lot of people now realise that GitHub gives a rosier result than the official pages.
April uptime not even had one nine, dropping below 89%.
Which begs this interesting question
“How many other services are painting a far rosier picture than reality on their service status pages?” by Dare Obasanjo: “GitHub just published a blogpo…” – mas.to:
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2026/04/20
Via [Wayback/Archive] Importing a repository with GitHub Importer – GitHub Docs I found [Wayback/Archive] Import repository · GitHub which can import from Subversion, Mercurial, TFVC, and Git as per [Wayback/Archive] About GitHub Importer – GitHub Docs.
Note this will import the repository, but not any surrounding things (like tickets/issues, wiki, etc).
In that sense, the more than 10 year old [Wayback/Archive] SourceForge: GitHub Project Importer as documented in [Wayback/Archive] SourceForge Support / Documentation / GitHub Importer does a way better job the other way around.
If you want to import more than just a repository into GitHub, then some inspiration is at [Wayback/Archive] Migrate from Sourceforge to Github – Stack Overflow (thanks [Wayback/Archive] Matthew Talbert, [Wayback/Archive] Masood Khaari, [Wayback/Archive] Thomas and [Wayback/Archive] Sergey Ponomarev) for instance with these tools:
Especially the last one is interesting as it allows you to separate tickets from repository import. This opens up the opportunity to do the svn to git conversion yourself and keep that conversion in place to you can use it to sync incoming svn changes towards the git repository.
The above does not cover CVS. For that, be sure to read these:
Via [Wayback/Archive] import sourceforge into github – Google Search.
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, GitHub, Software Development, Source Code Management, SourceForge, Subversion/SVN | Leave a Comment »
Posted by jpluimers on 2026/03/17
During a Cloudflare outage¹, I learned about [Wayback/Archive] Wisp.place Documentation | Wisp.place Docs
Decentralized static site hosting on the AT Protocol.
Wisp.place enables you to host static websites directly in your AT Protocol repository. Your Personal Data Server (PDS) holds the cryptographically signed manifest and files as the authoritative source of truth, while hosting services index and serve them with CDN-like performance.
This is the documentation of [Wayback/A] wisp.place by [Wayback/Archive] Ana (@nekomimi.pet) — Bluesky.
Related:
Posted in CDN (Content Delivery Network), Cloud, Cloudflare, Development, DVCS - Distributed Version Control, git, Hosting, Infrastructure, Power User, Software Development, Source Code Management | Leave a Comment »