Lmst

🚨BREAKING NEWS🚨: The latest groundbreaking #innovation in data processing - a CSV tool that does absolutely nothing because it's too busy being "unavailable" 🤦‍♂️. Finally, a service that promises to revolutionize how you stare at error messages! 📉🔒
https://apps.microsoft.com/detail/9pfcrwp46v22?hl=en-US&gl=US #CSVtool #Nothingness #ErrorMessages #DataProcessing #HackerNews #ngated

📉 Google Gemini's latest #update has turned it into the digital equivalent of a Victorian schoolmarm, wagging its finger at anything remotely emotional. 🚫 Forget about using those apps for trauma recovery—you're now greeted with an error message as comforting as a brick wall. 🙄
https://www.theregister.com/2025/05/08/google_gemini_update_prevents_disabling/ #GoogleGemini #VictorianSchoolmarm #EmotionalSupport #ErrorMessages #DigitalWellness #HackerNews #ngated

“Whilst it’s better to keep #errorMessages conversational, it’s important not to push it too far…Errors are moments of friction. Sometimes they’re unavoidable, but respecting our users means prioritising #clarity and #empathy… Whimsy can feel especially dismissive if a user is stressed or trying to complete something important. Imagine being late for a job interview and getting a “Whoopsie!” from the train ticketing app.”

https://piccalil.li/blog/how-to-write-error-messages-that-actually-help-users-rather-than-frustrate-them/

🎉 Breaking News: #ResearchGate has discovered the ultimate way to boost #productivity – by blocking everyone from accessing their site! 🚫🌐 Apparently, hitting a wall of error messages is exactly what we needed to not read about 'Xiaofeng Wang'. Who knew? 😂
https://www.researchgate.net/profile/Xiaofeng-Wang-35 #BreakingNews #Hacks #ErrorMessages #XiaofengWang #HackerNews #ngated

Welp you still printed so I'm counting that as a win #errorMessages #linux

A printer self-test page from CUPS. It has some Computer Stuff at the top, and then a box made with % signs. Inside the box it read "If you ccsn read this, you are using the wrong driver for your printer."

Is #pixelfed down or is it just me?
#errorMessages #error

Adding more beautiful error messages to Kitten. These should help make it easier to recover from common errors while authoring.

https://kitten.small-web.org

#Kitten #errorMessages #design #usability #authoring #SmallWeb #SmallTech #HTML #CSS #JavaScript #NodeJS #server #framework #platform #web #dev

Screenshot of Kitten error page with cute illustration of a grey kitten with pink ears and nose playing with a purple ball of yarn followed by the error message:

500
Error: Attempt to instantiate kitten.Component in markup without calling its connectedTo() static factory method:
In your kitten.html``, replace:

<{Uptime} />

With:

<{Uptime.connectedTo(this)} />

Finally, there’s a partial view of a stack trace that scrolls off the page.

So last night, while recording the preview of Kitten’s¹ improved component model², I made a silly mistake (copying raw HTML into a JavaScript function instead of wrapping it in a kitten.html`` tagged template, easy to do when you’re refactoring to pull out components from pages).

Then, once I figured out what I’d done, I made another one by forgetting to return the value from the function (easy to do when you’re used to using one-line closures as render functions).

I would have caught both of those so much faster if Kitten had helpful error messages for those two pitfalls. And guess what, this morning, it does :)

Attached are screenshot showing the before and after error messages.

Enjoy!

:kitten:💕

¹ https://kitten.small-web.org
² Scroll up the thread to watch the video.

#Kitten #SmallWeb #PeerToPeerWeb #web #server #framework #platform #design #usability #errorMessages #authoring #dev #JavaScript #HTML #CSS #htmx #hypermedia #WebSocket #StreamingHTML #SmallTech

Screenshot of first error message (before):

500 TypeError: Cannot read properties of undefined (reading 'match')

Screenshot of first error message (after):

Error: Render function did not return kitten.html``

class Count extends kitten.Component {
html {
kitten.html`<h1 morph>${kitten.db.counter.count}</h1>`
}
onIncrement {
kitten.db.counter.count++
this.update
}
}

Screenshot of second error message (before):

500 SyntaxError: Unexpected token '<

Screenshot of second error message (after):

500 SyntaxError: Unexpected token '<

(Did you put raw HTML inside a function by mistake instead of wrapping it in a kitten.html`` tagged template?)

Pro tip: If your error message is longer than a tweet, it’s not user-friendly.

#userexperience #errormessages #techtips

Angular Reactive Forms: Everything you need to know by Abdelfattah Ragab

Available on https://shop.tredition.com and https://www.amazon.com

#angular #reactiveforms #fromarrays #validation #errormessages #hierarchicalgroups #fileinput #fileupload #imagepreview

Angular Reactive Forms: Everything you need to know by Abdelfattah Ragab

Good error messages are hard, but it must be possible to do better than:

No instance for ‘MArray
(STArray s) Char Data.Functor.Identity.Identity’
arising from a use of ‘readArray’

For the program:

foo = runST do
ary <- newListArray (0,4) "hello" :: ST s (STArray s Int Char)
pure $ flip execState "" do
for_ [0..4] \i -> do
c <- lift $ readArray ary i
modify' (c:)

https://discourse.haskell.org/t/state-monad-within-st-monad/11010?u=jaror

#haskell #errormessages

#errormessages to die for. #waze

RE: https://mastodon.social/users/tubetime/statuses/113263471500879297

Aaah the dulcet tones of the bottom falling out of your world when your Linux machine stalls during reboot and the only real error message amounts to:

"This is R0yally B0rked" *
----

[Several Hours later - In the grand tradition of "Turn it off and on again "
- Restarting a total of three times, (complete power downs) seems to have fixed all the problems.

::sigh:: ]

#Linux #ErrorMessages

Can anyone translate broken Unicode for me? #errormessages #help

A piece of software where all the text is displaying as question marks and random characters from various languages.

What TypeScript says:

```
Type '{ name: string; kind: "alias"; options: { name: string; kind: "field"; type: string; options: {}; }; }' is not assignable to type 'FieldSchema'.
Property 'type' is missing in type '{ name: string; kind: "alias"; options: { name: string; kind: "field"; type: string; options: {}; }; }' but required in type 'AliasField'.
```

What I would wish it to say:

```
On line 44 add: `type: null`
```

Like how on earth is it possible to make a language that has such bad bad bad error messages? And intentionally ignore user complaints for years?

To not be old-man-yells-at-cloud:

1) Make it readable. Why is it that the example code is smushed to one-liner? Who can read code like that? Just prettify it across multiple lines.
2) Make it copy&pasteable. The parses is _theoretcially_ telling me _what_ to put _where_, but it would be way more practical if it'd just give me the code it expects. Even if it's just with `...` on places where it can't decide for me.
3) I'm actually surprised that I'm saying that, but on the side of telling me in words "but required in type 'AliasField'", give me also the excerpt of the type it violates with the pointer to that place. If I'm required to write TS, then I should be also able to read it and not translate from your-error-message-words -> TS.

#TypeScript #ErrorMessages #DX #WebDevelopment #CanWeDeprecateTypeScriptYet

#ErrorMessages In a previous life I wrote and supported various bits of software. I am still secretly proud of this terrible error screen from my INCA museum catalogue, which I recently resurrected in a VM... Am I a bad person? 😂 #HardCheese #Software #UserInterfaces

I don't have a Tumblr account but I read a good few blogs over thataways. And it just gave me the following error:

"We're sorry.

"Service is temporarily unavailable. Our engineers are working quickly to resolve the issue.

"Find out why you may have encountered this error."

Mind you, there's no clickable link or further information accompanying that last sentence. Just an instruction to go find out. Like, "You figure it out. Good luck, buddy."

#ErrorMessages #Usability #Tumblr

When #users come across #errors they are in need of help. It hurts their feelings and their #UX if our #errorMessages are bad.

Some great tips by #wix https://wix-ux.com/when-life-gives-you-lemons-write-better-error-messages-46c5223e1a2f
- state what happend & reassure user
- provide a way to fix it
- provide way out of fixing doesn't work

A bad error message using inappropriate tone, passing the blame to the user, speaking in tech jargon and its too generic.

Just improved the display of error messages in Kitten¹.

They should be far more robust now.

Run `kitten update` to get the latest.

:kitten:💕

¹ https://codeberg.org/kitten/app

#Kitten #errorMessages #stackTrace #web #dev #JavaScript #nodeJS

$Screenshot of error message in browser: There’s a cute illustration of a kitten playing with a ball of purple yarn. The error code (in pink) is 500. The error message reads ‘ReferenceError: meow is not defined’ Under that is a Stack trace split into two sections, ‘From your app’ and ‘From Kitten’. In the first section, there’s a coed snippet shown with syntax highlighting, line numbers, and striped lines (white/pink): export default () => kitten.html` ${meow}! ` The ‘m’ in meow has a pink arrow head (caret) pointing to it. The stack trace message reads: While running PageRoute.default [as _handler] in /index.page.js (line 2, column 5) In the From Kitten section the following stack messages are visible: While running PageRoute.lazilyLoadedHandler in /kitten-bundle.js (line 239183, column 31) While running loop in /kitten-bundle.js (line 203214, column 65) While running next in /kitten-bundle.js (line 203215, column 73) While running Array.<anonymous> in /kitten-bundle.js (line 239777, column 9)$

#ErrorMessages

Client Info