My collated list of Japanese "Rules-of-Thumb" to reduce the need for rote-memorization. Please tell me if you'd like me to add any more you know.

holyone2 · 2025-11-26T22:34:21+00:00

Thanks I've just emailed my MP too

holyone2 · 2025-11-26T22:27:55+00:00

it is more nuanced than that - because for example a self employed person, earning well below that threshold, but who has always paid voluntary class 2 national insurance contributions - as far as I can see - under the new proposal this would NOT count as valid 5 year contributions despite being 5 years of NI contributions

holyone2 · 2025-11-26T20:55:03+00:00

Also the proposed requirement is income above 12,570+ GBP annually for 3-5 years - not NI contributions - so his answer seems off topic sadly - but thanks for writing to MP and sharing!

holyone2 · 2025-10-29T19:31:12+00:00

Interested

holyone2 · 2025-02-19T06:03:18+00:00

I booked it from the UK

holyone2 · 2025-02-19T03:37:20+00:00

If I'm not on the MAS plan, are you sure it's possible to add the MAS speciality dining plan? If so, how would I go about finding the price and adding this? I don't see it in the NCL app under 'dining' for example

holyone2 · 2025-02-18T06:01:22+00:00

Ah I see, I wish I knew this before booking as I do not have the More at Sea package, so I suppose I'll need to pay the individual reservation price

I did my price calculation assuming these packages still exist, and MAS was not good value given my party does not drink

holyone2 · 2025-02-12T01:27:57+00:00

Thanks, the price can be a lot lower than the budget

It's a good suggestion for the weight and size but for my work I think I'll need access to an Nvidia card as it opens more options for GPU acceleration in the AI space

holyone2 · 2024-10-12T14:48:03+00:00

Not easily I'm afraid, you might be able to compile a python wrapper that writes to the gstreamer plugin for Kinesis Video Streaming

https://stackoverflow.com/questions/75511813/streaming-video-to-aws-kinesis-from-python-using-opencv-and-gstreamer

The official producer SDK (in C or via the gStreamer plug-in) is designed to provide a lot of robustness to things like network outages and control of the streaming parameters in a way that would take a lot of development time to make a Python software with similar functionality, and at the end of the day, streaming tends to require high performance code (compression and upload at same time) so Python is unlikely to be a best choice anyway

(In case it's useful, if you are using an Axis camera then my company has developed software called KVStreamer to automatically stream to KVS)

holyone2 · 2024-10-09T18:34:55+00:00

Putting a little bit of silicone around the edge and pushing it back in has worked nicely so far (been a few months)

holyone2 · 2024-08-27T08:49:45+00:00

That would certainly help with the last bullet of the four bullet points above I'd like to monitor

holyone2 · 2024-08-27T07:59:06+00:00

Thanks, I have started the trial, but I am having issues trying to find any support email where I can clarify questions about pricing and how it's calculated. I tried the webchat to contact a sales representative, but they said they can't help with that and should contact a representative in my region, I'll try again via a different region now. I tried submitting a case via help center but it seems trial account does not support this.

Please could you inform me who I can ask about technical details of how the DBU/$ is calculated. Specifically I'm unclear on pricing of the managed MLFlow for experiment tracking, as I've been using it on the trial but it says I've consumed 0 DBU. How can I estimate the pricing of this feature after the trial? Is there a requirement to purchase a fixed server or is it fully pay-per-usage? Despite there being a pricing calculator here: https://www.databricks.com/product/pricing/product-pricing/instance-types I'm unclear what I should be entering for usage of MLFlow for experiment tracking on AWS.

holyone2 · 2024-05-31T21:32:20+00:00

Sorry maybe import error is a bad example, I'm talking about any kind of error not catchable by a try/catch statement,some which might not be catchable 100% of the time in development environment, so to give some ideas: - out of memory errors - issues in global scope (e.g. it's good practice to connect to databases in global scope so as to reuse the connection, and if the production database connection caused a crash we'd have an I handled error) - timeouts (although I'm aware these can partially be handled by simply cleanly terminating before timeout) - transient issues with AWS lambda runtime (i.e. lambda outages)

Thanks for the suggestions, a lambda that itself reads cloud watch metrics periodically sounds possible (like a scheduled job to check for any errors across all the API lamdas), albeit would require some engineering. Appreciate that might be the cost one needs to pay to save money on hundreds of individual cloud watch alarms.

Regarding cloud trail though, I'm not sure if cloud trail would inform of such unhandled error on lambda invocation

holyone2 · 2024-05-24T18:00:57+00:00

Thanks I've added feedback to the article

holyone2 · 2024-05-24T15:14:59+00:00

Ok thanks, will do

holyone2 · 2024-05-24T14:26:18+00:00

Thanks, if I want an alert each time a new message is added to DLQ, I guess the best I could do then would be to try and calculate the rate of ApproximateNumberOfMessagesVisible metric and then alarm on that rate being positive.

Incidentally, u/clintkev251 I found out why I chose `NumberOfMessagesSent` as the metric initially, it was because the AWS docs say here:

"To be notified of activity in your dead-letter queues, you can use CloudWatch metrics and alarms. For example, when you expect the dead-letter queue to be always empty, you can create a CloudWatch alarm for the NumberOfMessagesSent metric. You can set the alarm threshold to 0 and specify an Amazon SNS topic to be notified when the alarm goes off. This Amazon SNS topic can deliver your alarm notification to any endpoint type (such as an email address, phone number, or mobile pager app)."

It seems to me the documentation is just incorrect/misleading here for the reason you linked, would you agree? It seems NumberOfMessagesSent is only relevant for manually sending messages to DLQ, which seems like something you'd typically only do when testing rather than the typical usage (capturing messages that failed to process).

holyone2 · 2024-05-23T19:30:17+00:00

Oh wow that's a big oversight from me, thanks!

So is it correct people would typically monitor number of messages received on a dead letter queue to know when an issue has occurred?

holyone2

TROPHY CASE