Search Results: "Junichi Uekawa"

6 April 2024

Junichi Uekawa: Trying to explain analogue clock.

Trying to explain analogue clock. It's hard to explain. Tried adding some things for affordance, and it is still not enough. So it's not obvious which arm is the hour and which arm is the minute. analog clock

31 March 2024

Junichi Uekawa: Learning about xz and what is happening is fascinating.

Learning about xz and what is happening is fascinating. The scope of potential exploit is very large. The Open source software space is filled with many unmaintained and unreviewed software.

1 March 2024

Junichi Uekawa: March.

March. Busy days.

11 February 2024

Junichi Uekawa: Adding a new date entry using GAS on Google Docs.

Adding a new date entry using GAS on Google Docs. When I am writing a diary, or having a weekly meeting, it is sometimes tedious to add today's date every time. I can automate such tasks with GAS. There's a onOpen method that gets called every time a doc is opened, and you can use that to implement adding the latest date when the latest date does not match.

2 February 2024

Junichi Uekawa: February already.

February already. I was planning on doing some Debian Rust stuff but then I need to reconstruct my environment.

1 January 2024

Junichi Uekawa: Happy new year.

Happy new year. 2023 saw my first foreign travels since COVID lockdown happened, and that was fun. I felt I had more than enough travel for me. Work life was challenging due to the lay offs and economic environment we are operating in, needs a different mode of operation. Family life is facing a different phase as kids grow, the eldest is approaching the teens.

30 November 2023

Junichi Uekawa: Did a tea ceremony yesterday.

Did a tea ceremony yesterday. Having fun talking about stuff is the most important part.

1 November 2023

Junichi Uekawa: Already November.

Already November. Been playing a bit with ureadahead. Build systems are hard. Resurrecting libnih to build again was a pain. Some tests rely on not being root so simply running things in Docker made it fail.

6 October 2023

Junichi Uekawa: Sick with COVID-19 and flu.

Sick with COVID-19 and flu. This time around we had two different things going around the household. Failure to isolate the second case in the household resulted in more cases.

3 October 2023

Junichi Uekawa: Electronic receipt storage in Japan.

Electronic receipt storage in Japan. Japan also started allowing electronic data for receipts, but had some red tape associated with it. Presumably they were worried about increase in fraud cases. Law amendment that went in effet Jan 2022 made the last annoying bits simpler. We used to be required to sign the paper receipt and scan within 3 days of receiving the receipt. This special requirement is now gone. It took a few years to reach this state but now we are at a similar state as our colleagues in the US. Nice.

1 October 2023

Junichi Uekawa: Family member getting sick, and I'm starting to feel bad.

Family member getting sick, and I'm starting to feel bad. This is bad.

2 September 2023

Junichi Uekawa: September.

September. Looking at performance traces and analysing scheduling and other issues. CPU Cache doesn't really play into effect until I figure out the scheduling issues. They don't collide.

1 August 2023

Junichi Uekawa: August.

August.

13 July 2023

Junichi Uekawa: Spent 2 hours migrating my chrome extension to manifest v3.

Spent 2 hours migrating my chrome extension to manifest v3. Two parts that didn't make sense at first, browser_action to action migration, and executeScript. First, browser_action to action manifest change was straightforward. However it didn't occur to me that I had to rewrite chrome.browserAction.onClicked.addListener to chrome.action.onClicked.addListener. It doesn't say anything on the web page, well maybe the less than equal to MV2. If you deprecate something please say what you replace it with. Second, chrome.tabs.executeScript API was updated to chrome.scripting.executeScript. Apart from the promisified interface that I liked, there was the more important difference that it no longer takes a string to inject as script, it takes a function. So I rewrote my script with $ stuff and as part of that unintentional bugs were fixed and introduced. Trying to figure out where my string became a float unintentionally took a good part of the hour. All in all I have spent 2 hours on migrating my script, this is my second migration. I am not very happy with this transition as it doesn't add any value to my script.

1 July 2023

Junichi Uekawa: New month.

New month. It's been 15 years since I joined the current company. That's a long time.

25 June 2023

Junichi Uekawa: update-info.

update-info. Something is corrupting my /usr/share/info/dir entry. I've found mutt-alias.info.gz and muttrc-mode.info.gz seems to cause the problematic entries. They seem to declare iso-8859-1 and that seems to cause some kind of corruption. Then I found there's a bug 1024997 and then it was fixed in experimental. So this fix didn't get in to bookworm.

16 June 2023

Junichi Uekawa: Upgraded my main machines to bookworm.

Upgraded my main machines to bookworm. Things look relatively eventless. Nice. Emacs is noisy. why is native-comp-async-report-warnings-errors t?

1 June 2023

Junichi Uekawa: Already June.

Already June.

20 May 2023

Junichi Uekawa: Shared library loading.

Shared library loading. ld.so seems to load shared libraries serially, looking through the load paths, looking through DT_LOADED sections, and looking up library paths or what's in ld.so.cache. I thought I could scan DT_LOADED with just reading approx first 2kB of shared library, and get the full list of shared libraries first, and then readahead(2) the list of shared libraries available. The result was that I could load blender binary slightly faster. blender spends about 300ms waiting for disk loading shared libraries and I could shorten it to about 100ms. sopreload, is a proof of concept with rough edges but I think it's a nice improvement.

1 May 2023

Junichi Uekawa: May.

May. Doing some rust stuff and maintenance of existing C++ code. Doing something that I can feel improves the codebase is nice.

Next.