yarnd? 🤔I 'm seeing this error: incomplete chunked encoding error(s) 
I don't know anything about this though, tbh I've never seen this before myself 🤔yarnd? 🤔I 'm seeing this error: incomplete chunked encoding" error(s)  I don't know anything about this though, tbh I've never seen this before myself 🤔
/https://baldo.cat/media/photos/photo_20325-07-2024_09-39-29.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
commit 4304ec7ea3c5df95e0ed82bfa292c9330e342f61
Author: James Mills <james@mills.io>
Date: Mon Jan 24 00:10:33 2022 +0000
Fix bug in DownloadImage() leaking termporary files for external avatar downloads (#746)
commit 4304ec7ea3c5df95e0ed82bfa292c9330e342f61
Author: James Mills <james@mills.io>
Date: Mon Jan 24 00:10:33 2022 +0000
Fix bug in DownloadImage() leaking termporary files for external avatar downloads (#746)
watch -n 60 rm -rf /tmp/yarn-avatar-* in a tmux because all of a sudden, without warning, yarnd started throwing hundreds of gigabytes of files with names like yarn-avatar-62582554 into /tmp, which filled up the entire disk and started crashing other services.
abucci@buc:/tmp$ du -sh /tmp/yarnd-avatar-*
564M /tmp/yarnd-avatar-3024946878
7.2G /tmp/yarnd-avatar-3122347915
11G /tmp/yarnd-avatar-3533381443
445M /tmp/yarnd-avatar-441914658
I'm going to have to shut down my server soon. This looks like some kind of DDoS. Whether intentional or not it's filling up the disk at an unsustainable rate.
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (149.71.56.69) "GET /external?nick=lovetocode999&uri=https://pagez.co.uk/services/your-own-100-fully-owned-online-vi>
Jul 25 01:37:39 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:39 (162.211.155.2) "GET /twt/112135496802692324 HTTP/1.1" 400 12 826.65µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (51.222.253.14) "GET /conv/muttriq HTTP/1.1" 200 36881 20.448309ms
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/112730114943543514 HTTP/1.1" 400 12 663.493µs
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (27.75.213.253) "GET /external?nick=lovetocode999&uri=http%3A%2F%2Falfarah.jo%2FHome%2FChangeCulture%3FlangCode%3Den>
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=error msg="http://bynet.com.br/log_envio.asp?cod=335&email=%21%2AEMAIL%2A%21&url=https%3A%2F%2Fwww.almanacar.c>
Jul 25 01:37:40 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:40 (162.211.155.2) "GET /twt/111674756400660911 HTTP/1.1" 400 12 545.106µs
Jul 25 01:37:40 buc.ci yarnd[829]: time="2024-07-25T01:37:40Z" level=warning msg="feed FetchFeedRequest: @<lovetocode999 http://alfarah.jo/Home/ChangeCulture?langCode=en&returnUrl>
Jul 25 01:37:41 buc.ci yarnd[829]: [yarnd] 2024/07/25 01:37:41 (162.211.155.2) "GET /twt/112507964696096567 HTTP/1.1" 400 12 838.946µs
Something really weird is going on?
abucci@buc:~$ du -sh /tmp/yarnd-avatar-3*
1.8G /tmp/yarnd-avatar-3122347915
2.4G /tmp/yarnd-avatar-3533381443
What is this?
yarnd filled up the disk on the VPS where I run it. It's never done anything like this before and I have no idea why it would start. But it threw almost 700 Gbytes of data into /tmp in files like this:
yarnd-avatar-1087570772 yarnd-avatar-1599127133 yarnd-avatar-2042956376 yarnd-avatar-2562946212 yarnd-avatar-3274766535 yarnd-avatar-3931929859 yarnd-avatar-553201529
yarnd-avatar-1089125452 yarnd-avatar-1606826819 yarnd-avatar-2089122560 yarnd-avatar-2611944556 yarnd-avatar-3310922372 yarnd-avatar-3938996661 yarnd-avatar-556240195
yarnd-avatar-1101228867 yarnd-avatar-1618755765 yarnd-avatar-2104107259 yarnd-avatar-2641384948 yarnd-avatar-3326285269 yarnd-avatar-3939402047 yarnd-avatar-559344463
yarnd-avatar-1112165824 yarnd-avatar-1650827505 yarnd-avatar-2142824779 yarnd-avatar-2680659340 yarnd-avatar-3340682113 yarnd-avatar-3998621883 yarnd-avatar-570292705
yarnd-avatar-1119886894 yarnd-avatar-1656673647 yarnd-avatar-2160786463 yarnd-avatar-271923479 yarnd-avatar-3374584613 yarnd-avatar-4005102536 yarnd-avatar-595490106
yarnd-avatar-1131417623 yarnd-avatar-1685698239 yarnd-avatar-2165405940 yarnd-avatar-2793562275 yarnd-avatar-3380606954 yarnd-avatar-4016872095 yarnd-avatar-679251850
yarnd-avatar-1160959085 yarnd-avatar-1746759128 yarnd-avatar-2171489899 yarnd-avatar-2842068287 yarnd-avatar-3416352997 yarnd-avatar-4110048378 yarnd-avatar-679950970
yarnd-avatar-1231649265 yarnd-avatar-1752278279 yarnd-avatar-2251317422 yarnd-avatar-2843868670 yarnd-avatar-3468636088 yarnd-avatar-4116552474 yarnd-avatar-737874628
164 files. Some are empty, some are 7 or even 10 Gbyte.
Any idea what would cause that? And why now, after running
yarnd for so long with nothing like this happening?
Blood red sunsetMore: https://lyse.isobeef.org/waldspaziergang-2024-07-24/
welcome back!
> "Some users experienced message delivery delays beginning last night that primarily impacted linked devices like Signal Desktop. We just deployed a fix. Affected users might see failed delivery notices while Signal automatically catches up. We apologize for the inconvenience!"
Source: Signal Fediverse account
We visited Heddal stave church from 13th century, was really nice. Never been inside it until yesterday. Such a great building. Amazing to sit there and think about all the people who had been there since it was built.
> “And for that, we send our heartfelt thanks and apologies for the inconvenience,” the email read, according to a screenshot shared by the source. The same email was also posted on X by someone else. “To express our gratitude, your next cup of coffee or late night snack is on us!”
Source: Techcrunch
With apology offers like these, who would remember? 🤣
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
smooth run. a bit tired since i had to get it done before heading out to weeki wachee for the day.
#running #treadmill
#catsoftwtxt
/https://baldo.cat/media/photos/photo_20223-07-2024_22-04-55.jpg) #catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_20123-07-2024_22-04-54.jpg) #catsoftwtxt
#catsoftwtxt
#catsoftwtxt
#catsoftwtxt
/https://baldo.cat/media/photos/photo_20023-07-2024_21-51-06.jpg) #catsoftwtxt
#catsoftwtxt
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.
Browsing the web today feels similar to 25 years ago. Even all this wobbling that my link above demonstrates already existed back then (in a way), but it was caused by images loading so slowly. Then, for a brief moment, some browser (I don’t remember which one) had this brilliant feature of trying to keep the current scrolling position *stable* while the page was still loading. That was great. 😃 This feature then got lost again, probably because it’s too hard to do with JavaScript changing the DOM all the time. So now we’re back to the way it was before.
Corporations should give devs the slowest and oldest machines that they have. 😏 Not only would this be more sustainable, it would also force them to optimize better.