3 hours of work lost because the Silverlight Lightswitch project randomly decided to shit itself and corrupts it's generated datasource. Twice.

Go fuck yourself you obsolete piece of shit.

Swift's structure is perfect as tableView's dataSource.

*Frustrated user noises* Whyyyy, Grafana, why don't you implement any actual query forgery checks?!

So long as a user has access to the Grafana frontend, they can happily forge the requests going off to the backend, and modify them to return *whatever* data they want from the datasource.

No matter that they're a read-only user. That only stops them from modifying the dashboard definitions on the frontend, but doesn't enforce any sort of immutability on the BE...

If anyone had any tips on how to further secure it, I'm curious...

Ah yes back from school, back into trying to get Arquillian to work. After trying to build on Jenkins (just for a test if they fixed some of the Problems) suddenly it wont even build properly, because they removed the datasource that my Arquillian tests were running on. Great. Not only are my tests not working now, but the whole fucking thing won't build and trying to get a datasource into the Arquillian Container is a pain the ass.
I've set it up according to multiple tutorials. But it always tries to read a non existant datasource... Why, why, why the fuck do I have to do this shit. I fucking hate everything related to JBoss. It... never... works.

Half a day wasted. FUCK!

I use grafana loki and mimir/prometheus for telemetry. A few days ago I queried loki to see if logging is still working. Yesterday I changed the datasource to mimir, changed the query parameters to get metrics from another env, ran the query, and... Querier [mimir] crashed.

Wtf.
Error says it got too much data to chew on.

So I spend 4 hours playing with the querier and grpc limits, balancing between limit errors and OOMKills [2G ram].

I got suspicious about oomk. Why would it...

Then I tried to shrink the timeframe to 15min. Still oomk. Down to 5min -- now it worked. But the number of different metrics returned was over 1k

then I look once again at the query. And ofc it is ´{env="prod"}´

turns out, forgetting that you're querying metrics with a logs' query is an expensive and frustrating mistake. Esp. at 3am.

idk why it even returned me anything...

Loopback 4 really is pulling me out of the expressjs shithole... It really feels like I'm avoiding a lot of tedious work.

"B-b-bbut you have to use typescript and its a slower"

I've preferred typescript ever since angular 2 came out, and the 'slower' comment is invalidated by the fact that, when working on projects that are distributed between multiple devs, are marked by silent errors and serialization issues, and can change datasource types between customers, then the benefits of typescript and loopback's CLI far outweigh any potential slowdowns that may be caused. If you can find me an alternative that does this better, please let me know.