A compressed bitset with supporting data structures and algorithms
An atom icon replacement. And a way to install it.
my fork of the build repo. be warned!
Argo Tunnel client
Official Docker Image for Node.js
My gentoo overlay
Mirror of aports repository
:station: - The easiest way to compile JavaScript, HTML and CSS
Optimized bcrypt in plain JavaScript with zero dependencies.
Script for starting bhyve instances based on a libUCL config file
pull request commenth2o/h2o
ci: update iovisor/bcc from a revision of 0.11.0-6021958a to 0.12.0
Confirmed that h2olog testing works with this image! (https://github.com/h2o/h2o/runs/1745751370).
The points are:
- BCC needs the
linux-headerspackage that corresponds to the runtime kernel - Installing linux-headers on
docker build(e.g. 14f2950) on my local VM does not work because it does not match the runtime kernel - The only way to provide the right linux-headers is to share host's /usr/src with containers, i.e. adding
-v /usr/src:/usr/src:rotodocker runoptions
I'm working on h2olog E2E testing on CI at https://github.com/h2o/h2o/pull/2520 to apply the above points.
comment created time in 44 minutes
push eventh2o/h2o
commit sha 1e7a768a13d2b9f5959c61c55a1e50b879ead447
Revert "ci: add linux-headers as a h2olog runtime dependencies" This reverts commit 14f2950840e3552c95778a86150fb0fce746b9b2. This is because build- and runtime kernels migh be different, so the only way that works is to share the /usr/src with containers.
push time in an hour
push eventh2o/h2o
commit sha 28196e5816d455bff5c1728a45b2afb630bc6d10
debug print
push time in 2 hours
URL Validation for Rails
fork in 6 hours
startedjbergstroem/mariadb-alpine
started time in 17 hours
push eventh2o/h2o
commit sha 1cb1ccdf1aad79575b1ece66c4bd20ebbd7dbed0
-v /usr/src:/usr/src:ro
push time in 18 hours
push eventh2o/h2o
commit sha 14f2950840e3552c95778a86150fb0fce746b9b2
ci: add linux-headers as a h2olog runtime dependencies
push time in 18 hours
push eventh2o/h2o
commit sha df941491eacebb0ebec09101f4cffcd6f2ac2479
ci: update iovisor/bcc from a revision of 0.11.0-6021958a to 0.12.0 in order to make sure h2olog work on GitHub Actions
commit sha 4b8ebd5fff602913fb37cd4e9a38624ca2ecbeaf
WIP
push time in 18 hours
push eventnodejs/snap
commit sha 9d1b8961ab676926f12694135a21a765c32d807c
snap: (auto) updated to 16.0.0-nightly20210121e279304954
push time in 19 hours
startedYegorov/awesome-ruby-blogs
started time in 21 hours
startedPopulateTools/gobierto
started time in a day
startedstreamich/react-use
started time in a day
created repositoryEstebanBorai/nasu
🧑🏻⚕️ Command-line utility which poll on remote addresses in order to perform status checks periodically
created time in a day
startedsensepost/objection
started time in 2 days
push eventnodejs/snap
commit sha 3e92d83c4a56dcb0501b8e2b0e185adeef44384a
snap: (auto) updated to 16.0.0-nightly20210120e3e054d020
push time in 2 days
startedFreenove/Freenove_Super_Starter_Kit_for_Raspberry_Pi
started time in 2 days
startedFreenove/Freenove_Starter_Kit
started time in 2 days
starteddotnet-architecture/eShopOnContainers
started time in 2 days
startedstemmlerjs/ddd-forum
started time in 2 days
PR opened h2o/h2o
This PR makes it possible for custom libh2o builds to exclude redis and/or memcached support by simply excluding the dependent library and the lib/common source file from the build. In theory this gives public API support to custom SSL resumption schemes.
This is my first PR so I'm hoping to get an idea of the process, this wasn't a complicated patch and I felt discussion would be easier if I just show what I want to do.
pr created time in 2 days
Node.js debugger based on Blink Developer Tools
fork in 3 days
push eventnodejs/snap
commit sha 38fddfec3a441eae4de36678a99d58ea3d983d60
snap: (auto) updated to 16.0.0-nightly20210119fef21282ef
push time in 3 days
push eventh2o/h2o
commit sha 5597a9de054db6dcd3f75684bdfd3ed0e4585ef7
add comment
push time in 3 days
issue closedlandley/toybox
In the comparison section (inside the roadmap) between the tools that toybox provides (and aims to provide) compared to coreutils, I noticed that b2sum is mentioned twice, the first being with square brackets [b2sum] which indicates that you're planning on adding b2sum in the future, and the latter being in the not section which indicates that you're not planning on supporting it, so which one is true?
coreutils: ... [b2sum] [tr] [unexpand] (not: b2sum base32 ...
Thanks for your time and effort.
closed time in 3 days
firasuke
issue commentlandley/toybox
I've since bumped into blake2 in the wild at work and will probably eventually implement it. Don't think I've heard of blake3 yet?
comment created time in 3 days
push eventlandley/toybox
commit sha 054d82ff46e236a7238c73d3dadfe446a6de4ff3
Remove redundant blake2 mention and move base32 into the implemented list.
push time in 3 days
issue commentlandley/toybox
I wrote some alternative in my package manager, in D but I think I also did some kinda porting vs. the coreutils. This also includes b3 which is the default in my distro. (although probably will revert to b2 or sha35).
You can still build LFS perfectly fine without b2sum, in fact, I don't think they have adopted a patch to move from md5sum to b2sum yet in their book(s).
comment created time in 3 days
startediptv-org/iptv
started time in 3 days
pull request commenth2o/h2o
ci: update iovisor/bcc from a revision of 0.11.0-6021958a to 0.12.0
Thanks. Proceeding the new one in the branch https://github.com/h2o/h2o/tree/gfx/h2olog-e2e-tests-canary , and I have found the tests stick in Docker containers. Fortunately, I can reproduce this problem in a local Docker.
comment created time in 3 days