Tag: debugging
-
npm ERR! Exit handler never called!
I quite like GitHub scanning all my code and sending me security advisories. Here’s today’s: With these, and my dependabot alerts, fixing them is usually just a matter of pulling down the project, running an npm update, building any artifacts, then pushing it back up. But today, not so: package-lock.json It’s probably worth revisiting what…
-
Where Do Docker Container Logs Go?
I’m still loving the Docker “just works” magic, despite their terrible PR skills, but sometimes I start a container, then the docker ps -a shows it exited almost immediately. Clearly I’ve made a mistake, but there’s no stdout error message to tell me what I’ve done wrong, where is it. Let’s look at an example…
-
Expired Packages Part II
Following on from the previous post… I went the nuclear route – deleted the node_modules folder, package-lock.json and installed the packages from packages.json. I still had some errors, but the react app at least ran correctly. Also, the messages are a bit more intelligible, and all of them cascade from this one. From my, admittedly…
-
Something weird ‘append
I’m noodling around making sure I understand how Core Data works. Thought I’d start with a master/detail app with an array of structs, then replicate it in a Core Data implementation. I’m using an array of this struct for my data: And I thought this code to load up some sample data was pretty sweet.…
-
Clean Build Folder
Working on adding Core Data to the FriendFace app, and burnt up 20 minutes figuring out a bug. To set the scene, all I’ve changed in the app is to add a couple of core data entities. The plan is that when the JSON is fetched, and decoded into the objects, a copy of the…
-
You need to enjoy puzzles
I’m writing the Habits list based app from #100Days and had a working MVP, then for some reason, decided to refactor by changing the subview I’d written as a function, into a struct. Some time later, I discovered that my list items were not updating correctly, so detective time. I talked a little bit about…
-
iExpense Feedback
I finally got around to looking at Paul’s solutions for the iExpense challenges. Use the user’s preferred currency, rather than always using US dollars. Same approach as me, .currency(code: Locale.current.currency?.identifier ?? “USD”) except that he does the work in a local variable which is a bit neater. Since it appears in two places – the…