惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
Stack Overflow Blog
Stack Overflow Blog
Hugging Face - Blog
Hugging Face - Blog
博客园_首页
T
The Blog of Author Tim Ferriss
博客园 - 叶小钗
N
Netflix TechBlog - Medium
腾讯CDC
C
Check Point Blog
P
Proofpoint News Feed
Engineering at Meta
Engineering at Meta
GbyAI
GbyAI
S
SegmentFault 最新的问题
F
Fortinet All Blogs
美团技术团队
U
Unit 42
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 司徒正美
F
Full Disclosure
Recorded Future
Recorded Future
D
DataBreaches.Net
博客园 - 【当耐特】
Martin Fowler
Martin Fowler
J
Java Code Geeks
I
InfoQ
Y
Y Combinator Blog
A
About on SuperTechFans
AI
AI
爱范儿
爱范儿
Exploit-DB.com RSS Feed
Exploit-DB.com RSS Feed
Forbes - Security
Forbes - Security
W
WeLiveSecurity
M
MIT News - Artificial intelligence
雷峰网
雷峰网
cs.CV updates on arXiv.org
cs.CV updates on arXiv.org
Simon Willison's Weblog
Simon Willison's Weblog
Schneier on Security
Schneier on Security
The GitHub Blog
The GitHub Blog
Security Archives - TechRepublic
Security Archives - TechRepublic
aimingoo的专栏
aimingoo的专栏
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
G
GRAHAM CLULEY
Know Your Adversary
Know Your Adversary
Latest news
Latest news
Threat Intelligence Blog | Flashpoint
Threat Intelligence Blog | Flashpoint
D
Docker
Recent Commits to openclaw:main
Recent Commits to openclaw:main
量子位
V2EX - 技术
V2EX - 技术
Project Zero
Project Zero

deaddabe - debian

Status update, May 2022 · deaddabe Status update, April 2022 · deaddabe Status update, February 2022 · deaddabe Status update, January 2022 · deaddabe Status update, November 2021 · deaddabe Status update, October 2021 · deaddabe Status update, August 2021 · deaddabe Status update, July 2021 · deaddabe investigating a curious access issue · deaddabe
Status update, September 2021 · deaddabe
deaddabe · 2021-09-20 · via deaddabe - debian

Status update, September 2021

Now that we finally had some (late) sun, let’s see how things have been.

Rust work

crates.io

I spend too much time trying to figure out how to center images in README.md files. Not only on github.com, but also on crates.io. To this purpose, I dug into the source code of the latter to see how I could make image centering work.

At first, I though the correct syntax was:

<img src="https://img.shields.io/crates/v/clap.svg" alt="" align="center">

I proposed a PR (pull request) to the upstream project, introducing a new unit test to make sure that this usecase will be documented are guaranteed to keep working in the future. After getting this merged, I actually tested to center an image in a crate and push it to crates.io. And the image was not centered. Dumb me. I should have tried this first.

Digging a little bit more, the correct syntax to center images both on github.com and crates.io was:

<p align="center">
    <img src="https://img.shields.io/crates/v/clap.svg" alt="">
</p>

After republishing to crates.io, this now seems to work. The image is centered. Now push to check for github.com. Centered too! Time to send a fix to upstream in order to really test that image centering will be supported in the future.

What a journey. Next time I will remember to test my changes before annoying upstream with a double PR instead of one.

cargo-release

I have started to play with cargo-release in order to try to automate my crate deployements. Indeed, most of my crates are making use of proc macros. They are architectured like this:

Both crates live in the same repository, using a cargo workspace to group them. The crates use the same version release number. However, I manually need to bump the versions in different files on each release. This is where cargo-release helps.

I am however still having trouble in trying to adapt this tool to my workflow. However I hope that I will be able to make it work, as I have currently 3 crates that are using this dual main/macro crates mechanism.

Debian work

DM application

My Debian Maintainer application, which I was happy to brag about in the previous status update, has stalled.

I managed to get my OpenPGP key signed in-person by sharing beers with a DD (Debian Developer) in Paris. However this was not enough to conclude the application. I still needed to find an advocate, that is a person that thinks my technical contributions are strong enough to be let done without further babysitting.

I now need to provide with more signed, irreprochable work before gathering enough street cred to propose my application again.

Stay tuned!