Archive for the ‘Source Code Management’ Category
Posted by jpluimers on 2024/03/12
Still working on handling open Chrome tabs after having moved in the period that GitLab had quite a few issues causing my PagerDuty alerts to go wild.
Today PagerDuty gave me 7 calls in 4 hours again (see [Wayback/Archive] Jeroen Wiert Pluimers @wiert@mastodon.social on X: “@gitlab Since 20240312T1727Z I get PagerDuty alerts from HetrixTools for some pages hosted on GitLab. It would be nice if someone could have a look at gitlab.com/gitlab-com/gl-infra/production/-/issues/17717“).
In adddition I need to check if anything made it to the GitLab issue list from the 20230827 connectivity issues I mentioned at [Wayback/Archive] Jeroen Wiert Pluimers @wiert@mastodon.social on X: “Is it @gitlab hosting having transcontinental issues, or are other continental connections affected as well? These are from two different *.gitlab.io pages as measured via @HetrixTools . No issues are listed at status.gitlab.com“.
Back then, this was the most important one: [Wayback/Archive] GitLab System Status: GitLab.com availability issues – October 30, 2023 15:39 UTC
Likely because of this, wiert.me.gitlab.io had been down for a while as well on 20231031 (see [Wayback/Archive] wiert.me.gitlab.io (Recent History) – HetrixTools down from 2023-10-30T15:24Z until 2023-10-30T16:14Z for 3 + 3 + 11 + 27 = 44 minutes.)
Back then, the hardest part was to quickly find out if there was indeed an issue being investigated at all.
The GitLab status multi-media account on Twitter just points to the status page, which makes it hard to find the underlying issue.
I didn’t archive that one in time, but when I got the alerts it didn’t show anything and when it was resolved it was already beyond the cut-off timestamp to mark it as “same day” and the graph didn’t show much down-time [Wayback/Archive] GitLab System Status graph didn’t show much down-time:
Read the rest of this entry »
Posted in *nix, Cloud, Development, DVCS - Distributed Version Control, GitLab, hetrixtools, Infrastructure, Monitoring, PagerDuty, Power User, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/01/19
I laughed a bit too hard: [Wayback/Archive] @monsieuricon@social.kernel.org: “@torvalds I believe that tree is in a detached state.” in a response to
[Wayback/Archive] Linus Torvalds @torvalds@social.kernel.org: Day four of no power and no Internet. This big tree is the reason.…
Day four of no power and no Internet. This big tree is the reason. One among hundreds in the area, but this is the one that took out *our* power and Internet.
PGE (Portland General Electric) claims we should get power back by 10pm today, but the ice storm arrives today, so we’ll see.
Edit: well, it looks like PGE fixed the outage by just removing me from the outage database, not by actually reconnecting power. That was the second time that happened, so I re-re-reported the outage. Not that I was hugely optimistic about the 10pm timeframe, but it looks even less likely now.
Read the rest of this entry »
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | 2 Comments »
Posted by jpluimers on 2024/01/11
Earlier this week I wrote about Fork Gist to Repo on GitHub – Stack Overflow and found out the example is about the git configuration variable commit.template which was completely new to me.
So below are a few links as it is a very cool feature!
Basically it is a pointer/softlink to a template file that has the initial commit message (the config can either be per repository or global).
Links (most via [Wayback/Archive] “commit.template” “git” – Google Search):
It also has some links to the documentation, but not deep links and misses a few, so I added those below myself.
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2024/01/09
It is not a full fork and misses a few things (including the Gist description), but is the easiest way to clone a gist to a regular GitHub repository.
I needed it because somehow pushing to gists was denied without explanation or real GitHub feedback.
Another reason is that regular GitHub repositories show you way more information about the commits than Gists do.
Thanks [Wayback/Archive] Noitidart for asking and [Wayback/Archive] Bruno Bronosky for answering at [Wayback/Archive] Fork Gist to Repo on GitHub – Stack Overflow:
Read the rest of this entry »
Posted in Authentication, Development, DVCS - Distributed Version Control, gist, git, GitHub, LifeHacker, Power User, Security, Source Code Management | Leave a Comment »
Posted by jpluimers on 2023/10/05
I like JSFiddle, but rather keep source code under my own version control.
I was curious, so queried [Wayback/Archive] gist as jssfiddle – Google Search and found [Wayback/Archive] Publishing a Github Gist to JSFiddle | Toolbox Tech
It has better steps than the official documentation at these links:
- [Wayback/Archive] Pass response directly from a Github repo – JSFiddle Docs
- [Wayback/Archive] Display fiddle from a Github repository – JSFiddle Docs
Demo Directory/
demo.js
demo.html
demo.css
demo.details
demo.[ js | html | css ] contains fiddle code for the specific paneldemo.details is a description of the demo written in YAML
---
name: Name of the Demo
description: Some description, please keep it in one line
authors:
- John Doe
- Jan Wisniewski
resources:
- http://some.url.com/some/file.js
- http://other.url.com/other_filename.css
normalize_css: no
load_type: d
...
- [Wayback/Archive] Display fiddle from Gist – JSFiddle Docs
Read a demo from Github Gist and present it as a fiddle.
Gist files structure
fiddle.js
fiddle.html
fiddle.css
fiddle.manifest
|
|
|
|
|
Contains fiddle code for the specific panel
|
|
|
YAML description of the Gist for JSFiddle to parse
|
Manifest file example
name: The Name of the Fiddle
description: Some description, please keep it in one line
authors:
- John Doe
- Jan Wisniewski
resources:
- http://some.url.com/some/file.js
- http://other.url.com/other_filename.css
normalize_css: no
wrap: bpanel_js: 1
panel_css: 1
Manifest fields
-
panel_html – Language for HTML panel. Accepts:
-
panel_css – Language for CSS panel. Accepts:
-
panel_js – Language for the JS panel. Accepts:
-
resources – List of external resources.
-
-
description – Fiddle description
-
normalize_css – Normalize CSS by loading normalize.css before any CSS declarations.
-
wrap – Set the JS code wrap. Options:
–jeroen
Posted in Development, DVCS - Distributed Version Control, gist, GitHub, JavaScript/ECMAScript, JSFiddle, Scripting, Software Development, Source Code Management | 1 Comment »
Posted by jpluimers on 2023/08/29
If you haven’t done so already, then enable 2FA for your GitHub account now: This will be a requirement in 2 weeks time.
The 2FA/MFA possibility started about half a year ago with [Wayback/Archive] Raising the bar for software security: GitHub 2FA begins March 13 – The GitHub Blog
You can have various means of 2FA, which al start with a choice between:
After completing either of those those, you can view/download a set of backup codes, and you can add more factors to your Multi-factor authentication setup up to these:
Read the rest of this entry »
Posted in 2FA/MFA, Authentication, Development, DVCS - Distributed Version Control, git, GitHub, Power User, Security, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2023/08/02
For my link archive, the table of contents of [Wayback/Archive/Archive] Searching code – GitHub Docs:
Limitations apply:
Due to the complexity of searching code, there are some restrictions on how searches are performed:
- You must be signed into a user account on GitHub to search for code across all public repositories.
- Code in forks is only searchable if the fork has more stars than the parent repository. Forks with fewer stars than the parent repository are not indexed for code search. To include forks with more stars than their parent in the search results, you will need to add
fork:true or fork:only to your query. For more information, see “Searching in forks.”
- Only the default branch is indexed for code search.
- Only files smaller than 384 KB are searchable.
- Only repositories with fewer than 500,000 files are searchable.
- Only repositories that have had activity or have been returned in search results in the last year are searchable.
- Except with
filename searches, you must always include at least one search term when searching source code. For example, searching for language:javascript is not valid, while amazing language:javascript is.
- At most, search results can show two fragments from the same file, but there may be more results within the file.
- You can’t use the following wildcard characters as part of your search query:
. , : ; / \ ` ' " = * ! ? # $ & + ^ | ~ < > ( ) { } [ ] @. The search will simply ignore these symbols.
There is a truckload of languages supported, though the yaml format of the list is not really human readable: [Wayback/Archive] linguist/languages.yml at master · github/linguist
I’ll try this and see if it works better than Google Search.
Via:
–jeroen
Posted in Development, DVCS - Distributed Version Control, GitHub, Google, GoogleSearch, Power User, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 