Posts
4818Following
319Followers
488OpenPGP: 3AB05486C7752FE1
Jarkko Sakkinen
jarkko
To make things worse, none of them are supported by the main project so you have to got to a treasure hunt in order find one.
Something like librunner-ci and runner-ci would be best I.e. runner services can call the API and runner-ci implement command -line application for running a CI job using librunner-ci, which has a dual function as a reference implemention for runner services adding heir adaptation.
0
0
0
Jarkko Sakkinen
jarkko
0
0
0
Jarkko Sakkinen
jarkkoRequires quite selective use tho because it does not scale that well.
#riscv #zkvm
0
0
0
repeated
Signal
signalapp@mastodon.worldWe're aware of reports that access to Signal has been blocked in some countries. As a reminder, Signal's built-in censorship circumvention feature might be able to help if your connection is affected:
Signal Settings > Privacy > Advanced > Censorship circumvention (on)
1
21
1
Jarkko Sakkinen
jarkko
0
0
0
Jarkko Sakkinen
jarkkoI think we as an industry could take the quantum leap and define standard for something like ".runner-ci.yml", and when split to multiple files ".runner-ci.d/*.yml". Then, just define stages and tasks.
That would also fix migration between hosts for Git repositories. Also, in a private company internal CI and external CI can sometimes be different. Only way to address is to support both, which is redundant work.
1
1
1
repeated
DCoder 🇱🇹❤🇺🇦
dcoderlt@ohai.socialAmazing work, @ryanc !
Edit: Direct link to Ryan’s write-up: https://rya.nc/vpp-hack.html
0
5
1
Jarkko Sakkinen
jarkkoMy workflow has been before:
1. Edit .gitlab-ci.yml without knowing what I'm actually doing.
2. git push
3. Hope for the best, fear for the worst.
It has been pretty difficult to learn it when I have to test every edit remotely and once I reach my quota wait for some weeks to continue.
And no, GitLab runner is not a solution:
1. I've never been able to successfully set it up.
2. It does not scale to multiple Gitlab instances easily.
3. Even if two former were somehow addressed I do not want to run random system daemons.
I.e. to summarize: A local Gitlab runner sucks. It sucks unimaginably hard.
#gitlab #ci
1
0
2
Jarkko Sakkinen
jarkko
0
0
1
repeated
Thomas Sturm
tsturm@famichiki.jpJapan, national morning news show:
An uninterrupted 10 minute segment about a new train running on a line to a popular vacation spot.
A journalist spends most of the segment being absolutely DELIGHTED by every single feature of this tastefully designed train. She sits in every class of car, tries every seat feature, eats a curry in the dining car, enjoys the view out of panorama windows. Arrives rested and gives us a whirlwind tour of town.
This is how you change car culture.
1
8
2
Jarkko Sakkinen
jarkkoThe priority for me was to squeeze down the compilation time for testing/CI while still having up to date tracing capabilities.
0
1
1
Jarkko Sakkinen
jarkkoDynamic EQ is not a great tool for shaping transients as the filters are connected in series. This will result most "bending" transients as EQ points will interact and are interconnected. For shaping, band needs to be split into blocks, and this exactly what a multi-band compressor does.
This reduces the meaningful parameters to exactly one: dynamic range:
1. Define a dynamic range (in dB for an EQ point.
2. Figure out values for the parameters that keep it within that range.
So with the dynamic EQ below this would mean a manual tuning until you find some
values that seem to work, and depending on signal coming this could even mean automating those parameters, depending on how static the signal is. Also any change to the signal coming in would require re-adjusting them.
On the other hand, Pro-Q3 starts from the dynamic range as the input parameter, listens the signal and adjusts compressor parameters dynamically to stay within the range, without user intervention.
Not my cup of tea because the choice is between spending hours on it vs spending less than a minute figuring this all out 🤷
#MusicProduction
0
0
0
repeated
Alasdair Allan
aallan@mastodon.socialAnnounced today at @defcon is #RaspberryPi's new microcontroller, the #RP2350. Two #Arm Cortex-M33 cores, two #RISCV Hazard3 cores, and more of everything you liked about #RP2040. Congratulations to all my former colleagues at Pi on a lot of hard work! https://www.raspberrypi.com/news/raspberry-pi-pico-2-our-new-5-microcontroller-board-on-sale-now/
0
2
0