Shopware 6 Hidden Gems #3: sw-expect-packages — let your integration fail fast
Here is a support ticket I have seen in about five different costumes: a middleware pushes orders into Shopware via the Admin API. One day the payloads start failing — or worse, they don't fail, they just silently write incomplete data. After an hour of digging it turns out someone deactivated a plugin on the shop side, or updated it to a version with a different custom field layout.
Civic Museums II 🏛️
民间博物馆 II 🏛️
📷 Pentax MX
🎞️ LUCKY SHD 400 (FF)
If you like my work, Support by buying me a coffee or a roll of film from
PayPal https://www.paypal.com/paypalme/ydcdingsite
Wise
Found a site that always goes the extra mile for it's niche subject, to the point I genuinely feel bad tryna explore rather than be a sincere initiate https://enochian.net/
People who don't mind driverless cars will find all sorts out reason to brush off this kind of news:
https://flipboard.social/@TechDesk/117135628617386440
It was moving slowly already to be safe, it did brake before the collision, the injuries were minimal, the child is at fault, etc.
In the end, a lot of people will shrug and say: human drivers also make mistakes like this, so what's the big deal if a robot does? Maybe the robot even has a better safety record on average than humans. You can't ask for perfection!
Here are three related reasons why you shouldn't buy these arguments:
1. The crash statistics for the "average human driver" include (and are probably significantly driven by) impaired human drivers, like drunk drivers or people on their phones. When driverless car companies put "as good as the average human driver" as the goal, they're saying that they're okay with their systems being just as bad as drunk or distracted drivers sometimes. That's not the right goal at all! We should demand that driving robots perform at least as well as non-distracted human drivers, which is significantly *better* than the average human driver when it comes to things like crashes.
2. Mistakes made by a robotic system are fundamentally different in nature from mistakes made by humans, because the robot mistakes ate *systematic* across all robots in similar-enough situations. If a human looking at their phone slows down too late and hits a child, that's tragic, but it doesn't mean that *every* human driver put into the same situation would make the same mistake. In fact, many of them probably wouldn't be looking at their phone and thus would avoid the accident, *even given the exact same situation in which to react.* In contrast, *every Waymo taxi running the same software* will make exactly the same mistake in that situation. In other words, this kind of event will definitely repeat whenever a similar-enough situation arises around a Waymo taxi. That's why news like this should be scary, even though the accident was a minor one.
3. Some might claim that it's good that a software upgrade could potentially fix the issue that caused this accident. It's sort of true that there's an upside there (although any behavior updates can cause errors in other situations). But the question we should be asking is: why wasn't this already fixed before the vehicle was approved for testing on real roads with real children and people in harm's way? Why wasn't there a stimulation scenario for this exact kind of situation, so that the system already knew what to do? Why should it take a child getting injured for a fix to be developed v(if one in fact will be)? In theory, of course, it's possible that this was a truly exceptional situation where even an alert human couldn't have done better. I'm sure what's what the company is telling the investigators. It's also possible that the designers are following the Silicon Valley motto of "move fast and break things", which reaches an entirely new level of frightfulness when the thing that's moving fast is a car and the thing being broken is a child. "I'll just deploy it now and as test cases when I see what really breaks in production" is an attitude I've been guilty of, but then I make videogames, not deadly robots.
During our vacation recently, I tried to practice more foreground and composition for .. not for documenting our vacation, but to capture more a feeling that I had at this moment.
This is one of the photos. Here it felt "better" to me to set the focus to the red poppies because at this moment, they just drew more attention as we were walking towards the gate.
More of this day:
Folk who've been following me for a long time will remember that last autumn I was posting pictures of doing the joinery for a new workshop. And then I went mad, and got ill, and for most of this year there's been no progress.
But my friend Lucy has been here for a week, and between the two of us the frame is now erected. Now I need to sort the timber stack (which hasn't been improving while I've been ill), erect a roof, and build some walls. But the bit I couldn't …
Theoretical derivation of blood velocity from TOF-MRA based artery centerline
Abrar Faiyaz
https://arxiv.org/abs/2607.16498 https://arxiv.org/pdf/2607.16498 https://arxiv.org/html/2607.16498
arXiv:2607.16498v1 Announce Type: new
Abstract: Time-of-flight magnetic resonance angiography (TOF-MRA) is widely used for structural vascular imaging, but extracting functional hemodynamics like blood velocity typically requires supplementary phase-contrast scans. This study proposes a novel, physics-informed computational framework to extract variable fluid velocity directly from standard TOF-MRA signal profiles. We analytically expand the Bloch equations into Bloch-McConnell flow equations, establishing a mathematical relationship between the spatial decay of longitudinal magnetization and fluid velocity. To validate this derivation and overcome the limitations of constant-velocity assumptions, a MATLAB simulation framework was developed to model fluid flow in two variable-geometry flowing tube cases i.e continuous tapering and focal stenosis -under synthetic scanner noise. A global inverse optimization approach utilizing Dual-Tikhonov regularization was deployed to stably invert the ill-posed transit time integral, actively penalizing high-frequency numerical ringing while preserving structural curve stiffness. The computational sim-ulations successfully recovered ground-truth point-wise velocities, accurately tracking gradual hemodynamic accelerations and sharp stenotic jets. This theoretical framework provides a robust mathematical proof-of-concept that quantitative, localized functional hemodynamic metrics can be extracted from standard structural MRA imaging, estab-lishing a foundation for advanced flow quantification without requiring additional scan time.
toXiv_bot_toot
Replaced article(s) found for astro-ph.GA. https://arxiv.org/list/astro-ph.GA/new
[1/3]:
- CO Observations of Early-mid Stage Major Mergers in the MaNGA Survey
Yu, Fang, Xu, Feng, Feng, Gao, Jiang, Lisenfeld
https://arxiv.org/abs/2404.18999 https://mastoxiv.page/@arXiv_astrophGA_bot/112364597912941989
- A first systematic study of [OIII] 88$\mu$m at $z>8$: two luminous oxygen lines and a powerful io...
Hiddo S. B. Algera, et al.
https://arxiv.org/abs/2512.14486 https://mastoxiv.page/@arXiv_astrophGA_bot/115734347184965000
- Electron temperature relations and the direct N, O, Ne, S and Ar abundances of 49959 star-forming...
D. Scholte, et al.
https://arxiv.org/abs/2601.02463 https://mastoxiv.page/@arXiv_astrophGA_bot/115852861581257007
- The Role of Inner Halo Angular Momentum (Spin) in Shaping Dark Matter Bars in Milky Way Analogs
Shouvik Ghosh, Sandeep Kumar Kataria
https://arxiv.org/abs/2601.14420 https://mastoxiv.page/@arXiv_astrophGA_bot/115938036617000433
- GA-NIFS: Dissecting The Alchemised: JWST reveals turbulent metal-poor gas fuelling a co-spatial s...
Robert G. Pascalau, et al.
https://arxiv.org/abs/2603.00232 https://mastoxiv.page/@arXiv_astrophGA_bot/116164296791419745
- The Star Formation History of WLM from Asymptotic Giant Branch Stars and The Discovery of a Candi...
Abigail J. Lee, Daniel R. Weisz, Andrew E. Dolphin, Alessandro Savino
https://arxiv.org/abs/2603.00243 https://mastoxiv.page/@arXiv_astrophGA_bot/116164584608441374
- Two Exciting High-redshift Galaxy Candidates Turn Out to Be Two Exciting Ultra-cool Brown Dwarfs
Maru\v{s}a Brada\v{c}, et al.
https://arxiv.org/abs/2604.23668 https://mastoxiv.page/@arXiv_astrophGA_bot/116481375281380996
- PEARLS: JWST Counterparts of Micro-Jy Radio Sources in the NEP Time Domain Field. II. All Four Sp...
S. P. Willner, et al.
https://arxiv.org/abs/2605.17040 https://mastoxiv.page/@arXiv_astrophGA_bot/116600246884579228
- Eppur non si trovano Vol. 3: Phoebe -- a Mirage of a Primordial Black Hole
Andrzej Udalski, Przemek Mr\'oz
https://arxiv.org/abs/2606.19442 https://mastoxiv.page/@arXiv_astrophGA_bot/116775643602203820
- LEGGOS I: The JWST LEGGOS Survey -- LEnsing and Galaxy Growth: Observing Substructures -- Unpacks...
Gourav Khullar, et al.
https://arxiv.org/abs/2606.20845 https://mastoxiv.page/@arXiv_astrophGA_bot/116798485365000724
toXiv_bot_toot
How Trump and Musk made the Nepal disaster worse, by glaciologist dr Heïdi Sevestre:
"What about early warning systems?"
SERVIR Hindu Kush Himalaya, a joint initiative by NASA, USAID and ICIMOD monitoring, had mapped landslide and flood hazard in these valleys since 2010.
The Trump administration’s aid freeze cut it in January 2025."
https…
I couldn't decide what to do today and where to go. I got up too late for a longer hike due to the heat. In the end I just got on my bike and followed the road and pushed myself for some training effect.
It was a really enjoyable ride except for the last 10km where the heat got really annoying.
Is this a #silentsunday contribution? I think so... No talking, less thinking, j…