
2025-06-10 10:24:32
Density jump as a function of the field for parallel relativistic collisionless shocks
Antoine Bret, Ramesh Narayan
https://arxiv.org/abs/2506.07973 https:…
Density jump as a function of the field for parallel relativistic collisionless shocks
Antoine Bret, Ramesh Narayan
https://arxiv.org/abs/2506.07973 https:…
How to prepare for a 8h train ride: go running.
Now of to Prague to #FlockToFedora; looking forward to meet a lot of old friends there and make new ones.
Ohh, and I give a talk there, too: When and how to use upstream Linux kernels to fix or improve Fedora –
from my link log —
ZJIT has been merged into Ruby.
https://railsatscale.com/2025-05-14-merge-zjit/
saved 2025-05-14 https://
Falls in jemandes rezentem Lenovo-Laptop bei einem Linux-Updtate plötzlich die Bluetooth-Funktionalität verschwindet, könnte sich eine der hier empfohlenen Methoden lohnen (bei mir war "update firmware with upstream" nötig). Schuld war das linux-firmware-Paket.
#ServiceToot #Lenovo
»HTTP/1.1 Must Die – It's time to acknowledge HTTP/1.1 is insecure«
Admittedly, I know pers. not how seriously you have to take this but I am only developing web servers set to HTTP/2.0, because HTTP/3 is not yet extensively supported.
🪦 https://http1mustdie.com
Integrating Upstream Supply Chains into Generation Expansion Planning
Boyu Yao, Andrey Bernstein, Yury Dvorkin
https://arxiv.org/abs/2508.03001 https://arx…
Planar Collisionless Shock Simulations with Semi-Implicit Particle-in-Cell Model FLEKS
Hongyang Zhou, Yuxi Chen, Chuanfei Dong, Liang Wang, Ying Zou, Brian Walsh, G\'abor T\'oth
https://arxiv.org/abs/2506.08384
New set of #Gentoo #Linux Distribution Kernels (6.1.143, 6.6.96, 6.12.36, 6.15.5) is out. This set brings some major changes:
• I've backported a bunch of changes from sys-kernel/gentoo-kernel to sys-kernel/vanilla-kernel that were missing — notably wider architecture support.
• I've added default #RISCV configs to 6.12 (in addition to 6.15), since Fedora had them.
• All three packages are based off the baseline kernel tarball upstream patch (vanilla-kernel used to fetch patch-level tarball every time, and gentoo-kernel* used genpatches for patch versions). This should reduce disk space and bandwidth use.
• All three packages now support verify-sig. Rather than verifying the uncompressed tarball signature, we now use upstream `sha256sums.asc` file to verify the compressed tarball and patch.
• sys-kernel/gentoo-kernel* now repackages genpatches. This means patchset that's much leaner and faster to apply (since we just fetch and use the combined upstream patch rather than including point patches). This also means that we are able to release Distribution Kernels before gentoo-sources are done.
The changes still need to be done to 5.15 and 5.10 branches — we're going to do for the next upstream releases of these.
#kernel
Suppressing secondary shock waves in jam-absorption driving via string-stable support vehicles
Atsushi Suzuki, Akihiro Tokumitsu, Ryosuke Nishi
https://arxiv.org/abs/2508.03604 …
4 MB/s upstream in der Ferienwohnung. Das ist fast schon digital detox.
Why LLM Safety Guardrails Collapse After Fine-tuning: A Similarity Analysis Between Alignment and Fine-tuning Datasets
Lei Hsiung, Tianyu Pang, Yung-Chen Tang, Linyue Song, Tsung-Yi Ho, Pin-Yu Chen, Yaoqing Yang
https://arxiv.org/abs/2506.05346
Uh, World Bank, solar?
World Bank Lifts Ban on Nuclear Power, Considers Upstream Gas | Financial Post
https://financialpost.com/pmn/business-pmn/world-bank-lifts-ban-on-nuclear-power-considers-upstream-gas
hacker: "yeah, I downloaded a driver from the manufacturer. It didn't build of course, because the v2l API changed between what they released and the kernel you're running, but i updated it to the new API and it worked."
linux user: "you going to send the driver upstream?"
https://mk.moth.zon…
To cross or not to cross, that's the question...
(One of the more intense streams — the outflow of a glacier — I had to cross in my life, that bridge looks a lot safer that it was IRL...)
#FootpathFriday #Hiking
This https://arxiv.org/abs/2505.24200 has been replaced.
initial toot: https://mastoxiv.page/@arXiv_csSD_…
Upstream competition and exclusive content provision in media markets
Kiho Yoon
https://arxiv.org/abs/2506.15063 https://arxiv.org/pd…
xAI apologizes for Grok's "horrific behavior" when it wrote antisemitic posts on July 8, and blames "an update to a code path upstream of the Grok bot" (Anthony Ha/TechCrunch)
https://techcrunch.com/2025/07/12/xai-and-grok-apologize-for…
Quantum Hall Andreev Conversion in Graphene Nanostructures
Alexey Bondarev, William H. Klein, Harold U. Baranger
https://arxiv.org/abs/2507.02114 https://
This https://arxiv.org/abs/2503.22935 has been replaced.
initial toot: https://mastoxiv.page/@arXiv_csCR_…
#Matplotlib has a lot of "image comparison tests" that are horrible fragile. Technically, most of them permit some deviation from the reference images, but quite often I've been getting higher RMS than that. So for a long time, we've been maintaining patches that increased the tolerance in tests, and regularly either had to be rebased and updated for new tests.
At some point upstream started adding conditions permitting higher tolerance on non-x86_64 platforms. Of course, these changes forced me to rebase our patches. Curious enough, my previous overrides often happened to be close to the tolerance given for non-x86_64 platforms.
Today, it finally occurred to me that instead of updating the patch once again, I can try dropping it entirely and just sed-ing all `platform.machine() == 'x86_64'` with `False`. And guess what — down to 3 failures (related to TeΧ). And I don't have to spend 15 minutes manually doing what effectively accounted to the same thing.
#Gentoo #Python
@… thanks, I added to upstream <https://bugs.kde.org/show_bug.cgi?id=505552>; and drew attention to the downstream report.
As you ford life's rivers, keep your knees bent and face upstream so you can better see what's coming at you. But as you crawl life's ductworks, face downwind and keep your mouth shut lest you suck in dust-bunnies.
#NaturalPhilosophy #Strife and
“ upstream connect error or disconnect/reset before headers. reset reason: remote connection failure, transport failure reason: delayed connect error: 111”
Clear the decks
Effect of protection zone on the dynamics of a diffusion-advection population-toxicant model
Jing Gao, Xiaoli Wang, Guohong Zhang
https://arxiv.org/abs/2508.01246 https://
Real-Time Capable, Low-latency Upstream Scheduling in Multi-Tenant, SLA Compliant TWDM PON
Arijeet Ganguli, Marco Ruffini
https://arxiv.org/abs/2506.12118 …
Systemic Trade Risk Suppresses Comparative Advantage in Rare Earth Dependent Industries
Peter Klimek, Sophia Baum, Markus Gerschberger, Maximilian Hess
https://arxiv.org/abs/2508.00556
Replaced article(s) found for cs.AI. https://arxiv.org/list/cs.AI/new
[8/8]:
- Machine Learning Methods for Small Data and Upstream Bioprocessing Applications: A Comprehensive ...
Johnny Peng, Thanh Tung Khuat, Katarzyna Musial, Bogdan Gabrys
Filamentation of the electromagnetic precursor in relativistic quasi-perpendicular electron-positron shocks
Emanuele Sobacchi, Yuri Lyubarsky, Lorenzo Sironi, Masanori Iwamoto
https://arxiv.org/abs/2507.22561
Google Project Zero to publicly announce bugs within a week of reporting them https://therecord.media/google-project-zero-publicly-announce-vulnerabilities-week-after-reporting
Cooperation as Black Box: Conceptual Fluctuation and Diagnostic Tools for Misalignment in MAS
Shayak Nandi, Fernanda M. Eliott
https://arxiv.org/abs/2506.22876
Very early in the commercial registrar era, some registrars priced domains in harmony with their costs: no teaser marketing, just discounts on buying multiple future years at once. Even after everyone stopped giving out-year discounts explicitly, the fact of inflation in upstream fees made it wise for legitimate domain holders to buy many years in advance.
I am close to wanting a return to the InterNIC model. DNS Marxism.
Vortex-Induced Drag Forecast for Cylinder in Non-uniform Inflow
Jiashun Guan, Haoyang Hu, Tianfang Hao, Huimin Wang, Yunxiao Ren, Dixia Fan
https://arxiv.org/abs/2506.21075
Probing Proton versus Electron Heating and Energization during Magnetic Reconnection
Zhiyu Yin, James F. Drake, Marc Swisdak
https://arxiv.org/abs/2508.00119 https://
from my link log —
jemalloc postmortem.
https://jasone.github.io/2025/06/12/jemalloc-postmortem/
saved 2025-06-13 https…
Three-dimensional Dynamics of Strongly Magnetized Ion-Electron Relativistic Reconnection
Fabio Bacchini, Gregory R. Werner, Camille Granier, Jesse Vos
https://arxiv.org/abs/2507.12509
Physics-Informed Neural Networks for Nonlocal Flow Modeling of Connected Automated Vehicles
Chenguang Zhao, Huan Yu
https://arxiv.org/abs/2506.18357 https:…
Agentic AI and Hallucinations
Engin Iyidogan, Ali I. Ozkes
https://arxiv.org/abs/2507.19183 https://arxiv.org/pdf/2507.19183…
Occurrence of Non-Stationarity at Earth's Quasi-Perpendicular Bow Shock
Ajay Lotekar, Yuri V. Khotyaintsev, Daniel B. Graham, Andrew Dimmock, Andreas Johlander, Ahmad Lalti
https://arxiv.org/abs/2507.13817
A while ago, I've followed the example given by #Fedora and unbundled ensurepip wheels from #Python in #Gentoo (just checked — "a while ago" was 3 years ago). This had the important advantage that it enabled us to update these wheels along with the actual pip and setuptools packages, meaning new virtual environments would get fresh versions rather than whatever CPython happened to bundle at the time of release.
I had considered using our system packages to prepare these wheels, but since we were already unbundling dependencies back then, that couldn't work. So I just went with fetching upstream wheels from PyPI. Why not build them from source instead? Well, besides feeling unnecessary (it's not like the PyPI wheels are actually binary packages), we probably didn't have the right kind of eclass support for that at the time.
Inspired by @…, today I've tried preparing new revisions of ensurepip packages that actually do build everything from source. So what changed, and why should building from source matter now? Firstly, as part of the wheel reuse patches, we do have a reasonably clean architecture to grab the wheels created as part of the PEP517 build. Secondly, since we're unbundling dependencies from pip and setuptools, we're effectively testing different packages than these installed as ensurepip wheels — and so it would be meaningful to test both variants. Thirdly, building from source is going to make patching easier, and at the very least enable user patching.
While at it, I've refreshed the test suite runs in all three regular packages (pip, setuptools and wheel — we need an "ensurepip" wheel for the last because of test suites). And of course, I hit some test failures in testing the versions with bundled dependencies, and I've discovered a random bug in #PyPy.
https://github.com/gentoo/gentoo/pull/42882 (yes, we haven't moved yet)
https://github.com/pypy/pypy/issues/5306
The evolution of CME sheath turbulence from L1 to Earth: Wind and MMS observations of the 2023-04-23 CME
Matthew R. Argall, Li-Jen Chen, No\'e Lugaz, Norberto Romanelli, Jaye L. Verniero, Charles W. Smith, Brandon Burkholder, Victoria Wilder
https://arxiv.org/abs/2505.13645